we are in the process of setting up a SES cluster and planning on
using Uyuni to deploy SLES12 and provide SLES12+SES5 packages/patches
using traditional client mode to our SES nodes.
I'm trying to create a bootstrap repo but it complains about missing packages:
mgr-create-bootstrap-repo -c SLE-12-SP3-x86_64
ERROR: package 'hwdata' not found
ERROR: package 'libnewt0_52' not found
ERROR: package 'newt' not found
ERROR: package 'salt' not found
ERROR: package 'salt-minion' not found
ERROR: package 'python2-salt' not found
My guess is that I need to setup "Client Tools" for SLE12 but I can't
find anything about that in the documentation.
Do I simply create a new channel with SLES12SP3-Pool as parent and add
as a repository to that channel or?
Have a nice day!
To unsubscribe, e-mail: uyuni-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: uyuni-devel+owner(a)opensuse.org
Hello Uyuni team!
I'm currently writing a Chef cookbook for automating Uyuni test deployments.
After installing Uyuni, the first organization still needs to be created using the web page.
I understand that there is an automation tool spacecmd, but this seems not to work if no organization or admin user exist:
# spacecmd org_create
ERROR: Invalid credentials
I figured out that entering no username/password does not work (also not via the .spacecmd/config file) - so therefore the error message seems legit.
My question is now: how can I automate this? I cannot used the web page in an automated manner.
Is there an option for the /root/setup_env.sh file?
Thanks a lot in advance - also keep up the good work!
First of all, thanks for trying out Uyuni!
I am moving this thread to uyuni-devel since list is supposed to be only for
On jueves, 1 de noviembre de 2018 10:55:38 (CET) Bernd Helber wrote:
> Hi Uyuni Team,
> impressed by the Stability of the Beta Product,
> i tried to give the Upgrade from Beta to Stable a Shot.
> What i did so far...
> 1st removed the Beta Repos
> 2nd added the Uyuni Stable Reps
> 3rd Database Hot Backup from the Existing Installation.
> smdba backup-hot --backup-dir=/var/spacewalk/db-backup
> zypper dup (Vendor got changed succesfully)
> spacewalk-service stop
> Postgres was running as it should be.
> THe issue i had to face covers the Topic Schema Upgrade.
> # spacewalk-schema-upgrade
> Schema upgrade: [susemanager-schema-3.2.10-320.1.2.develHead] ->
> Searching for upgrade path to: [susemanager-schema-4.0.2-1.1]
> Searching for upgrade path to: [susemanager-schema-4.0.2]
> Searching for start path: [susemanager-schema-3.2.10-320.1.2]
> Searching for start path: [susemanager-schema-3.2.10]
> Was not able to find upgrade path in directory
> Do you guys have an Advice for me, to get this fixed?
> With kind regards.
> Bernd Helber
Julio González Gil <jgonzalez(a)suse.com>
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)