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... 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@ua.edu

________________________________________ From: Beddingfield, Allen Sent: Monday, January 13, 2020 10:43 AM To: uyuni-users@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@ua.edu -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com