January 2020 - Uyuni Users - openSUSE Mailing Lists

[uyuni-users] Uyuni 2020.01 is released!

by Julio Gonzalez

Hello everyone! We are happy to announce the immediate availability of Uyuni 2020.01 As you can notice, we changed the version schema from X.Y to YYYY.MM. The reason is that this will allow us improve the releasing procedure, it will make things easier for users (as they will not need to change URLs for the repositories in the future), and will avoid mistakes with SUSE Manager versioning, which is using Uyuni as upstream. This means you need to CAREFULLY read the release notes, as they contain instructions for the setup of the new repositories for Server and Proxy that you need to follow before starting with the update. Repositories: - Server: https://download.opensuse.org/repositories/systemsmanagement:/ Uyuni:/Stable/images/repo/Uyuni-Server-POOL-x86_64-Media1/ - Proxy: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/ Stable/images/repo/Uyuni-Proxy-POOL-x86_64-Media1/ - openSUSE Leap 15.* (x86_64): https://download.opensuse.org/repositories/ systemsmanagement:/Uyuni:/Stable:/openSUSE_Leap_15-Uyuni-Client-Tools/ openSUSE_Leap_15.0/ - SLE12 (x86_64, pcc64le, s390x, aarch64): https://download.opensuse.org/ repositories/systemsmanagement:/Uyuni:/Stable:/SLE12-Uyuni-Client-Tools/ SLE_12/ - SLE15 (x86_64, pcc64le, s390x, aarch64): https://download.opensuse.org/ repositories/systemsmanagement:/Uyuni:/Stable:/SLE15-Uyuni-Client-Tools/SLE_15 - CentOS6 (i686, x86_64): https://download.opensuse.org/repositories/ systemsmanagement:/Uyuni:/Stable:/CentOS6-Uyuni-Client-Tools/CentOS_6/ - CentOS7 (x86_64): https://download.opensuse.org/repositories/ systemsmanagement:/Uyuni:/Stable:/CentOS7-Uyuni-Client-Tools/CentOS_7/ - CentOS8 (x86_64): https://download.opensuse.org/repositories/ systemsmanagement:/Uyuni:/Stable:/CentOS8-Uyuni-Client-Tools/CentOS_8/ - Ubuntu 16.04 (x86_64): https://download.opensuse.org/repositories/ systemsmanagement:/Uyuni:/Master:/Ubuntu1604-Uyuni-Client-Tools/xUbuntu_16.04/ - Ubuntu 18.04 (x86_64): https://download.opensuse.org/repositories/ systemsmanagement:/Uyuni:/Master:/Ubuntu1804-Uyuni-Client-Tools/xUbuntu_18.04/ At https://www.uyuni-project.org/stable-version.html you will find all the resources you need to start working with Uyuni 2020.01, including the release notes, documentation, requirements and setup instructions. This is the list of highlights for this release: - Version format change - CentOS8, RHEL 8 and SLES ES 8 support - Monitoring for Ubuntu 18.04, CentOS6, CentOS7 and Proxy. - Prometheus service autodiscovery - Grafana - New Prometheus exporters and formulas - Package Hub - Formulas with forms improvements - CPU mitigation formula - New Content Lifecycle Management filters - Enhanced support for Debian and Ubuntu - Subscription matching in Public Cloud - Preventive shutdown of Server when running out of disk space - Single Page Application UI - Updated documentation - New products enabled (from SCC) - SUSE Container as a Service Platform v4 support Please check the release notes for full details. Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2020.01 We hope you will enjoy Uyuni 2020.01 and invite everyone of you to send us your feedback [1] and of course your patches, if you can contribute. Happy hacking! [1] https://www.uyuni-project.org/contact.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 year, 5 months

1
0
0 0

[uyuni-users] Uyuni at CentOS Dojom FOSDEM and Config Management Camp

by Julio González Gil

Hello! There will be a few Uyuni-related talks and a workshop in Brussels and Ghent this weekend and next week. We will be happy to meet you there! ================================== CENTOS DOJO (31.01.2020, Brussels) ================================== Introduction to Uyuni and using Uyuni to manage CentOS ------------------------------------------------------ Pau Garcia Quiles (Product Owner & Technical Project Manager, SUSE Manager) https://wiki.centos.org/Events/Dojo/Brussels2020 Uyuni is a software-defined infrastructure and configuration management solution. It bootstraps physical servers, creates VMs for virtualization and cloud, deploys and updates packages -even with content lifecycle management features-, builds container images, and tracks what runs on your Kubernetes clusters. All using Salt under the hood. ================================ FOSDEM (01-02.02.2020, Brussels) ================================ Stand ----- https://fosdem.org/2020/stands/ We will be present at the openSUSE booth at building K, Level1. Come visit us! ============================================= CONFIG MANAGEMENT CAMP (03-05.02.2020, Ghent) ============================================= Presenting Yomi --------------- Alberto Planas (Developer, SUSE Future Technologies) https://cfp.cfgmgmtcamp.be/2020/talk/XPFAWX/ Yomi (Yet one more installer) is a new proposal for an OS installer that is build on top of the features that a Software Configuration Tool (StalStack) provides. In this talk we will present the objectives of the projects, the technical decisions done, how it works internally, and an small demo that will present the installation of MicroOS (transactional updates) and a normal openSUSE Tumbleweed with LVM/RAID. Installing dozens of systems with different hardware profiles, services and network configurations can be tricky without a formal approach to the problem. Yomi is a proposal for a new kind of installer that uses the mechanisms provided by your Software Configuration Management tool (in this case SaltStack), to drive in parallel and in unattended fashion the installation of multiple nodes in your network. From a DevOps PoV, this have the advantage that the installation process can be naturally integrated into the more general provisioning workflow, making of the discovery, bootstrap and redeployment of systems a more straightforward task. For a cluster/cloud management PoV (OpenStack, Kubernetes, etc), where the difference on hardware profiles of the nodes implies a different role in the cluster (compute nodes, control plane, storage), this king of installation will delegate decisions like partitioning (RAID, LVM, file system used), software and service configuration to the SCM tool in use. Running Ansible within Salt: Smoothly migrate away from Ansible to Salt ----------------------------------------------------------------------- Pablo Suárez Hernández (Developer, SUSE Manager) https://cfp.cfgmgmtcamp.be/2020/talk/7EUV3A/ At SUSE we firmly believe that Salt is the best choice for Configuration Management and Orchestration. We actively develop and integrate Salt as a core component of some of our products. Sometimes we face customers and users who chose Ansible as their Configuration Management engine. They invested time and efforts designing all states and playbooks to define their infrastructure. Then, at some point, they realize that with Salt they would have the same functionality and much more: real-time monitoring, reactors, event driven orchestration, superior flexibility, and more. The latest Fluorine release of Salt comes with a new module called ansiblegate which has been started by SUSE and allows a user to run Ansible from within Salt. You can execute any Ansible module directly using Salt and you can even reuse your own Ansible playbooks and apply them using Salt! Since many customers and users have invested time designing their Ansible states and playbooks, this session will show how Salt is able to run Ansible using ansiblegate. That will allow users to smoothly migrate away from Ansible by switching to Salt and reusing all their previous Ansible efforts plus adding all extra value that Salt brings into the scene. Manage Virtual Machines like Configuration with Salt ---------------------------------------------------- Cédric Bosdonnat (Developer, SUSE Labs) https://cfp.cfgmgmtcamp.be/2020/talk/HR39GE/ Virtual Machines are live things, but what if I want to manage them just like configuration? Salt helps you doing it by defining the VMs using states. This talk will be showing off how to leverage this feature. The talk will quickly walk through the basics of Salt states before exploring the virt state. Then we will see how Salt uses libvirt to get this done. Since this is also used by Uyuni, the session will provide an insight of a real-life use case. Workshop: Learn configuration management and SDI from scratch using Uyuni ------------------------------------------------------------------------- Pau Garcia Quiles (Product Owner & Technical Project Manager, SUSE Manager) Pablo Suárez Hernández (Developer, SUSE Manager) https://cfp.cfgmgmtcamp.be/2020/talk/FAYVSX/ Uyuni is a software-defined infrastructure and configuration management solution. You can use it to bootstrap physical servers, deploy and update packages and patches -even with content lifecycle management features- create VMs for virtualization and cloud, builds container images, tracks what runs on your Kubernetes clusters, CVE audit your machines and containers, etc. All using Salt under the hood! In this workshop we will start from scratch: install Uyuni, register some clients machines, deploy software, subscribe machine to software channels, learn how to use the content lifecycle management features, create and manage virtual machines, etc. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 year, 5 months

1
0
0 0

Re: [uyuni-users] CentOS clients in Uyuni

by Can Bulut Bayburt

Hi, Already released in 4.0.2, the basic support for "modular repositories" concept of RHEL/CentOS 8 is available. "Basic" means; - You can sync modular repositories - You can register CentOS 8 clients - You can assign the modular repositories to the clients However, modular repository structure hasn't been implemented on the UI level yet, so you cannot do any package operations (update, install, etc.) in the GUI. Doing so would cause wrong updates to be suggested by Uyuni. So at this level of support, you need to do the package operations manually from the client's CLI (dnf). Soon, we'll introduce a more sophisticated way to manage modular repositories via content lifecycle management filters. With this approach, you'll be able to make a selection of preferred modules and create a regular (flattened) repository with your module selections. After these regular repositories are created, you'll be able to use Uyuni as-is with CentOS 8 clients. Hope this helps On 1/27/20 10:39:58 (CET) Haupt, Torsten wrote: > Hey, > what about CentOS 8 as clients in Uyuni? Can I manage this OS? And which > client tools should I user? > > Greets > Torsten -- Can Bulut Bayburt <cbbayburt(a)suse.de> Software Developer, SUSE Manager, R&D SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 year, 6 months

2
1
0 0

[uyuni-users] CentOS clients in Uyuni

by Haupt, Torsten

Hey, what about CentOS 8 as clients in Uyuni? Can I manage this OS? And which client tools should I user? 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 year, 6 months

1
0
0 0

[uyuni-users] Register CentOS in LXC to Uyuni

by Haupt, Torsten

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

1 year, 6 months

2
1
0 0

[uyuni-users] Uyuni and CentOS 8 relation

by Cristian Gherman

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

1 year, 6 months

2
1
0 0

Re: [uyuni-users] no SLES12 products available

by Michael Calmer

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

1 year, 6 months

3
5
0 0

Re: [uyuni-users] Re: mgr-create-bootstrap-repo not offering option for Ubuntu 1804

by Julio González Gil

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 year, 6 months

1
0
0 0

Re: [uyuni-users] Re: mgr-create-bootstrap-repo not offering option for Ubuntu 1804

by Julio González Gil

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 year, 6 months

1
0
0 0

[uyuni-users] mgr-create-bootstrap-repo not offering option for Ubuntu 1804

by Beddingfield, Allen

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

1 year, 6 months

2
2
0 0

2021

2020

2019

2018

Uyuni Users January 2020