PDA

View Full Version : Unable to mirror OpenStack 6 Repositories



hamekhan
01-Aug-2016, 12:41
I am following OpenStack 6 deployment guide. When I reach the point where I have to enable mirroring on repositories for SMT server i get "no repository named *"

admin:~ # for REPO in SLES12-SP1-{Pool,Updates} SUSE-OpenStack-Cloud-6-{Pool,Updates}; do smt-repos $REPO sle-12-x86_64 -e; done
1 repository enabled.
1 repository enabled.
no repository named SUSE-OpenStack-Cloud-6-Pool
no repository named SUSE-OpenStack-Cloud-6-Updates

Where as I can see the repos listed when I run smt-repos without any arguments:

| No | 1170 | nu | SUSE-OpenStack-Cloud-6-Debuginfo-Pool | -- | SUSE-OpenStack-Cloud-6-Debuginfo-Pool for | No | No |
| No | 1171 | nu | SUSE-OpenStack-Cloud-6-Debuginfo-Updates | -- | SUSE-OpenStack-Cloud-6-Debuginfo-Updates for | No | No |
| No | 1172 | nu | SUSE-OpenStack-Cloud-6-Pool | -- | SUSE-OpenStack-Cloud-6-Pool for | No | No |
| No | 1173 | nu | SUSE-OpenStack-Cloud-6-Source-Pool | -- | SUSE-OpenStack-Cloud-6-Source-Pool for | No | No |
| No | 1174 | nu | SUSE-OpenStack-Cloud-6-Updates | -- | SUSE-OpenStack-Cloud-6-Updates for | No | No |


What am I missing? Any kind of tip/guidance is really appreciated. Can I skip this part? What will be the impact of skipping this part later on?

Thanks.
--
Regards,
Hameedullah Khan.

eblock
03-Aug-2016, 11:02
Hi,

not sure I can help, but I'll try.
I believe your smt is not setup properly, here is the output of our smt server:


smt-server:~ # smt-repos | grep -i cloud
.------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.
| Mirror? | ID | Type | Name | Target | Description | Can be Mirrored | Staging |
+---------+-----+------+---------------------------------------------+-------------------------+---------------------------------------------------------------+-----------------+---------+
| No | 461 | nu | SLE11-Public-Cloud-Module | sle-11-i586 | SLE11-Public-Cloud-Module for sle-11-i586 | Yes | No |
| No | 462 | nu | SLE11-Public-Cloud-Module | sle-11-ia64 | SLE11-Public-Cloud-Module for sle-11-ia64 | Yes | No |
| No | 463 | nu | SLE11-Public-Cloud-Module | sle-11-ppc64 | SLE11-Public-Cloud-Module for sle-11-ppc64 | Yes | No |
| No | 464 | nu | SLE11-Public-Cloud-Module | sle-11-s390x | SLE11-Public-Cloud-Module for sle-11-s390x | Yes | No |
| No | 465 | nu | SLE11-Public-Cloud-Module | sle-11-x86_64 | SLE11-Public-Cloud-Module for sle-11-x86_64 | Yes | No |
| No | 948 | nu | SUSE-Cloud-1.0-Pool | sle-11-x86_64 | SUSE-Cloud-1.0-Pool for sle-11-x86_64 | Yes | No |
| No | 949 | nu | SUSE-Cloud-1.0-Updates | sle-11-x86_64 | SUSE-Cloud-1.0-Updates for sle-11-x86_64 | Yes | No |
| No | 950 | nu | SUSE-Cloud-2.0-Pool | sle-11-x86_64 | SUSE-Cloud-2.0-Pool for sle-11-x86_64 | Yes | No |
| No | 951 | nu | SUSE-Cloud-2.0-Updates | sle-11-x86_64 | SUSE-Cloud-2.0-Updates for sle-11-x86_64 | Yes | No |
| No | 952 | nu | SUSE-Cloud-3.0-Pool | sle-11-x86_64 | SUSE-Cloud-3.0-Pool for sle-11-x86_64 | Yes | No |
| No | 953 | nu | SUSE-Cloud-3.0-Updates | sle-11-x86_64 | SUSE-Cloud-3.0-Updates for sle-11-x86_64 | Yes | No |
| No | 954 | nu | SUSE-Cloud-4-Pool | sle-11-x86_64 | SUSE-Cloud-4-Pool for sle-11-x86_64 | Yes | No |
| No | 955 | nu | SUSE-Cloud-4-Updates | sle-11-x86_64 | SUSE-Cloud-4-Updates for sle-11-x86_64 | Yes | No |
| Yes | 956 | nu | SUSE-Cloud-5-Pool | sle-11-x86_64 | SUSE-Cloud-5-Pool for sle-11-x86_64 | Yes | No |
| Yes | 957 | nu | SUSE-Cloud-5-Updates | sle-11-x86_64 | SUSE-Cloud-5-Updates for sle-11-x86_64 | Yes | No |


We used an smt-server for the cloud 5 setup, we didn't use it for cloud 6 anymore, but I see several differences between our and your setup. You have no "Target" specified (I believe it's required, it should be created when executing the smt-repos command) and "Can be Mirrored" is always no in your setup. Have you already mirrored your repositories? Is there any content in /srv/www/htdocs/repo/$RCE/SLES12-SP1/sle-12-x86_64/ or a similar directory on your admin node?
Do you have appropriate SCC subscriptions?

Regards,
Eugen