containerized commands centos (beta 2 review)

[keichwa]

see https://github.com/SUSE/spacewalk/issues/24328

Some hints

Consider adding an entry to the CHANGELOG.md file in the toplevel directory.
Cosmetic changes such as fixing typos do not need log entries (nevertheless it is important to fix typos, etc.)!
In the manager-4.3, the hidden .changelog file with a leading dot is still in use.

Add Description, Target branches, and related Links below the following section titles.

In the Description, just enter a summary of why you created this PR (and, if available, add any relevant diagram).

Description

Short summary of why you created this PR (if you added documentation, please add any relevant diagram).

Target branches

• Which product version this PR applies to (Uyuni, SUMA 4.3, SUMA MU X.Y.Z, or SUMA development version). This information can be helpful if ifeval statements are needed to publish it for certain products only.
• Does this PR need to be backported? If yes, create an issue for tracking it and add the link to this PR.
• Whenever possible, cross-reference each backport PR here, so that all backports can be easily accessed from the description.

Backport targets (edit as needed):

• master
• 4.3

Links

• This PR tracks issue #<insert spacewalk issue, if any>
• Related development PR #<insert PR link, if any>

[mbussolotto]

I don't think this procedure could work. I think we need to pre-install perl-Text-Unidecode in server-image, then:
- mgrctl exec -- systemctl restart tomcat should be subtiture by mgradm restart
- /usr/local/bin/cent-errata.sh should be moved to a persisted location

@cbosdo @rjmateus JFYI, let me know if I missed anything

EDIT
Clarified by Cedric in below comments

[cbosdo]

The big issue here is that the development tools module cannot be installed on SLE-Micro as it requires the base system module to be added... and this would turn a SLE Micro into a SLES.

Now we need to figure out what we want to tell the user to do... Should they run this script on a SLES machine (not the SUMA server thus) or should we provide an alternative using mgrctl?

@admd @rjmateus any opinion on that?

[rjmateus]

Outcome of the discussion/research: Keep it for uyuni and remove the all section for SUSE Manager.
@admd anything to adD?

[keichwa]

Outcome of the discussion/research: Keep it for uyuni and remove the all section for SUSE Manager. @admd anything to adD?

Ok, done. Additionally, I changed the procedure suitable for a containerized Uyuni installation. I hope that's what we want and that I got it right. New reviews appreciated!

[admd]

@keichwa these changes will not work!

This workaround to get the errata information was needed for centos, we only have CentOS 7 right now which is going EOL in June. So I would say keep the original text but only for Uyuni and maybe add a note in this section that this is only applicable to non-containerized Uyuni and this section will be removed after CentOS 7 will go EOL.

[keichwa]

... So I would say keep the original text but only for Uyuni and maybe add a note in this section that this is only applicable to non-containerized Uyuni and this section will be removed after CentOS 7 will go EOL.

Thanks, makes a lot of sense. Done.