PDA

View Full Version : Storage-4-Pool (Wrong Repository)



morgan666
05-Apr-2018, 09:54
Hello Guys,
I'm deploying SUSE OpenStack Cloud in my own test lab, I downloaded Storage 4 DVD1 and copied to "/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Pool" using rsync, but I've got "Wrong Repository" with Storage 4 Pool.
Any help?
Thanks,

smflood
05-Apr-2018, 22:35
morgan666 Wrote in message:

> I'm deploying *SUSE OpenStack Cloud* in my own test lab, I downloaded
> *Storage 4 DVD1* and copied to
> "/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Pool"
> using *rsync*, but I've got "Wrong Repository" with Storage 4 Pool.
> Any help?

Presumably you are using SUSE OpenStack Cloud 7?

What was the exact rsync command you used? Please can you post the
out from
'ls /srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4
-Pool'.

HTH.
--
Simon Flood
SUSE Knowledge Partner


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

morgan666
10-Apr-2018, 09:32
Thank you for the reply,
1- Yes, I'm using SOC7.
2- The output:

soc7-admin:~ # ls -la /srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Pool
total 2524
dr-xr-xr-x 6 root root 4096 Nov 22 2016 .
drwxr-xr-x 6 root root 79 Apr 10 04:07 ..
-r--r--r-- 1 root root 649877 Nov 22 2016 ARCHIVES.gz
-r--r--r-- 1 root root 17992 Nov 19 2016 COPYING
-r--r--r-- 1 root root 25733 Nov 19 2016 COPYING.de
-r--r--r-- 1 root root 1455 Nov 19 2016 COPYRIGHT
-r--r--r-- 1 root root 1620 Nov 19 2016 COPYRIGHT.de
-r--r--r-- 1 root root 1704402 Nov 22 2016 ChangeLog
-r--r--r-- 1 root root 5050 Nov 22 2016 INDEX.gz
-r--r--r-- 1 root root 8470 Nov 19 2016 NEWS
-r--r--r-- 1 root root 1230 Sep 26 2016 README
dr-xr-xr-x 2 root root 28 Nov 22 2016 boot
-r--r--r-- 1 root root 3359 Nov 22 2016 content
-r--r--r-- 1 root root 481 Nov 22 2016 content.asc
-r--r--r-- 1 root root 972 Nov 22 2016 content.key
-r--r--r-- 1 root root 246 Nov 22 2016 directory.yast
dr-xr-xr-x 2 root root 119 Nov 22 2016 docu
-r--r--r-- 1 root root 955 Nov 19 2016 gpg-pubkey-39db7c82-510a966b.asc
-r--r--r-- 1 root root 975 Nov 19 2016 gpg-pubkey-50a3dd1c-50f35137.asc
-r--r--r-- 1 root root 96254 Nov 19 2016 license.tar.gz
-r--r--r-- 1 root root 8964 Nov 22 2016 ls-lR.gz
dr-xr-xr-x 2 root root 110 Nov 22 2016 media.1
-r--r--r-- 1 root root 1288 Nov 19 2016 pubring.gpg
dr-xr-xr-x 7 root root 74 Nov 22 2016 suse

This is the same content copied from SUSE-Enterprise-Storage-4-DVD-x86_64-GM-DVD1.iso.

morgan666
10-Apr-2018, 14:07
It solved by adding a custom directory under "repos", and Crowbar setup. Now the custom repository for Storage-4 shows OK.
But I got another issue "The SUSE Enterprise Storage repositories have not been setup.", when deploying Ceph.

smflood
10-Apr-2018, 17:44
On 10/04/18 09:34, morgan666 wrote:

> Thank you for the reply,
> 1- Yes, I'm using SOC7.
> 2- The output:
> Code:
> --------------------
>
> soc7-admin:~ # ls -la /srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Pool
> total 2524
> dr-xr-xr-x 6 root root 4096 Nov 22 2016 .
> drwxr-xr-x 6 root root 79 Apr 10 04:07 ..
> -r--r--r-- 1 root root 649877 Nov 22 2016 ARCHIVES.gz
> -r--r--r-- 1 root root 17992 Nov 19 2016 COPYING
> -r--r--r-- 1 root root 25733 Nov 19 2016 COPYING.de
> -r--r--r-- 1 root root 1455 Nov 19 2016 COPYRIGHT
> -r--r--r-- 1 root root 1620 Nov 19 2016 COPYRIGHT.de
> -r--r--r-- 1 root root 1704402 Nov 22 2016 ChangeLog
> -r--r--r-- 1 root root 5050 Nov 22 2016 INDEX.gz
> -r--r--r-- 1 root root 8470 Nov 19 2016 NEWS
> -r--r--r-- 1 root root 1230 Sep 26 2016 README
> dr-xr-xr-x 2 root root 28 Nov 22 2016 boot
> -r--r--r-- 1 root root 3359 Nov 22 2016 content
> -r--r--r-- 1 root root 481 Nov 22 2016 content.asc
> -r--r--r-- 1 root root 972 Nov 22 2016 content.key
> -r--r--r-- 1 root root 246 Nov 22 2016 directory.yast
> dr-xr-xr-x 2 root root 119 Nov 22 2016 docu
> -r--r--r-- 1 root root 955 Nov 19 2016 gpg-pubkey-39db7c82-510a966b.asc
> -r--r--r-- 1 root root 975 Nov 19 2016 gpg-pubkey-50a3dd1c-50f35137.asc
> -r--r--r-- 1 root root 96254 Nov 19 2016 license.tar.gz
> -r--r--r-- 1 root root 8964 Nov 22 2016 ls-lR.gz
> dr-xr-xr-x 2 root root 110 Nov 22 2016 media.1
> -r--r--r-- 1 root root 1288 Nov 19 2016 pubring.gpg
> dr-xr-xr-x 7 root root 74 Nov 22 2016 suse
> --------------------
>
>
> This is the same content copied from
> *SUSE-Enterprise-Storage-4-DVD-x86_64-GM-DVD1.iso*.

So the thing to remember is that the Product Media repositories are
different to the Update and Pool repositories.

Product Media repositories are created as per section 5.1 of the
Deployment Guide[1] and involve copying the contents of the SLES12 SP2
and SOC7 DVDs/ISOs to directories under /srv/tftpboot/suse-12.2/x86_64/.

Update and Pool repositories are expected to be hosted on a SMT or SUSE
Manager server, with SMT possibly hosted on the Administration Server.
If SMT or SUSE Manager is not an option you can create fake repositories
on the Admin Server although this is unsupported.

Repos, real or fake, have a particular directory structure and are not
simply copies of DVDs/ISOs hence the reason this isn't working. The
following is based on a Getting Started with SUSE OpenStack Cloud 6
presentation I gave at SUSECON 2016[2]:

# mount SES4 DVD1
mount /dev/dvd /mnt/
# create
/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Pool
structure
mkdir -p
/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Pool/rpm
# copy packages from SES4 DVD
rsync -avP /mnt/suse/{noarch,x86_64}
/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Pool/rpm/
# unmount DVD
umount /mnt
# create a fake repo
createrepo
/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Pool/

# create
/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Updates
structure
mkdir -p
/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Updates/rpm
# create empty fake repo
createrepo
/srv/tftpboot/suse-12.2/x86_64/repos/SUSE-Enterprise-Storage-4-Updates/

Once this done Crowbar should find the fake SES4 repos without needing
to change to custom and then the install should find them to install Ceph.

HTH.

[1]
https://www.suse.com/documentation/suse-openstack-cloud-7/book_cloud_deploy/data/sec_depl_adm_conf_repos_product.html
[2]
https://www.suse.com/media/presentation/TUT88917_getting_started_with_suse_openstack_cloud _6.pdf
--
Simon
SUSE Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

smflood
10-Apr-2018, 17:45
On 10/04/18 14:14, morgan666 wrote:

> It solved by adding a custom directory under "repos", and Crowbar setup.
> Now the custom repository for Storage-4 shows *OK*.
> But I got another issue *"The SUSE Enterprise Storage repositories have
> not been setup."*, when deploying Ceph.

This new issue is due to the repos having different names to what is
expected. Please see my other reply on how to create fake SES4 repos.

HTH.
--
Simon
SUSE Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

morgan666
11-Apr-2018, 10:36
Thank you,
Very helpful, and it worked perfectly.
What I missed "createrepo", additionally I commented out "repo md" section for storage 4 pool/updates in "/opt/dell/crowbar_framework/config/repos-cloud.yml".
Again, thank you so much.

smflood
11-Apr-2018, 16:37
On 11/04/18 10:44, morgan666 wrote:

> Thank you,
> Very helpful, and it worked perfectly.

Great! I'll admit I've not yet tried installing SES4 when installing
SOC7 within an isolated virtual environment so was adapting my previous
SOC6 workings.

> What I missed "createrepo", additionally I commented out "repo md"
> section for storage 4 pool/updates in
> "/opt/dell/crowbar_framework/config/repos-cloud.yml".
> Again, thank you so much.

No problem. Sorry forgot about commenting out the repo-md sections but
glad you figured that out and that the trick still works!

HTH.
--
Simon
SUSE Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------