search

uyuni-project / uyuni

Source code for Uyuni
https://www.uyuni-project.org/
GNU General Public License v2.0
428 stars 178 forks source link

ERROR: client_config_update.py was not downloaded during the installation of salt-minion #8865

Open Teamspeak5 opened 3 months ago

Teamspeak5 commented 3 months ago

Problem description

I recently upgraded my uyuni environment to release 2024.03 and some of the new installation attempts always fail with the same error.

UPDATING RHEN_REGISTER/UP2DATE CONFIGURATION FILES
-------------------------------------------------
* downloading necessary files
  client_config_update.py...
https://*FQDN*/pub/bootstrap/client_config_update.py:
2024-06-04 11:02:24 ERROR 404: 404.
  client-config-overrides.txt...
2024-06-04 11:02:24 URL:https://*FQDN*/pub/bootstrap/client-config-overrides.txt [580/580] -> "client-config-overrides.txt" [1]
FINISHED --2024-06-04 11:02:24--
Total wall clock time: 0.3s
Downloaded: 1 files, 580 in 0s (12.9 MB/s)
ERROR: client_config_update.py was not downloaded

I've not found any error/problem before that are related to this same error a part from this article from RedHat: https://access.redhat.com/solutions/78563

Is there any way to regenerate this python file in order to solve this issue?

Steps to reproduce

  1. rm -f /etc/machine-id
  2. rm -f /var/lib/dbus/machine-id
  3. dbus-uuidgen --ensure
  4. systemd-machine-id-setup
  5. wget https://*FQDN*/pub/bootstrap/bootstrap.sh --no-check-certificate
  6. chmod +x bootstrap.sh
  7. ./bootstrap.sh

Uyuni version

Information for package Uyuni-Server-release:
---------------------------------------------
Repository     : Uyuni Server Stable
Name           : Uyuni-Server-release
Version        : 2024.05-230900.217.1.uyuni3
Arch           : x86_64
Vendor         : obs://build.opensuse.org/systemsmanagement:Uyuni
Support Level  : Level 3
Installed Size : 1.4 KiB
Installed      : Yes (automatically)
Status         : out-of-date (version 2024.03-230900.214.6.uyuni3 installed)
Source package : Uyuni-Server-release-2024.05-230900.217.1.uyuni3.src
Summary        : Uyuni Server
Description    :
    Uyuni lets you efficiently manage physical, virtual,
    and cloud-based Linux systems. It provides automated and cost-effective
    configuration and software management, asset management, and system
    provisioning.

Uyuni proxy version (if used)

N/A

Useful logs

N/A

Additional information

I've checked if this .py file really exists under that directory but didn't found it.

content of ../pub/bootstrap image

Additionally, while checking the client-config-overrides.txt file I've saw those comments, maybe they can be also useful to further analyze the situation. image

rjmateus commented 3 months ago

Are you using traditional stack? Can you try re-generate a fresh bootstract script and try again?

Teamspeak5 commented 3 months ago

Are you using traditional stack?

I do not know, as I can see from other posts, I could be using the traditional one that is no more supported in the new updates of Uyuni as I recently saw. Could you please tell me how could I check for that? Could you please give me instructions or docs for that?

Can you try re-generate a fresh bootstrap script and try again?

Yes, I tried using the web-ui going into [Admin -> Manager Configuration -> Bootstrap Script] and then I clicked "Update". Right after clicking that, I got this alert/error message "Could not find the CA certificate".

What could be wrong to get that message? What should I do to address this other issue? I did not find any article talking about this error in particular
I'm attaching a screenshot as evidence image

Teamspeak5 commented 3 months ago

Sorry for bothering you again @rjmateus , could you kindly help me further troubleshoot the issue? Unfortunately to make the bootstrap work again with the missing script, I had to make a workaround to momentarily solve the issue, I just copied the script from the VM PRE-Upgrade and putted it in the same directory on the POST-Upgrade one.

However, this still doesn't solve the regeneration of the script and the bootstrap script upgrade. Additionally, I've noticed that some channels are failing to build the bootstrap scripts, some packages seem to be "missing". After searching online I've noticed this issue seem to have already been solved in those issues, or at least seem to have been mitigated in different ways: 7591 - the repo for client tools wasn't added 8623 - mirror-redirector issue 5739 - not a parental channel

All of those 3 problems, similar to mine at a first glance, seem not related to my problem as I appear to not have those issues.

image image image image

rjmateus commented 3 months ago

Do you have the client tools channels added to your uyuni server? Are they correctly synchronized? Look at /var/log/rhn/reposyn/ to check repo-syn error. Did you tried to manually force the generation of bootstrap repository? Even using the --force flag?

rjmateus commented 3 months ago

for sle-15-sp4 and sles4sap-15-sp3 looks like you are missing the client tools channels.

Teamspeak5 commented 3 months ago

for sle-15-sp4 and sles4sap-15-sp3 looks like you are missing the client tools channels.

Dear @rjmateus, I've tried to check for the missing client channels to solve the issue. I've found just those channel client tools in my server for the moment : image

So I tried to follow the following Doc to add the client tool channel for those ones. https://www.uyuni-project.org/uyuni-docs/en/uyuni/client-configuration/clients-sle.html I didn't find any direct mention of SLES4SAP, but I've found this article 8879 where @mcalmer said :

Yes, it is by design. On a system we see only it is a SLE 15 SP4. SLES, SLES for SAP, SLED and others are all the same. So only 1 entry for all.

So I got for a "fact" that this is right. I've tried to add the channel using mgr-sync add channel <channel_label_1> but got this error: General error: can't set attribute

I've tried to make some research about that and found this other issue : 8473 Where @pj256 is reporting this problem and, for the moment, I got stuck here because I want to take a deeper look before taking action on that problem.



On the other hand regarding this reply :

Do you have the client tools channels added to your uyuni server? Are they correctly synchronized? Look at /var/log/rhn/reposyn/ to check repo-syn error. Did you tried to manually force the generation of bootstrap repository? Even using the --force flag?

The sync fails at the final section, when generating the bootstrap, that's where i also noticed that the sync was returning errors. Soon I'll try to force that manually and keep you posted. Please correct me if something is wrong

Thank you