Repo sync issue on RMT

Hi All,
I'm totally new to SUSE and novice to Linux. I've been recently asked to test deployment of RMT server on SLES15 (to see how non-Linux******** persons deal with instructions they gave ;-) ). When it comes to repo mirror (rmt-cli mirror), it looks like it is synchronizing something but finally it fails with following msgs:
W, [2021-03-18T14:29:56.627564 #8110] WARN -- : The following errors occurred while mirroring:
W, [2021-03-18T14:29:56.627676 #8110] WARN -- : Repository 'SLE-Product-SLES15-Updates' (408): Error while mirroring metadata: https://updates.suse.com/SUSE/Updates/SLE-Product-SLES/15/x86_64/update/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627711 #8110] WARN -- : Repository 'SLE-Product-SLES15-Pool' (410): Error while mirroring metadata: https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15/x86_64/product/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627732 #8110] WARN -- : Repository 'SLE-Product-HPC-15-Updates' (501): Error while mirroring metadata: https://updates.suse.com/SUSE/Updates/SLE-Product-HPC/15/x86_64/update/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627750 #8110] WARN -- : Repository 'SLE-Product-HPC-15-Pool' (502): Error while mirroring metadata: https://updates.suse.com/SUSE/Products/SLE-Product-HPC/15/x86_64/product/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627767 #8110] WARN -- : Repository 'SLE-Product-SLES15-SP1-Updates' (526): Error while mirroring metadata: https://updates.suse.com/SUSE/Updates/SLE-Product-SLES/15-SP1/x86_64/update/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627807 #8110] WARN -- : Repository 'SLE-Product-SLES15-SP1-Pool' (529): Error while mirroring metadata: https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15-SP1/x86_64/product/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627836 #8110] WARN -- : Repository 'SLE-Product-HPC-15-SP1-Updates' (595): Error while mirroring metadata: https://updates.suse.com/SUSE/Updates/SLE-Product-HPC/15-SP1/x86_64/update/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627885 #8110] WARN -- : Repository 'SLE-Product-HPC-15-SP1-Pool' (597): Error while mirroring metadata: https://updates.suse.com/SUSE/Products/SLE-Product-HPC/15-SP1/x86_64/product/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627907 #8110] WARN -- : Repository 'SLE12-SP5-HPC-Updates' (608): Error while mirroring metadata: https://updates.suse.com/SUSE/Updates/SLE-HPC/12-SP5/x86_64/update/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627935 #8110] WARN -- : Repository 'SLES12-SP5-Updates' (609): Error while mirroring metadata: https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP5/x86_64/update/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.627976 #8110] WARN -- : Repository 'SLE12-SP5-HPC-Pool' (613): Error while mirroring metadata: https://updates.suse.com/SUSE/Products/SLE-HPC/12-SP5/x86_64/product/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.628007 #8110] WARN -- : Repository 'SLES12-SP5-Pool' (614): Error while mirroring metadata: https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP5/x86_64/product/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.628042 #8110] WARN -- : Repository 'SLE-Product-HPC-15-SP2-Updates' (631): Error while mirroring metadata: https://updates.suse.com/SUSE/Updates/SLE-Product-HPC/15-SP2/x86_64/update/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.628108 #8110] WARN -- : Repository 'SLE-Product-HPC-15-SP2-Pool' (633): Error while mirroring metadata: https://updates.suse.com/SUSE/Products/SLE-Product-HPC/15-SP2/x86_64/product/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.628136 #8110] WARN -- : Repository 'SLE-Product-SLES15-SP2-Updates' (689): Error while mirroring metadata: https://updates.suse.com/SUSE/Updates/SLE-Product-SLES/15-SP2/x86_64/update/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.628166 #8110] WARN -- : Repository 'SLE-Product-SLES15-SP2-Pool' (692): Error while mirroring metadata: https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15-SP2/x86_64/product/repodata/repomd.xml - HTTP request failed with code 403.
W, [2021-03-18T14:29:56.628197 #8110] WARN -- : Mirroring completed with errors.

Some information about the system:
NAME="SLES"
VERSION="15-SP1"
VERSION_ID="15.1"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP1"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp1"

I'm using trial SUSE account (so no support) and under customer center I can see my RMT server connected as proxy.
I have also 2 client VMs connected to my RMT and "rmt-cli systems list" shows them but there are no products in the last column.

It looks for some authentication error (http403) but I don't know what can be wrong. Maybe it cached some old credentials and it needs to be erased?
I tried wget to one of the URLs:
suse15repo:/home/ec2-user # wget https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15-SP1/x86_64/product/repodata/repomd.xml
--2021-03-18 14:41:18-- https://updates.suse.com/SUSE/Products/SLE-Product-SLES/15-SP1/x86_64/product/repodata/repomd.xml
Resolving updates.suse.com (updates.suse.com)... 93.184.215.211
Connecting to updates.suse.com (updates.suse.com)|93.184.215.211|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2021-03-18 14:41:18 ERROR 403: Forbidden.

Does it mean trial version account can't download everything?
Checking repo directory, there is almost 200GB of data downloaded...
suse15repo:/home/ec2-user # df -h /var/lib/rmt/public/repo
Filesystem Size Used Avail Use% Mounted on
127.0.0.1:/ 8.0E 187G 8.0E 1% /var/lib/rmt/public/repo

Could someone help me to troubleshoot this issue?
Let me know if you need any additional output, let me know the command and I'll come back with information.

Comments

  • rogerbycekrogerbycek New or Quiet Member

    I had similar issue, but running ** rmt-cli sync** seems to have fixed it.

  • Hi,
    Just for information what was wrong.
    Despite it was downloading some software, the problem was that trial subscription didn't properly link to our test account. Once trail subscription was added to the SCC account by SUSE support, we were able to synchronize everything we needed.
    Thanks.

Sign In or Register to comment.