- ARCHIVED: Uyuni Users

[uyuni-users] Register CentOS in LXC to Uyuni
by Haupt, Torsten 24 Jan '20

24 Jan '20

I want to install some CentOS machines in LX containers (a Proxmox server). Can I register these LXE based machines to Uyuni and manage updates and so on? The repo definitions seems to be the same as in a normal CentOS installation. Greets Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 1

[uyuni-users] Uyuni and CentOS 8 relation
by Cristian Gherman 17 Jan '20

17 Jan '20

Hello, Anybody have tested Uyuni 4.0.2 and CentOS 8? If yes is need some particular settings or just create two main repos ? Thank in advance for any replay. -- Cristian Gherman -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 1

Re: [uyuni-users] no SLES12 products available
by Michael Calmer 16 Jan '20

16 Jan '20

Hi the tag is correct and I think we found the issue. It is an issue in some data we provide via SCC. We look into how to fix it and I hope it will magically work again in the next days. Thanks for the report. Regards Michael Am Dienstag, 14. Januar 2020, 15:58:41 CET schrieb Thomas Weis: > Hi, > > uyuni:~ # cat /usr/share/rhn/config-defaults/rhn_java.conf | grep java.product_tree.tag > java.product_tree.tag = Uyuni > uyuni:~ # > > > > > Am 14.01.2020 um 15:34 schrieb Michael Calmer <mc(a)suse.de>: > > > > Hi > > > > Can you check what value the key "java.product_tree.tag" in > > > > /usr/share/rhn/config-defaults/rhn_java.conf > > > > has? > > > > Am Dienstag, 14. Januar 2020, 13:34:12 CET schrieb Thomas Weis: > >> Hi, > >> > >> the same problem exists with our installation. 4.02 stable. > >> After the initial installation of 4.02, all channels were available, including the SLES12 channels. > >> At some point the SLES12 channels have "disappeared". > >> However, they can still be synchronized > >> > >> Regards > >> Thomas > >> > >> > >>> Am 14.01.2020 um 13:25 schrieb Julio González Gil <jgonzalez(a)suse.com>: > >>> > >>> Hi, > >>> > >>> Master or Stable 4.0.2? > >>> > >>> On martes, 14 de enero de 2020 8:39:52 (CET) Haupt, Torsten wrote: > >>>> Hi, > >>>> > >>>> I can't see any SLES12 products in the setup wizard, just SLES15, RHEL and > >>>> Ubuntu. SCC shows everything from SLES10 to SLES15.1. So I can't add SLES12 > >>>> SP5 at the moment. Any suggestions? > >>>> > >>>> Regards > >>>> Torsten > >>> > >>> > >> > >> > > > > > -- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer(a)suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 5

Re: [uyuni-users] Re: mgr-create-bootstrap-repo not offering option for Ubuntu 1804
by Julio González Gil 14 Jan '20

14 Jan '20

On martes, 14 de enero de 2020 17:08:50 (CET) Beddingfield, Allen wrote: > Yes, replacing that file with the one you suggest gives me the option for > Ubuntu now, as follows: > > uyuni-test01:/tmp # mgr-create-bootstrap-repo --with-custom-channels > 1. centos-7-x86_64 > 2. openSUSE-Leap-15.1-x86_64-uyuni > 3. ubuntu-18.04-amd64-uyuni Good, then the problem will be fixed for the next release, that we expect to have ready by the end of the month. > However, it yields this error: > ---- > Creating bootstrap repo for ubuntu-18.04-amd64-uyuni > > copy 'salt-common-2019.2.0+ds-1.1.all-deb' > copy 'salt-minion-2019.2.0+ds-1.1.all-deb' > Exporting indices... > ERROR: package 'dctrl-tools' not found > ERROR: package 'javascript-common' not found > ERROR: package 'libjs-jquery' not found > ERROR: package 'libjs-sphinxdoc' not found > ERROR: package 'libjs-underscore' not found > ERROR: package 'libnorm1' not found > ERROR: package 'libpgm-5.2-0' not found > ERROR: package 'libpython-stdlib' not found > ERROR: package 'libpython2.7-minimal' not found > ERROR: package 'libpython2.7-stdlib' not found > ERROR: package 'libsodium23' not found > ERROR: package 'libzmq5' not found > ERROR: package 'python' not found > ERROR: package 'python-apt' not found > ERROR: package 'python-asn1crypto' not found > ERROR: package 'python-backports-abc' not found > ERROR: package 'python-certifi' not found > ERROR: package 'python-cffi-backend' not found > ERROR: package 'python-chardet' not found > ERROR: package 'python-concurrent.futures' not found > ERROR: package 'python-croniter' not found > ERROR: package 'python-crypto' not found > ERROR: package 'python-cryptography' not found > ERROR: package 'python-dateutil' not found > ERROR: package 'python-enum34' not found > ERROR: package 'python-idna' not found > ERROR: package 'python-ipaddress' not found > ERROR: package 'python-jinja2' not found > ERROR: package 'python-markupsafe' not found > ERROR: package 'python-minimal' not found > ERROR: package 'python-msgpack' not found > ERROR: package 'python-openssl' not found > ERROR: package 'python-pkg-resources' not found > ERROR: package 'python-psutil' not found > ERROR: package 'python-requests' not found > ERROR: package 'python-singledispatch' not found > ERROR: package 'python-six' not found > ERROR: package 'python-systemd' not found > ERROR: package 'python-tornado' not found > ERROR: package 'python-tz' not found > ERROR: package 'python-urllib3' not found > ERROR: package 'python-yaml' not found > ERROR: package 'python-zmq' not found > ERROR: package 'python2.7' not found > ERROR: package 'python2.7-minimal' not found > ERROR: package 'dmidecode' not found > > Suggestions: > - mgr-create-bootstrap-repo uses the locally synchronized versions of files > from the Tools repository, and uses the locally synchronized pool channel > for dependency resolution. Both should be fully synced before running the > mgr-create-bootstrap-repo script. > ---- > > My channels look like this: > ubuntu-18.04-pool-amd64-uyuni > --ubuntu-1804-amd64-uyuni-client > > ubuntu-18.04-pool-amd64 > --ubuntu-1804-amd64-main > --ubuntu-1804-amd64-main-security > --ubuntu-1804-amd64-main-updates > --ubuntu-1804-amd64-main-universe > > It appears that the missing packages are found in ubuntu-1804-amd64-main, > which is under ubuntu-18.04-pool-amd64. Am I needing to sync the -uyuni > channels for this? Maybe I misunderstood your explanation for the two sets > of channels? Remove the last set (ubuntu-18.04-pool-amd64 and children) as that set is the one for SUSE Manager, and not for Uyuni. Also you are missing children for ubuntu-18.04-pool-amd64-uyuni (this is basically an empty channel). Having the client tools (ubuntu-1804-amd64-uyuni- client) is not enough Run: > spacewalk-common-channels \ > ubuntu-1804-amd64-main-uyuni \ > ubuntu-1804-amd64-main-updates-uyuni \ > ubuntu-1804-amd64-main-security-uyuni \ > ubuntu-1804-amd64-universe-uyuni \ > ubuntu-1804-amd64-universe-updates-uyuni This will add the main and universe channels (including updates, with security for main as well). All of them are required, including universe. Then launch the sync for the repositories in the child channels of ubuntu-18.04-pool-amd64-uyuni And finally launch: > mgr-create-bootstrap-repo --with-custom-channels With that, the bootstrap creation should work fine. > Thanks. > Allen B. > > -- > Allen Beddingfield > Systems Engineer > Office of Information Technology > The University of Alabama > Office 205-348-2251 > allen(a)ua.edu > <https://www.ua.edu/> > > ________________________________ > From: Julio González Gil > Sent: Tuesday, January 14, 2020 9:52 AM > To: Beddingfield, Allen > Cc: uyuni-users(a)opensuse.org; cbbayburt(a)suse.de > Subject: Re: [uyuni-users] Re: mgr-create-bootstrap-repo not offering option > for Ubuntu 1804 > On martes, 14 de enero de 2020 16:42:47 (CET) Beddingfield, Allen wrote: > > My file has this: > > }, > > 'ubuntu-16.04-amd64' : { > > > > 'PDID' : [-2, 1917], 'PKGLIST' : PKGLISTUBUNTU1604, > > 'DEST' : > > '/srv/www/htdocs/pub/repositories/ubuntu/16/4/bootstrap/', > > 'TYPE' : 'deb' > > > > }, > > 'ubuntu-18.04-amd64' : { > > > > 'PDID' : [-1, 1918], 'PKGLIST' : PKGLISTUBUNTU1804, > > 'DEST' : > > '/srv/www/htdocs/pub/repositories/ubuntu/18/4/bootstrap/', > > 'TYPE' : 'deb' > > > > } > > > > The ACTUAL base channel is named: "ubuntu-18.04-pool-amd64". The main, > > main security, main updates, and universe channels are below it. There is > > NO "client tools" channel there. There is another base channel named > > "ubuntu-18.04-pool-amd64-uyuni", and the client tools repo is under it. > > So > > it is under a completely different base channel. > > > > You mentioned that I should not sync the -uyuni channels, but that is the > > only place where the client tools repo exists. Should I try syncing down > > the -uyuni channels, then modifying the config file to use > > "ubuntu-18.04-pool-amd64-uyuni" for the base channel? > > No, not really, I wrote: > > Those without "-uyuni" can be ignored in your case (they are intended > > for SUSE Manager). > > "ubuntu-18.04-pool-amd64" doesn't have client tools as a child because > for SUSE Manager those are SUSE products . But again: that's not what you > want for Uyuni. > > The reason you have the file contents you described above is that you are on > 4.0.2 (while I was wrongly looking at master) > > This is from 4.0.2: > https://github.com/uyuni-project/uyuni/blob/Uyuni-4.0.2/susemanager/src/mgr_ > bootstrap_data.py > > While this is from master: > https://github.com/uyuni-project/uyuni/blob/master/susemanager/src/mgr_boots > trap_data.py > > So in short: try the following: > > 1. Backup /usr/share/susemanager/mgr_bootstrap_data.py > 2. Download > https://github.com/uyuni-project/uyuni/blob/master/susemanager/src/mgr_boot > strap_data.py and copy it to /usr/share/susemanager/mgr_bootstrap_data.py > 3. Try "mgr-create-bootstrap-repo --with-custom-channels" > > That should work. If not, ping me again, and maybe I will ask you to do the > replacements I asked before :-) > > > Allen B. > > > > -- > > Allen Beddingfield > > Systems Engineer > > Office of Information Technology > > The University of Alabama > > Office 205-348-2251 > > allen(a)ua.edu > > <https://www.ua.edu/> > > > > ________________________________ > > From: Julio González Gil > > Sent: Tuesday, January 14, 2020 7:27 AM > > To: uyuni-users(a)opensuse.org > > Cc: Beddingfield, Allen; cbbayburt(a)suse.de > > Subject: Re: [uyuni-users] Re: mgr-create-bootstrap-repo not offering > > option for Ubuntu 1804 > > > > Those without "-uyuni" can be ignored in your case (they are intended > > for SUSE Manager). > > > > For me, this seems to be a bug at the bootstrap creator script not > > being able to detect ubuntu-1804-pool-amd64-uyuni as the base channel. > > > > Having a quick look, I'd say this is a bug at > > https://github.com/uyuni-project/uyuni/blob/master/susemanager/src/mgr_boo > > ts trap_data.py as the base channels fur Uyuni do have a dot in the > > version. > > > > Let's try the following: create a backup of > > /usr/share/susemanager/mgr_bootstrap_data.py > > > > Then change: > > 'BASECHANNEL' : 'ubuntu-16.04-pool-amd64-uyuni', 'PKGLIST' : > > PKGLISTUBUNTU1604, > > > > To: > > 'BASECHANNEL' : 'ubuntu-1604-pool-amd64-uyuni', 'PKGLIST' : > > PKGLISTUBUNTU1604, > > > > And: > > 'BASECHANNEL' : 'ubuntu-18.04-pool-amd64-uyuni', 'PKGLIST' : > > PKGLISTUBUNTU1804, > > > > To: > > 'BASECHANNEL' : 'ubuntu-1804-pool-amd64-uyuni', 'PKGLIST' : > > PKGLISTUBUNTU1804, > > > > Finally, try to rerun "mgr-create-bootstrap-repo --with-custom-channels" > > and let us know the results. > > > > On lunes, 13 de enero de 2020 20:48:24 (CET) Beddingfield, Allen wrote: > > > I am using version 4.0.2 > > > > > > I think I may have uncovered something that could be causing this. > > > If you do "spacewalk-common-channels -l" there are two sets of repos for > > > Ubuntu. ubuntu-1804-amd64-main: amd64-deb > > > > > > ubuntu-1804-amd64-main-security: amd64-deb > > > ubuntu-1804-amd64-main-security-uyuni: amd64-deb > > > ubuntu-1804-amd64-main-updates: amd64-deb > > > ubuntu-1804-amd64-main-updates-uyuni: amd64-deb > > > ubuntu-1804-amd64-main-uyuni: amd64-deb > > > ubuntu-1804-amd64-universe: amd64-deb > > > ubuntu-1804-amd64-universe-uyuni: amd64-deb > > > ubuntu-1804-amd64-uyuni-client: amd64-deb > > > ubuntu-1804-amd64-uyuni-client-devel: amd64-deb > > > ubuntu-1804-pool-amd64: amd64-deb > > > ubuntu-1804-pool-amd64-uyuni: amd64-deb > > > > > > Notice that some have "-uyuni" appended to the name, and some do not. > > > I was able to add all of those originally, and received an error with > > > the > > > others. I just went through and retried those without "-uyuni", and this > > > channel actually added this time: ubuntu-1804-pool-amd64 It also > > > created > > > the "main", "main security", and "main updates" beneath it. > > > > > > Which set of these repositories am I supposed to actually add and sync? > > > Why are there two? > > > > > > > > > > > > -- > > > Allen Beddingfield > > > Systems Engineer > > > Office of Information Technology > > > The University of Alabama > > > Office 205-348-2251 > > > allen(a)ua.edu > > > > > > > > > ________________________________________ > > > From: Beddingfield, Allen <allen(a)ua.edu> > > > Sent: Monday, January 13, 2020 10:43 AM > > > To: uyuni-users(a)opensuse.org > > > Subject: [uyuni-users] mgr-create-bootstrap-repo not offering option for > > > Ubuntu 1804 > > > > > > I have added the following channels with spacewalk-common-channels, > > > fully > > > synced them, and scheduled daily syncs for them. That is all working as > > > expected. > > > > > > ubuntu-1804-amd64-main-security-uyuni: amd64-deb > > > ubuntu-1804-amd64-main-updates-uyuni: amd64-deb > > > ubuntu-1804-amd64-main-uyuni: amd64-deb > > > ubuntu-1804-amd64-universe-uyuni: amd64-deb > > > ubuntu-1804-amd64-uyuni-client: amd64-deb > > > ubuntu-1804-amd64-uyuni-client-devel: amd64-deb > > > ubuntu-1804-pool-amd64-uyuni: amd64-deb > > > > > > When I run "mgr-create-bootstrap-repo --with-custom-channels", the > > > option > > > does not exist for creating a bootstrap repo for Ubutu 1804. It DOES > > > exist > > > for CentOS 7.x and openSUSE Leap 15.1. Here is a copy/paste of what I > > > see: > > > uyuni-test01:~ # mgr-create-bootstrap-repo --with-custom-channels > > > 1. centos-7-x86_64 > > > 2. openSUSE-Leap-15.1-x86_64 > > > Enter a number of a product label: > > > > > > Any ideas of where to begin troubleshooting this? > > > Thanks. > > > Allen B. > > > > > > > > > -- > > > Allen Beddingfield > > > Systems Engineer > > > Office of Information Technology > > > The University of Alabama > > > Office 205-348-2251 > > > allen(a)ua.edu > > > -- > > > To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org > > > To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org > > > > -- > > Julio González Gil > > Release Engineer, SUSE Manager and Uyuni > > jgonzalez(a)suse.com > > -- > Julio González Gil > Release Engineer, SUSE Manager and Uyuni > jgonzalez(a)suse.com -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

Re: [uyuni-users] Re: mgr-create-bootstrap-repo not offering option for Ubuntu 1804
by Julio González Gil 14 Jan '20

14 Jan '20

On martes, 14 de enero de 2020 16:42:47 (CET) Beddingfield, Allen wrote: > My file has this: > > }, > 'ubuntu-16.04-amd64' : { > 'PDID' : [-2, 1917], 'PKGLIST' : PKGLISTUBUNTU1604, > 'DEST' : '/srv/www/htdocs/pub/repositories/ubuntu/16/4/bootstrap/', > 'TYPE' : 'deb' > }, > 'ubuntu-18.04-amd64' : { > 'PDID' : [-1, 1918], 'PKGLIST' : PKGLISTUBUNTU1804, > 'DEST' : '/srv/www/htdocs/pub/repositories/ubuntu/18/4/bootstrap/', > 'TYPE' : 'deb' > } > > > The ACTUAL base channel is named: "ubuntu-18.04-pool-amd64". The main, > main security, main updates, and universe channels are below it. There is > NO "client tools" channel there. There is another base channel named > "ubuntu-18.04-pool-amd64-uyuni", and the client tools repo is under it. So > it is under a completely different base channel. > > You mentioned that I should not sync the -uyuni channels, but that is the > only place where the client tools repo exists. Should I try syncing down > the -uyuni channels, then modifying the config file to use > "ubuntu-18.04-pool-amd64-uyuni" for the base channel? No, not really, I wrote: > Those without "-uyuni" can be ignored in your case (they are intended > for SUSE Manager). "ubuntu-18.04-pool-amd64" doesn't have client tools as a child because for SUSE Manager those are SUSE products . But again: that's not what you want for Uyuni. The reason you have the file contents you described above is that you are on 4.0.2 (while I was wrongly looking at master) This is from 4.0.2: https://github.com/uyuni-project/uyuni/blob/Uyuni-4.0.2/susemanager/src/mgr… While this is from master: https://github.com/uyuni-project/uyuni/blob/master/susemanager/src/mgr_boot… So in short: try the following: 1. Backup /usr/share/susemanager/mgr_bootstrap_data.py 2. Download https://github.com/uyuni-project/uyuni/blob/master/susemanager/src/mgr_boot… and copy it to /usr/share/susemanager/mgr_bootstrap_data.py 3. Try "mgr-create-bootstrap-repo --with-custom-channels" That should work. If not, ping me again, and maybe I will ask you to do the replacements I asked before :-) > Allen B. > > -- > Allen Beddingfield > Systems Engineer > Office of Information Technology > The University of Alabama > Office 205-348-2251 > allen(a)ua.edu > <https://www.ua.edu/> > > ________________________________ > From: Julio González Gil > Sent: Tuesday, January 14, 2020 7:27 AM > To: uyuni-users(a)opensuse.org > Cc: Beddingfield, Allen; cbbayburt(a)suse.de > Subject: Re: [uyuni-users] Re: mgr-create-bootstrap-repo not offering option > for Ubuntu 1804 > > Those without "-uyuni" can be ignored in your case (they are intended > for SUSE Manager). > > For me, this seems to be a bug at the bootstrap creator script not > being able to detect ubuntu-1804-pool-amd64-uyuni as the base channel. > > Having a quick look, I'd say this is a bug at > https://github.com/uyuni-project/uyuni/blob/master/susemanager/src/mgr_boots > trap_data.py as the base channels fur Uyuni do have a dot in the version. > > Let's try the following: create a backup of > /usr/share/susemanager/mgr_bootstrap_data.py > > Then change: > > 'BASECHANNEL' : 'ubuntu-16.04-pool-amd64-uyuni', 'PKGLIST' : > PKGLISTUBUNTU1604, > > To: > > 'BASECHANNEL' : 'ubuntu-1604-pool-amd64-uyuni', 'PKGLIST' : > PKGLISTUBUNTU1604, > > And: > > 'BASECHANNEL' : 'ubuntu-18.04-pool-amd64-uyuni', 'PKGLIST' : > PKGLISTUBUNTU1804, > > To: > > 'BASECHANNEL' : 'ubuntu-1804-pool-amd64-uyuni', 'PKGLIST' : > PKGLISTUBUNTU1804, > > Finally, try to rerun "mgr-create-bootstrap-repo --with-custom-channels" and > let us know the results. > > On lunes, 13 de enero de 2020 20:48:24 (CET) Beddingfield, Allen wrote: > > I am using version 4.0.2 > > > > I think I may have uncovered something that could be causing this. > > If you do "spacewalk-common-channels -l" there are two sets of repos for > > Ubuntu. ubuntu-1804-amd64-main: amd64-deb > > > > ubuntu-1804-amd64-main-security: amd64-deb > > ubuntu-1804-amd64-main-security-uyuni: amd64-deb > > ubuntu-1804-amd64-main-updates: amd64-deb > > ubuntu-1804-amd64-main-updates-uyuni: amd64-deb > > ubuntu-1804-amd64-main-uyuni: amd64-deb > > ubuntu-1804-amd64-universe: amd64-deb > > ubuntu-1804-amd64-universe-uyuni: amd64-deb > > ubuntu-1804-amd64-uyuni-client: amd64-deb > > ubuntu-1804-amd64-uyuni-client-devel: amd64-deb > > ubuntu-1804-pool-amd64: amd64-deb > > ubuntu-1804-pool-amd64-uyuni: amd64-deb > > > > Notice that some have "-uyuni" appended to the name, and some do not. > > I was able to add all of those originally, and received an error with the > > others. I just went through and retried those without "-uyuni", and this > > channel actually added this time: ubuntu-1804-pool-amd64 It also created > > the "main", "main security", and "main updates" beneath it. > > > > Which set of these repositories am I supposed to actually add and sync? > > Why are there two? > > > > > > > > -- > > Allen Beddingfield > > Systems Engineer > > Office of Information Technology > > The University of Alabama > > Office 205-348-2251 > > allen(a)ua.edu > > > > > > ________________________________________ > > From: Beddingfield, Allen <allen(a)ua.edu> > > Sent: Monday, January 13, 2020 10:43 AM > > To: uyuni-users(a)opensuse.org > > Subject: [uyuni-users] mgr-create-bootstrap-repo not offering option for > > Ubuntu 1804 > > > > I have added the following channels with spacewalk-common-channels, fully > > synced them, and scheduled daily syncs for them. That is all working as > > expected. > > > > ubuntu-1804-amd64-main-security-uyuni: amd64-deb > > ubuntu-1804-amd64-main-updates-uyuni: amd64-deb > > ubuntu-1804-amd64-main-uyuni: amd64-deb > > ubuntu-1804-amd64-universe-uyuni: amd64-deb > > ubuntu-1804-amd64-uyuni-client: amd64-deb > > ubuntu-1804-amd64-uyuni-client-devel: amd64-deb > > ubuntu-1804-pool-amd64-uyuni: amd64-deb > > > > When I run "mgr-create-bootstrap-repo --with-custom-channels", the option > > does not exist for creating a bootstrap repo for Ubutu 1804. It DOES > > exist > > for CentOS 7.x and openSUSE Leap 15.1. Here is a copy/paste of what I > > see: > > uyuni-test01:~ # mgr-create-bootstrap-repo --with-custom-channels > > 1. centos-7-x86_64 > > 2. openSUSE-Leap-15.1-x86_64 > > Enter a number of a product label: > > > > Any ideas of where to begin troubleshooting this? > > Thanks. > > Allen B. > > > > > > -- > > Allen Beddingfield > > Systems Engineer > > Office of Information Technology > > The University of Alabama > > Office 205-348-2251 > > allen(a)ua.edu > > -- > > To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org > > To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org > > -- > Julio González Gil > Release Engineer, SUSE Manager and Uyuni > jgonzalez(a)suse.com -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

[uyuni-users] mgr-create-bootstrap-repo not offering option for Ubuntu 1804
by Beddingfield, Allen 14 Jan '20

14 Jan '20

I have added the following channels with spacewalk-common-channels, fully synced them, and scheduled daily syncs for them. That is all working as expected. ubuntu-1804-amd64-main-security-uyuni: amd64-deb ubuntu-1804-amd64-main-updates-uyuni: amd64-deb ubuntu-1804-amd64-main-uyuni: amd64-deb ubuntu-1804-amd64-universe-uyuni: amd64-deb ubuntu-1804-amd64-uyuni-client: amd64-deb ubuntu-1804-amd64-uyuni-client-devel: amd64-deb ubuntu-1804-pool-amd64-uyuni: amd64-deb When I run "mgr-create-bootstrap-repo --with-custom-channels", the option does not exist for creating a bootstrap repo for Ubutu 1804. It DOES exist for CentOS 7.x and openSUSE Leap 15.1. Here is a copy/paste of what I see: uyuni-test01:~ # mgr-create-bootstrap-repo --with-custom-channels 1. centos-7-x86_64 2. openSUSE-Leap-15.1-x86_64 Enter a number of a product label: Any ideas of where to begin troubleshooting this? Thanks. Allen B. -- Allen Beddingfield Systems Engineer Office of Information Technology The University of Alabama Office 205-348-2251 allen(a)ua.edu -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 2

[uyuni-users] no SLES12 products available
by Haupt, Torsten 14 Jan '20

14 Jan '20

Hi, I can't see any SLES12 products in the setup wizard, just SLES15, RHEL and Ubuntu. SCC shows everything from SLES10 to SLES15.1. So I can't add SLES12 SP5 at the moment. Any suggestions? Regards Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

4 5

Re: [uyuni-users] spacecmd: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 1: ordinal not in range(128)
by Torsten haupt 14 Jan '20

14 Jan '20

> On 24.09.19 13:55, Haupt, Torsten wrote: > > Hi, > > > > the output is > > i | Uyuni Server Stable | spacecmd > > | 4.0.12-400.1.1.uyunimaster | noarch > > > > > > > >> -----Original Message----- > >> From: Michele Bologna [mailto:mbologna@suse.de] > >> Sent: Tuesday, September 24, 2019 1:29 PM > >> To: uyuni-users(a)opensuse.org > >> Subject: [EXTERN] Re: [uyuni-users] spacecmd: UnicodeDecodeError: 'ascii' > >> codec can't decode byte 0xe3 in position 1: ordinal not in range(128) > >> > >> On 20/09/2019, at 07:47, Haupt, Torsten wrote: > >>> Hello, > >>> > >>> the spacecmd command doesn't work anymore on my uyuni server. I get > >> the following error: > >> > >> Can you please share the spacecmd version you are running? > >> > >> Example: > >> > >> # zypper pa -i | grep -i spacecmd > >> i | Uyuni builds from master branch | spacecmd > >> | 4.0.12-410.29.1.uyunimaster | noarch > >> i | Uyuni-Master-x86_64-Pool | spacecmd > >> | 4.0.12-410.29.1.uyunimaster | noarch > > > Hi! > > Since we write with "wb" and read with "rb", I don't think this should happen. Is > the locale set to something with UTF-8? > Hi, spacecmd still doesn't work; same error. smduyuni:~ # localectl System Locale: LC_CTYPE=de_DE.UTF-8 VC Keymap: de-nodeadkeys X11 Layout: n/a Should I change the locale configuration? Which locale should i use? Greets Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 0

[uyuni-users] Uyuni 4.02, repositories from SCC are only partially displayed
by Thomas Weis 13 Jan '20

13 Jan '20

Hello everyone, I am new here and not sure if this is the right way to look for help. I successfully installed the current Uyuni stable version, after the initial setup all SLES repositories available in the SCC were shown in the first overview and I was able to successfully synchronize all repos. For reasons not yet known to me, however, I am now not shown any SLES12 repositories. However, I can manually synchronize all SLES12 repositories whose regular sync intervals I originally set up with spacewalk-repo-sync. The nightly reposyncs are successful. My question now is, how can I display all channels and repositories that are actually available to me in the SCC in the Uyuni server, is there a "reset" or something similar? Here is a link for some Printscreens, hope, that is allowed? (please wait some seconds and then click“als Gast beitreten“) https://share.ntw-datentechnik.de/ssf/a/c/p_name/ss_forum/p_action/1/binder… lot of Thanks for your support Regards Thomas -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 1

[uyuni-users] Cobbler system add fails with exception
by Strahil Nikolov 01 Dec '19

01 Dec '19

Hello Community, I'm trying to setup a fully automated deployment with Uyuni and cobbler, but it seems that there is something wrong with my setup. When I run 'uyuni:/etc/cobbler # cobbler system add --help' Traceback (most recent call last): File "/usr/bin/cobbler", line 35, in <module> sys.exit(app.main()) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 745, in main rc = cli.run(sys.argv) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 358, in run self.object_command(object_type, object_action) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 428, in object_command network_interface_fields, settings, object_action) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 238, in add_options_from_fields _add_parser_option_from_field(parser, field, settings) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 209, in _add_parser_option_from_field raise Exception("field %s default value (%s) is not listed in choices (%s)" % (name, default, str(choices))) Exception: field redhat_management_key default value (<<inherit>>) is not listed in choices (str) I got a traceback that 'redhat_management_key' default value is not listed in choices. My guess is that this should not happen,but my python skills are quite limited. As I have a separate NIC (separate VLAN) for the Uyuni's cobbler, I wanted to be able to pass in kickstart/autoyast 's script the network settings (via system variables) before powering off the machine. Then an automated process will change the VLAN (and PXE boot) of the client's NIC and will start it up. Once it's available, it will be bootstrapped and additional configuration can be done on the permanent address. Also, it seems that bootstrapping RHEL 7 via cobbler is failing, so that cannot be done during initial deployment. Most probably the 'spacewalk/redhat_register' snippet has an issue and cobbler is not expanding the it. Thanks for reading such a long post and any help is appreciated, maybe there is already a fix. If not - I can provide details in an issue. Best Regards, Strahil Nikolov -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 1