Hello
Resending in a decent format since the mailing list management software seems to choke with Microsoft Teams appointments.
We will be holding monthly Uyuni Community Hours on the last Friday of the month, as usual.
Agenda:
1. Uyuni 2020.07. Now based on openSUSE Leap 15.2!
2. Salt module.run compatibility
3. Monitoring: exposing all your Prometheus metrics
4. Translations. How to make Uyuni available in your language.
Link to join:
https://teams.microsoft.com/l/meetup-join/19%3ameeting_NTEzNGIzMDItMzUwMi00…
Dial-in:
Numbers: https://dialin.teams.microsoft.com/58c3986f-4c3a-4b77-b4e8-f431171ef66d?id=…
Conference ID: 620 373 916#
Thank you
Pau Garcia Quiles
SUSE Manager Product Owner & Technical Project Manager
SUSE Software Solutions Spain
Hello, (Poss duplicate as got a bounce message)
Not the most critical of problems, but one that niggles each day.
By default, Uyuni sends scheduled emails, like the Daily Status report, addressed with the FROM field as: "SUSE Manager"
As the only Suse box in our organisation is the one Uyuni runs on, this is confusing to our users and disbalances the cosmic harmony of things being 'right'.
I'd like to change this, perhaps to "Uyuni Server Manager".
I can't seem to find documentation relating to changing this.
Is it possible, please?
Thanks,
S
Hello,
Not the most critical of problems, but one that niggles each day.
By default, Uyuni sends scheduled emails, like the Daily Status report, addressed with the FROM field as: "SUSE Manager"
As the only Suse box in our organisation is the one Uyuni runs on, this is confusing to our users and disbalances the cosmic harmony of things being 'right'.
I'd like to change this, perhaps to "Uyuni Server Manager".
I can't seem to find documentation relating to changing this.
Is it possible, please?
Thanks,
S
Hi all,
I have noticed that "gpgcheck" parameter is now set to 1 in the susemanager:channels.repo repo client configuration.
I have compared with servers registered before the upgrade to 2020.07, and GPG check was deactivated.
Do you know why this change ? Is there a way to deactivate it again, or perhaps automatically import the GPG keys while registering the server in Uyuni ?
Regards,
Philippe.
Philippe Bidault | Unix Engineer
Getronics
________________________________
M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com
[cid:M17520GetronicsConnectingPossibilitiesE-Sig425x204_e1803ca0-99a5-4a65-abd8-074c86bf11aa.png]<http://www.getronics.com/>
<http://www.linkedin.com/company/2077785>[cid:LinkedIn_4aeb630a-f385-4f22-927e-31323d2554b8.png]<https://www.linkedin.com/company/2077785> [cid:Twitter_6c9cce61-b2e3-49d4-991c-e799d031f1ae.png] <https://twitter.com/Getronics> <http://twitter.com/Getronics> [cid:Youtube_5150f807-4ba8-46a3-bbbf-038ccfdc2793.png] <https://www.youtube.com/user/getronicsonline?feature=results_main> <http://www.youtube.com/user/getronicsonline?feature=results_main> sign-info
<http://www.getronics.com/knowledge-share/news-and-events/ovum.php#sthash.cb…>
Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262.
Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain.
The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you.
Legal disclaimer: http://www.getronics.com/legal/
Hi all,
I have noticed that the CVE ID were truncated, importing them from the philicious script (https://github.com/philicious/spacewalk-scripts/blob/master/errata-import.py)
Truncated because of the regexp limitation "CVE = "(?P<cve>CVE-\d{4}-\d{4})".
I have modified it to accept 5 digits ( CVE = "(?P<cve>CVE-\d{4}-\d{5} ), but to be able to import them again, I would need to remove all the erratas from the Ubuntu repositories.
Is there an easy way to do it ?
Regards,
Philippe.
Philippe Bidault | Unix Engineer
Getronics
________________________________
M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com
[cid:M17520GetronicsConnectingPossibilitiesE-Sig425x204_e1803ca0-99a5-4a65-abd8-074c86bf11aa.png]<http://www.getronics.com/>
<http://www.linkedin.com/company/2077785>[cid:LinkedIn_4aeb630a-f385-4f22-927e-31323d2554b8.png]<https://www.linkedin.com/company/2077785> [cid:Twitter_6c9cce61-b2e3-49d4-991c-e799d031f1ae.png] <https://twitter.com/Getronics> <http://twitter.com/Getronics> [cid:Youtube_5150f807-4ba8-46a3-bbbf-038ccfdc2793.png] <https://www.youtube.com/user/getronicsonline?feature=results_main> <http://www.youtube.com/user/getronicsonline?feature=results_main> sign-info
<http://www.getronics.com/knowledge-share/news-and-events/ovum.php#sthash.cb…>
Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262.
Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain.
The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you.
Legal disclaimer: http://www.getronics.com/legal/
Hi
I have state channels I would like to assign and apply to any new system that registers with Uyuni.
Adding the state channels to the activation key is not enough. The state channels will be assigned, however they will not be automatically applied.
As a workaround I added this to the boostrap.sh: sleep 60 && salt-call state.apply &
Is there a more elegant way to achieve this?
Regards,
Javier
I am installing the new 2020.07 on a brand new SUSE box and when I got to
the install phase I am getting : Problem: nothing provides postgresql12
needed by spacewalk-postgresql-4.1.3-1.4.uyuni.noarch
Detailed information:
patterns-uyuni_server-2020.07-1.1.uyuni.x86_64 requires
spacewalk-postgresql, but this requirement cannot be provided
nothing provides postgresql12 needed by
spacewalk-postgresql-4.1.3-1.4.uyuni.noarch
I can't seem to figure out a way around this, I don't want to break
postgres and end up in dependency hell, so has anyone seen this and has a
work around?
---------------
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.
Hello, Spacewalk orphan looking for new home here.
New Leap 15.2 and Uyuni 2020.07 install.
On bootstrapping a Centos 8 client, I hit some snags initially, and needed to install salt-minion on the client, which in turn needed a new repo adding.
yum install https://repo.saltstack.com/py3/redhat/salt-py3-repo-latest.el8.noarch.rpm
yum install salt-minion
This installs salt-minion 3001-1.el8 plus dependencies.
This allowed me to bootstrap through the Uyuni web interface and add the client successfully using the salt method.
However, when running a remote command, such as "touch /tmp/i_exist.txt" (actual path doesn't matter), this fails with
stderr:
/bin/sh: /tmp/__salt.tmp.jir6xlhr.sh: Permission denied
Googling tells me this is a salt error rather than a Uyuni one, but as Uyuni set up salt-minion I'm hoping to gain a solution here.
Can anyone point me in the right direction please?
Thanks
Hi,
is there an advice how to upgrade SLES 15 to SLES 15 SP1 (and later to
SP2) by Uyuni (2020/01)?
Searching at the web I only found a lot of hits for upgrading Uyuni
itself (and the mail archive of this list is mainly delivering "Error
500" right now). At Uyuni's docs I find only some informations about
X-upgrading SLES 12 to SLES 15.
Of course I already added the respective channels at Admin / Setup
Wizard / Products which got synchronized successfully in the meantime.
How should I proceed?
--
Gruss,
Tobias Crefeld.
xmpp (no email): crefeld(a)xabber.de
--
To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org
To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org