We are happy to announce the immediate availability of Uyuni 2022.03
At https://www.uyuni-project.org/pages/stable-version.html you will find all
the resources you need to start working with Uyuni 2022.03, including the
release notes, documentation, requirements and setup instructions.
This is the list of highlights for this release:
- Fixes for Salt security issues
- New XML-RPC API version 26
- smdba: changed defaults for newer PostgreSQL versions
- Monitoring: Grafana 8.3.5
- Salt SSH now uses the Salt Bundle
- Some products are now becoming unsupported
Please check the release notes for full details. For the Salt Security issues,
you must update the Salt master on the Uyuni Server before updating any
client.
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 2022.03
As always, we hope you will enjoy Uyuni 2022.03 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
Hi Julio,
I am getting the same error. This is with a new install of Uyuni 2022.02.
It looks like the certificate is getting created in /root/ssl-build but the rpm package is not. I manually copied the certificate and key to the locations in /etc/pki/tls/ indicated by the apache2 config to be able to start the web service, but we need to build the cert rpm package for deployment to clients. We're actually going to go through the procedure to build a custom CA-signed cert so we will see whether that goes OK or if it breaks as well, but the default process for using a self-signed cert seems to be broken after the creation of the cert. The self signed cert also appears to have the OU and O order mixed up, although I expect that shouldn't be enough to break the cert configuration.
Cheers,
Paul-Andre Panon
We are happy to announce the immediate availability of Uyuni 2021.02
At https://www.uyuni-project.org/pages/stable-version.html you will find all
the resources you need to start working with Uyuni 2022.02, including the
release notes, documentation, requirements and setup instructions.
VERY IMPORTANT: Read the release notes! If you are updating from an Uyuni
version older than 2021.06, a major upgrade procedure is required.
This is the list of highlights for this release:
* Reporting Database
* Ubuntu errata installation
* Monitoring: Prometheus 2.32.1
* Monitoring: Postgres exporter updated to version 0.10.0 for SUSE Linux
Enterprise and openSUSE
* SLES PAYG client support on cloud
* openscap for Debian 11 (Tech Preview)
Please check the release notes for full details, and in particular review
the section about the Postgres exporter update and the Prometheus update, as
it could require manual if you are using monitoring.
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 2022.02
As always, we hope you will enjoy Uyuni 2022.02 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
Has anyone managed to get the Grafana dashboards working on Centos or Rocky?
I have tried several times over various versions and just given another hour to the task without any joy.
Following the guide and applying the Salt formula always fails on the targets I've tried, with:
ID: install_prometheus
Function: pkg.installed
Name: golang-github-prometheus-prometheus
Result: false
Comment: Error occurred installing package(s). Additional info follows:
errors:
- Running scope as unit: run-r4cd5eeb15cd8494685380c6107f1045b.scope
Last metadata expiration check: 0:00:03 ago on Thu Mar 10 14:37:34 2022.
No match for argument: golang-github-prometheus-prometheus
Error: Unable to find a match: golang-github-prometheus-prometheus
Started: 14:37:18.669658
Duration: 20980.625
SLS: prometheus
Changed: {}
And indeed - the package is not called that on EL. It is supplied in the Epel repos (although on Centos 7 that appears to be broken - it does install fine manually on Rocky 8) - but the package is called golang-github-prometheus - so always fails.
Anyone know how to work around this? I don't have any Suse machines other than the one Uyuni runs on.
Manually, I always seem to get into configuration problems with Prometheus. It's not software I'm familiar with and it does seem very fussy about syntax (something I've seen discussed at https://github.com/uyuni-project/uyuni/issues/2082 )
I have an existing Grafana server that I'd like to be able to use this with.
Simon Avery
Linux Systems Administrator: ATASS Sports
Oxygen House | Grenadier Road, Exeter Business Park | EX1 3LH
t: 01392 440 400
e: simon.avery(a)atass-sports.co.uk<mailto:simon.avery@atass-sports.co.uk>
www.atass-sports.co.uk<https://gbr01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.atass-…>
Follow us on Twitter: @atassSports<https://twitter.com/atassSports>
NOTICE
This email and any attachments confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Please notify the sender immediately. ATASS Ltd is incorporated in England and Wales with company number 04807405. See our website for further details and our privacy policy
Can someone help I am getting the following Error output.
Setup script output
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
xPerforming forced re-installation! x
xShutting down spacewalk services... x
xDone. x
xDelete existing database... x
xDelete existing salt minion keys x
xCREATE ROLE w
x* Loading answer file: /root/spacewalk-answers. x
x** Database: Setting up database connection for PostgreSQL backend. x
x** Database: Populating database. x
x** Database: --clear-db option used. Clearing database. x
x** Database: Shutting down spacewalk services that may be using DB. x
x** Database: Services stopped. Clearing DB. x
x*** Progress: # x
x* Configuring tomcat. x
x* Setting up users and groups. x
x* Performing initial configuration. x
x* Configuring apache SSL virtual host. x
x* Configuring jabberd. x
x* Creating SSL certificates. x
x** SSL: Generating CA certificate. x
x** SSL: Generating server certificate. x
xCould not deploy the certificates. Exit value: 1. x
xPlease examine /var/log/rhn/rhn_installation.log for more information. v
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
Error output
xWarning: ALREADY_ENABLED: suse-manager-server x
xERROR: spacewalk-setup failed x
x
I would like to configure an Uyuni installation to bootstrap systems to use a public available repo URL instead of a local one.
I believe this is achieved by changing the "Uyuni server hostname" under "Uyuni Configuration - Bootstrap", but when bootstrapping a system, the repo URL is using the "Uyuni Hostname" (e.g. uyuni.my-local-domain) and not the Uyuni server hostname (e.g. update.my-public-domain).
I have checked all the Uyuni documentation, and googled this topic, but I have only found hints that it should be possible, but not an explanation how to actually achieve this, so I wonder if my understanding is wrong, or if something is missing in our installation.
Running Uyuni 2022.01 on openSUSE Leap 15.3
I would highly appreciate if someone could help with getting this up and running.
Thanks,
Jacob Dall
Sending it to the list, as it somehow ended in the Bcc.
It will be useful if we have Uyuni (and later SUMA) on a Kubernetes/Openshift cluster.
Best Regards,Strahil Nikolov
On Thu, Mar 3, 2022 at 16:03, Julio Gonzalez<jgonzalez(a)suse.com> wrote: On jueves, 3 de marzo de 2022 14:48:28 (CET) Strahil Nikolov wrote:
> Hi Julio,
> Are there any plans for moving Uyuni into the container world ?
> Best Regards,Strahil Nikolov
Hi!
Please send the question to the users list. It seems you did it, but the list
was not present at the TO field :-)
--
Julio González Gil
Release Engineer, SUSE Manager and Uyuni
jgonzalez(a)suse.com
