(or especially hey @atix )
I just updated one of my Ubuntu 22.04 testsystems to the latest packages, and as well to the
python3-subscription-manager package version from
Noticed there, that it moved the working
/etc/rhsm/rhsm.conf config to
/etc/rhsm/rhsm.conf.dpkg-old, which basically made the upgrade fail, because it couldn’t do the package-profile-upload at the end of the upgrade anymore.
After I recovered the needed variables to the new config file (hostname, prefix, baseurl, repo_ca_cert) it’s working again, but yeah I don’t understand apt enough to know if they are doing this all the time or if this is a packaging thing that needs to be changed, that it creates dpkg-new files instead of moving the old config to dpkg-old?
If needed I can provide more information, not sure right now what might help here!
Foreman and Proxy versions:
Distribution and version:
Server: Rocky Linux 8.8
Client: Ubuntu 22.04 LTS
Looking into it, I would have had to define
-o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold", which is the default if ran via a job invocation, but is not the default when manually run on the system.
If there is no way to surpass this on the package level (or unwanted in the deb building world), welp then is it like that, coming from the RPM based world this is just different.
I could not reproduce this issue with the latest packaged
subscription-manager for Ubuntu 22.04. Can you please retest this? Please resync and reinstall
subscription-manager on your host.
I went from
1e4867bb70c448a7e5d6240cde4c10077e83fb59706d4b8a314b6835c2899ea3 python3-subscription-manager_1.28.24-8_amd64.deb to
thanks for your help
Tbh it’s weird, fortunately I have backups and lots of automatic CV builds, so I rolled back to before the upgrade, switched to the old CV, reinstalled subscription-manager, switched back to the new CV, and now it happened like it would be expected! :
Setting up python3-subscription-manager (1.29.35-1) ...
Configuration file '/etc/rhsm/rhsm.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** rhsm.conf (Y/I/N/O/D/Z) [default=N] ?
Was missing this part before the restore/reinstall! So yeah… I don’t know what was happening there, but obviously apt was thinking it’s fine to not ask.
Thanks for testing though