/etc/rhn/rhn.conf was empty after updating to 2023.03 - how to regenerate?

[srinidhibs]

Hello Team,

When I updated to the 2023.03 release on the 12th of March, I realized that none of the spacewalk services came up after the reboot. I found the following in the logs:

...
2023-03-12T23:53:15.475071+05:30 uyuni systemd[1]: Starting Configures secrets between salt-master and other services...
2023-03-12T23:53:15.476431+05:30 uyuni systemd[1]: Starting Uyuni update config...
2023-03-12T23:53:15.597654+05:30 uyuni systemd[1]: Finished Uyuni update config.
2023-03-12T23:53:15.600220+05:30 uyuni systemd[1]: Starting Uyuni check database...
2023-03-12T23:53:15.619536+05:30 uyuni salt-secrets-config.py[9181]: Traceback (most recent call last):
2023-03-12T23:53:15.619613+05:30 uyuni salt-secrets-config.py[9181]:   File "/usr/bin/salt-secrets-config.py", line 81, in <module>
2023-03-12T23:53:15.619666+05:30 uyuni salt-secrets-config.py[9181]:     secret_hash = hashlib.sha512(CFG.secret_key.encode('ascii')).hexdigest()
2023-03-12T23:53:15.619704+05:30 uyuni salt-secrets-config.py[9181]: AttributeError: 'NoneType' object has no attribute 'encode'
2023-03-12T23:53:15.626529+05:30 uyuni systemd[1]: salt-secrets-config.service: Main process exited, code=exited, status=1/FAILURE
2023-03-12T23:53:15.626720+05:30 uyuni systemd[1]: salt-secrets-config.service: Failed with result 'exit-code'.
2023-03-12T23:53:15.627104+05:30 uyuni systemd[1]: Failed to start Configures secrets between salt-master and other services.
2023-03-12T23:53:15.627337+05:30 uyuni systemd[1]: Dependency failed for Spacewalk.
2023-03-12T23:53:15.627420+05:30 uyuni systemd[1]: spacewalk.target: Job spacewalk.target/start failed with result 'dependency'.
2023-03-12T23:53:15.879636+05:30 uyuni spacewalk-startup-helper[9188]: Config file [/etc/rhn/rhn.conf] does not seem to have db_backend set.
2023-03-12T23:53:15.879732+05:30 uyuni spacewalk-startup-helper[9188]: Config file [/etc/rhn/rhn.conf] does not seem to have db_name set.
2023-03-12T23:53:15.879771+05:30 uyuni spacewalk-startup-helper[9188]: Config file [/etc/rhn/rhn.conf] does not seem to have db_user set.
2023-03-12T23:53:15.879815+05:30 uyuni spacewalk-startup-helper[9188]: Config file [/etc/rhn/rhn.conf] does not seem to have db_password set.
2023-03-12T23:53:15.882849+05:30 uyuni spacewalk-startup-helper[9184]: Database version '' is not supported for SUSE Manager/Uyuni on openSUSE Leap 15.4. Perform database migration.
2023-03-12T23:53:15.883165+05:30 uyuni systemd[1]: uyuni-check-database.service: Main process exited, code=exited, status=1/FAILURE
2023-03-12T23:53:15.883306+05:30 uyuni systemd[1]: uyuni-check-database.service: Failed with result 'exit-code'.
2023-03-12T23:53:15.883703+05:30 uyuni systemd[1]: Failed to start Uyuni check database.
2023-03-12T23:53:15.883871+05:30 uyuni systemd[1]: Dependency failed for Apache Tomcat Web Application Container.
2023-03-12T23:53:15.883940+05:30 uyuni systemd[1]: tomcat.service: Job tomcat.service/start failed with result 'dependency'.
...

Indeed, the contents of /etc/rhn/rhn.conf was reduced to just one line:

# cat /etc/rhn/rhn.conf-20230424


server.susemanager.scc_backup_srv_usr = 08cad9ac-a29c-4cdc-816e-12aa133a42cf

I remember configuring the rhn.conf to use the disconnected setup against our local SMT server. I've been trying to find the older file contents using snapper, but to no avail!

How can I generate or restore the contents of the /etc/rhn/rhn.conf file?

I updated to 2023.04 yesterday, but the services are still not up due to the obvious empty file.

Regards,
Srinidhi.

[srinidhibs]

I reinstalled Uyuni! 😞

As soon as I have the initial setup ready, I am going to follow the instructions available at backup and restore to avoid such loss of configuration whenever a major update is performed.