April 2021 - ARCHIVED: Uyuni Users - openSUSE Mailing Lists

[uyuni-users] Fresh Install uyuni 2020.05 Error generating bootstrap repo
by Thomas Weis 24 Aug '22

24 Aug '22

Hello everyone we are configuring a fresh installation of Uyuni 2020.05 After a successful reposync of SUSE Linux Enterprise Server 15 SP1 x86_64 we get an error message: Type: Creating Bootstrap Repository failed Summary: Error generating bootstrap repo for: SLE-15-SP1-x86_64 show details said: ERROR: package 'hwdata' not found ERROR: package 'python3-hwdata' not found ERROR: package 'python3-rhnlib' not found ERROR: package 'spacewalk-check' not found ERROR: package 'spacewalk-client-setup' not found ERROR: package 'spacewalk-client-tools' not found ERROR: package 'python3-spacewalk-check' not found ERROR: package 'python3-spacewalk-client-setup' not found ERROR: package 'python3-spacewalk-client-tools' not found ERROR: package 'python3-uyuni-common-libs' not found ERROR: none of 'mgr-daemon', 'spacewalksd' found ERROR: package 'suseRegisterInfo' not found ERROR: package 'python3-suseRegisterInfo' not found ERROR: package 'zypp-plugin-spacewalk' not found ERROR: package 'python3-zypp-plugin-spacewalk' not found The installation was error-free, we proceeded exactly according to the documentation. What is our mistake? thanks for suggestions Regards Thomas-- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 2

Suma feedback / potentital enh requests
by J-M Roth 02 May '21

02 May '21

Hello, We've been in contact with our Suse Account Team after evaluating and getting a Suma subscription to show our support. First, congrats, the product seems pretty stable, usability is high (GUI is very reactive), it is well-integrated with Saltstack while at the same time providing interfaces for customization. Concerning potential feedback and enhancement requests they told us to come here. So here is my current list: * VERY DANGEROUS: Using groups: It is not clear from the system view that a state/config channel is applied to a system via a group. If a system is managed through a group, that should be made clear on the Systems > system > Configuration > Overview screen and also Systems > system > States > Configuration Channels screen of that individual system. This is _very_ dangerous because applying a highstate might do unexpected things since the system is mostly invisibly part of a group. In the same way, Configuration > Channels > channel > Systems does not show that the currently selected channel applies to any group (or a list of systems expanded from the group, for that matter). It looks like groups were retrofitted, this really needs to be cleaned up. * System shows ok (up-to-date) if product does not exist at all. If you add a system for which the product is not mirrored to Suma at all, the "Updates" column of System List shows a green checkmark while the "base repo" column shows "(none)". The green checkmark is misleading, at most there should be a grey icon or so meaning that there is actually no info. * System shows ok if there are non-compliant packages. A green checkmark appears in System List if system contains non-compliant packages (Systems > system > Software > Packages > Non Compliant). The system list could somehow reflect the presence of non-compliant packages. These could for example pose a security risk. * Very old OS release shows as ok/up-to-date. For example, a fully patched SLES11-SP1 is shown with a green checkmark. Technically, this information therefore correct. However, in reality, the OS has been end-of-life for several years. It should show something other than the green checkmark which is creating a false belief that the system is ok while it should be replaced. Certainly it would not be impossible to look at for example the release date of the latest patch. If it's too old, there can be a warning. * In general, the system list/overview page could provide an even more holistic view by making more distinctions in the "Updates" column (or adding another "Status" perhaps) - Show a warning for very old OS (see above) - Show a warning if system contains non-compliant packages (see above) - Show a warning if product does not exist at all (instead of green, see above) - Reboot required could be shown in that same list (like after an SP migration) - State apply failures could also reflect in that list * Suma bootstrapping does not recognize enabled modules/products If the system being onboarded was previously registered to SCC, SMT or RMT, the previously enabled modules (for example SDK or Web-Scripting-Module etc.) are not automatically activated, even if Suma has correctly mirrored them. Instead, you have to compare which modules were used previously and perform manual actions to add them again. Probably this is not fixable, still it was something that caught our attention. * Software Channel Management Software > Manage > Channels page could show the sync policy for the individual channels. Currently there is no overview of the sync policies of the individual channels. You have to click on each one, open it and take a look. Best regards, J-M Roth

3 2

Nothing scheduling
by Len Ewen 30 Apr '21

30 Apr '21

So I just built a new server, rather than updating. After doing this, I cannot get anything to schedule. If I tell it to apply a package, it never pops up with the schedule action. When I try to schedule weekly repo syncs, I again have the same issue. Nothing ever shows up in the schedule section. Any suggestions? --------------- Len Ewen Systems Administrator 1 Information Technology University of Indianapolis (317) 788-3362 [image: UIndyIT.jpg] Confidentiality Notice: This communication and/or its content are for the sole use of the intended recipient, and may be privileged, confidential, or otherwise protected from disclosure by law. If you are not the intended recipient, please notify the sender and then delete all copies of it. Unless you are the intended recipient, your use or dissemination of the information contained in this communication may be illegal.

2 1

Prometheus Exporter -> wrong url
by Martin Willisegger 23 Apr '21

23 Apr '21

Hello all One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address. myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1 The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip. When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error: Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused What can I do to change the connection string to: http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics that is accessible from the prometheus server? I tried to change the prometheus_exporter Address: field from :9100 to myserver.domain:9100 and the Argument field from --web.listen-address=":9100" to --web.listen-address="myserver.domain:9100", but that changes nothing. The prometheus server catches the mgr-clients from the uyuni server: # -------------------- # Auto discover clients of uyuni # -------------------- - job_name: 'mgr-clients' uyuni_sd_configs: - host: https://uyuni.domain username: admin password: <password> Same problem with the apache Exporter :) Some ideas? Best regards Martin

5 11

Uyuni 2021.04 is released!
by Julio González Gil 23 Apr '21

23 Apr '21

Hello everyone! We are happy to announce the immediate availability of Uyuni 2021.04 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2021.04, including the release notes, documentation, requirements and setup instructions. IMPORTANT: Read the release notes. This update requires an extra manual step to adjust a dependency vendor change, and depending on your current Uyuni version some more manual steps can be required to update the Server (for example if your current version is < 2020.07) This is the list of highlights for this release: * Vendor change for some Java dependencies * Fix for potential security issue with Java RMI * New products enabled * Amazon Linux 2 clients * AlmaLinux 8 clients * Alibaba Linux 2 clients * Maintenance Windows UI * Removal of deprecated XMLRPC API methods * Reactivation keys in bootstrap scripts * Enable SAN SSL certificates * Universe Security, Multiverse, Restricted, and Backport channels for Ubuntu. * Oracle Linux UEK channel * Performance improvements * Redfish power management * OpenSCAP from SSM * Virtual network creation UI * Logging * Monitoring - Prometheus Exporter Exporter for Debian - Node Exporter Updated to 1.1.2 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 2021.04 As always, we hope you will enjoy Uyuni 2021.04 and we 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/pages/contact.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 2

Re: Adding OBS repo to system and GPG keys
by Julio González Gil 21 Apr '21

21 Apr '21

On miércoles, 21 de abril de 2021 17:20:52 (CEST) Robert Martens wrote: > So this is what I am looking at? > > https://www.uyuni-project.org/uyuni-docs/uyuni/salt/custom-states.html#_cust > om_state_to_trust_a_gpgkey > > Sincerely, > Bob Martens Hard to tell, since you didn't specify what your GPG key issues are. But if you are talking about the GPG keys not being trusted at the clients, then yes. That's what you need if you use salt. > > On Apr 21, 2021, at 10:17 AM, Julio González Gil <jgonzalez(a)suse.com> wrote: > >> Greetings! I have a Uyuni instance with, primarily, Leap 15.2 servers and > >> I > >> am wondering what is the best way to add repositories, especially in > >> order > >> to work around the GPG key issues I have been running into. > >> > >> Thanks! > > > > Depends on what GPG key problems you are are talking, as in this case > > there > > are two: > > > > 1. Running reposync > > > > This one can be fixed by syncing once usign CLI (spacewalk-repo-sync) as > > that will ask if you want to trust the GPG key from the repository. At > > that point you can "trust always", and subsequent reposyncs will just > > work, from CLI, WebUI, API or any other method. > > > > 2. Installing the packages at the clients > > > > As the clients do not trust the GPG key, you need to somehow trust it. > > > > The best approach is using salt and a salt state, or otherwise adding the > > GPG key to the bootstrap script (if used). > > > > It's what we describe for the Client Tools, as it's precisely this case: > > https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/client > > s-opensuse.html#_trust_gpg_keys_on_clients > > > > As for how to add the repositories: > > > > 1. To the server: > > https://www.uyuni-project.org/uyuni-docs/uyuni/administration/custom-chan > > nels.html> > > 2. Then of course you need to add the new channel to clients: > > - New clients: use activation keys > > - Existing clients: There are several ways but find myself using System > > Set > > > > Manager and System Groups, to avoid doing the change to each client > > individually > > https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/s > > ystem-set-manager.html > > https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/s > > ystem-groups.html> > > On miércoles, 21 de abril de 2021 15:54:35 (CEST) Bob Martens wrote: -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 1

Adding OBS repo to system and GPG keys
by Bob Martens 21 Apr '21

21 Apr '21

Greetings! I have a Uyuni instance with, primarily, Leap 15.2 servers and I am wondering what is the best way to add repositories, especially in order to work around the GPG key issues I have been running into. Thanks!

2 2

How to define RPM Repo Priorities
by Heiner Wulfhorst 21 Apr '21

21 Apr '21

Hi List, What is the suggested method to define RPM repo priorities? We need PackageHub to install icinga, but my customer suggested to enable it with lower priority than base, pool, etc. So far I haven't found any way to do this in documentation and GUI. BR Heiner (new uyuni lover)

1 0

Best/correct way to register SLES Clients
by Heiner Wulfhorst 19 Apr '21

19 Apr '21

Hi Group, We are using SLES Clients and in the past they were connected to our RMT / Reposerver using SUSEConnect command. Now that i have bootstrapped some SLES Clients to use my Uyuni Server with salt, "SUSEConnect -l" says: "To list extensions, you must first register the base product, using: SUSEConnect -r <registration code>" Is this the normal/wanted behavior as repos are pushed actively from Server to Client, or what should i do to make them know they belong to my uyuni server? Thanks, Heiner PGP: C5160402C3F27014(a)keys.gnupg.net <http://keys.gnupg.net/pks/lookup?search=0xC5160402C3F27014&fingerprint=on&o…>

2 1

Fwd: hello / how to add read-only WebGUI user accounts
by Heiner Wulfhorst 19 Apr '21

19 Apr '21

Hi folks, I am new to uyuni and try to create a read-only account for my colleagues. I want them to be able to see information like patches and known issues for the systems i am managing for them, but they should not be able to add, edit or delete anything. Any hint on how to do this? Thanks, Heiner PGP: C5160402C3F27014(a)keys.gnupg.net <http://keys.gnupg.net/pks/lookup?search=0xC5160402C3F27014&fingerprint=on&o…>

3 3