Hello list, first post.
Given that IBM provides Salt packages for AIX [1], including salt-minion
and salt-ssh, would AIX work as a Salt minion (or Salt client as some Uyuni
docs sometimes refer to) that connects to a Uyuni Salt master?
The reason why I'm asking this is because, on Saltstack, AIX usage is
restricted to Saltstack Enterprise. Even downloading the minion package for
AIX from Saltstack is restricted. [2]
So, I was wondering, would there be any usage related or legal related
restrictions regarding running Salt minion on AIX, using the IBM provided
packages, and a Uyuni Salt Master?
Thank you for your patience and time.
Luiz Vianna
Ref.:
1 -
https://www.ibm.com/support/pages/aix-toolbox-linux-applications-downloads-…
2 -
https://enterprise.saltstack.com/en/latest/_downloads/5b009a14c66480efccef2…
- *"If you are a SaltStack Enterprise customer, you can download the AIX
native minion from theSaltStack EnterpriseInstallation Guide."*
Dear users and contributors,
Now that 2020 is coming to an end, I'd like to take a quick look back at what
year was for Uyuni.
During 2020 we saw the community grow in numbers, not just in terms of users,
but also in terms of active contributors. Now we have people helping with the
translations, the documentation, the code itself (be it bugfixing or even new
features), and helping other fellow users at the mailing lists or Gitter.
Here are some highlights of what we all accomplished during the last 12
months:
- We now release each month or two months: 8 releases this year (versus 1 in
2019 and 2 in 2018).
- Since May 2020, we have been holding monthly Uyuni Community Hours meetings,
with presentations both from the main contributor (SUSE) and the community.
- We started a YouTube channel and populated it with videos on how to use
Uyuni, translate it, test it and analyze its performance [1].
- We moved our chat from IRC to Gitter [2]
- Mailing lists were moved to the new system [3] (kudos to the openSUSE Heroes
team!)
- Uyuni can now be translated, and that brought a lot of contributors that
already did an impressive job in a number of languages.
- Support for new OS as clients: CentOS/RHEL 8 (including ppc64le for CentOS
7/8), Ubuntu 20.04, Oracle Linux 6/7/8 and Debian 9/10.
- A lot of improvements in monitoring with Prometheus such as: new exporters
(and supported OSs), autodiscovery, federation and reverse proxy.
- Grafana, which can be used (among other things) to show the status of the
prometheus monotoring.
- Performance improvements for repository syncing.
- Uyuni Hub: allows management of several Uyuni Servers from a central one.
- Recurring actions.
- Usability improvements: automated database schema upgrade, autogeneration of
bootstrap repositories, UI icons for child channel synchronization status,
etc
- New formulas and improved formulas (cpu mitigations, prometheus federation,
prometheus exporters, Uyuni Hub...).
- Single sign-on (SSO).
- WebUI themes.
- Server and Proxy were updated to openSUSE Leap 15.2, that brought salt 3000
and PostgreSQL 12
- Yomi: new installer framework for openSUSE And SUSE Linux Enterprise Linux,
with formulas and forms for easy use
- A port of the Server to CentOS 8 was started
Keep in mind this is just a brief hightlight. The release notes [2] contain so
many changes and improvements that we cannot possibly list all of them here.
This was only possible thanks to the combined effort of all people from the
community, SUSE and openSUSE, and we can all be proud of the results.
Let me wish you all the best for the upcoming year 2021, for your personal
endeavours, and for your work at Uyuni, and for all your loved ones.
Keep up the good work, and remember to have a lot of fun!
[1] https://www.youtube.com/channel/UCB0SkZFAw9vPCFeUIYqZQ5A
[2] https://gitter.im/uyuni-project
[3] https://lists.uyuni-project.org/archives/?name=uyuni
[4] https://www.uyuni-project.org/doc/2020.11/release-notes-uyuni-server.html
--
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
Hi,
Helping a friend.
cat /etc/products.d/Uyuni-Server.prod shows:
Uyuni Server 2020.01
running on openSUSE 15.1
What would the steps look like to get current on both?
-Steve
Hello
Most of us will be on vacation in the coming weeks. That means there will be no Uyuni 2020.12 or Uyuni Community Hours this month.
We expect to release Uyuni 2021.01 in January and have our next Uyuni Community Hours on 29.01.2021.
Of course, e-mail and Gitter will keep working as usual.
Thank you
Pau Garcia Quiles
SUSE Manager Product Owner & Technical Project Manager
SUSE Software Solutions Spain
Hi
Following Redhat's announcement last week, I've moved three systems from Centos 8 Linux to centos 8 Stream.
I've added the Stream repos to Uyuni and switched channels to them, then followed the instructions at https://centos.org/distro-faq/
(As Uyuni doesn't have a uyuni-tools repo for Stream, I used the same Centos 8 Linux repo) The operation went successfully on the clients and all seemed good. However, it later emerged some of Uyuni's salt functionality has been lost on these clients.
What's okay: Remote commands still work, and all scheduled instructions to these servers are picked up as before.
What's not okay:
1.
Highstate won't apply. This also breaks repos when re-running the bootstrap command: "curl -Sks https://{URL}/pub/bootstrap/bootstrap-c8.sh<https://%7bURL%7d/pub/bootstrap/bootstrap-c8.sh> | /bin/bash"
As part of the script, existing repos are disabled, and any existing susemanager:channels.repo file is removed. Normally, this file is recreated when Highstate is applied, but this now fails. (Ditto when applying via Uyuni's webui)
Error: Error: Could not parse state file. Please check YAML syntax.
On server, /var/log/salt/minion logs show things like;
2020-12-16 11:50:41,871 [salt.state :3636][CRITICAL][36037] Rendering SLS 'base:services.salt-minion' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'pkg.list_repos'
2.
When running "Update Package List" via the webui (Server page: Software -> Packages)
An unexpected error has occurred. Please check the server logs.
We see
2020-12-15 14:29:41,653 [salt.utils.decorators:636 ][WARNING ][7610] The function "module.run" is using its deprecated version and will expire in version "Sodium".
2020-12-15 14:29:46,319 [salt.state :323 ][ERROR ][7610] Module function pkg.info_installed is not available
System info:
/etc/centos-release: CentOS Stream release 8
salt-minion -version: salt-minion 3000
Uyuni master is 2020-11
yum repolist:
repo id repo name
susemanager:c8s-powertools CentOS 8-stream Powertools
susemanager:c8s_appstream Centos 8-stream Appstream
susemanager:centos8stream_x86_64 Centos 8 Stream (x86_64)
susemanager:uyuni_client_stream Uyuni Client Tools for CentOS 8 (x86_64) Stream
To me, these two problems look linked, and I'm guessing that the Stream migration process has 'lost' a Salt module for package and repo management. My knowledge of salt is not good enough to diagnose this issue, and it's proved difficult to google a way to success despite spending too much time on it yesterday.
Can someone please help?
Simon Avery
Linux Systems Administrator
When I try to install the bootstrap, everything seems to work, right up
until the end and it gets to the registering phase when suddenly it goes:
REGISTRATION
------------
* registering
./bootstrap-ol7.sh: line 832: /etc/salt/minion.d/susemanager.conf: No such
file or directory
./bootstrap-ol7.sh: line 833: /etc/salt/minion.d/susemanager.conf: No such
file or directory
./bootstrap-ol7.sh: line 834: /etc/salt/minion.d/susemanager.conf: No such
file or directory
./bootstrap-ol7.sh: line 835: /etc/salt/minion.d/susemanager.conf: No such
file or directory
./bootstrap-ol7.sh: line 836: /etc/salt/minion.d/susemanager.conf: No such
file or directory
./bootstrap-ol7.sh: line 837: /etc/salt/minion.d/susemanager.conf: No such
file or directory
./bootstrap-ol7.sh: line 840: /etc/salt/minion.d/susemanager.conf: No such
file or directory
* removing TLS certificate used for bootstrap
(will be re-added via salt state)
* starting salt daemon and enabling it during boot
Created symlink from
/etc/systemd/system/multi-user.target.wants/salt-minion.service to
/usr/lib/systemd/system/salt-minion.service.
i have verified the minion.d folder exists but the susemanager.conf file
has not been copied.
Anyone got any suggestions on what is going wrong?
---------------
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.
I've been working to get a test box up and running for a while now as time
permitted and for reasons I don't know I cannot install packages to new
servers, I just push the button and it doesn't do anything. The second
issue is I can't schedule any repo syncs. I try to schedule the sync and
nothing happens. I can get remote commands to work, but nothing else.
Suggestions? I have no idea where to even look.
I am getting this in /var/log/messages
2020-12-07T15:44:51.960474-05:00 uyuni salt-master[2166]: Traceback (most
recent call last):
2020-12-07T15:44:51.960667-05:00 uyuni salt-master[2166]: File
"/usr/lib/python3.6/site-packages/salt/loader.py", line 853, in grains
2020-12-07T15:44:51.960840-05:00 uyuni salt-master[2166]: ret =
funcs[key](**kwargs)
2020-12-07T15:44:51.961009-05:00 uyuni salt-master[2166]: File
"/usr/lib/python3.6/site-packages/salt/grains/extra.py", line 106, in uefi
2020-12-07T15:44:51.961274-05:00 uyuni salt-master[2166]:
"efi-secure-boot": __secure_boot(),
2020-12-07T15:44:51.961489-05:00 uyuni salt-master[2166]: File
"/usr/lib/python3.6/site-packages/salt/grains/extra.py", line 97, in
__secure_boot
2020-12-07T15:44:51.961711-05:00 uyuni salt-master[2166]: with
salt.utils.files.fopen(sboot[0], "rb") as fd:
2020-12-07T15:44:51.961877-05:00 uyuni salt-master[2166]: File
"/usr/lib/python3.6/site-packages/salt/utils/files.py", line 399, in fopen
2020-12-07T15:44:51.962044-05:00 uyuni salt-master[2166]: f_handle =
open(*args, **kwargs) # pylint: disable=resource-leakage
2020-12-07T15:44:51.962203-05:00 uyuni salt-master[2166]: PermissionError:
[Errno 13] Permission denied:
'/sys/firmware/efi/vars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c/data'
---------------
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,
Where I can disable SSL comunication Uyuni to Salt-api? I can't use my
local bot to comunicate with salt-api.
Thanks
--
Cristian Gherman
Support / PHP developer
cristian.gherman(a)reea.net | www.reea.net | +4 0365410942
