I am right jumping into this discussion too. We just managed to get a subscription-manager running on a fresh Ubuntu 20.04, thanks to apt.atix
Registering the host worked, we do have repos for Ubuntu, they sync every day. When I use subscription-manager repos --list, I get four repos back (three for Ubuntu, one for atix).
When I manually type apt update, apt runs against our foreman server and I get a list of upgradable packages. However, I don’t see theses packages under Hosts → All Hosts or Hosts → Content Hosts.
I do have this error messages:
" No installed packages and/or enabled repositories have been reported by subscription-manager."
and under provisioning details:
“Status: Error
Operating System: Ubuntu 20.04”
I mean, it works somehow, but not completely We can update via our foreman server, but it would be nice, to get the info about available updates, too.
More info: Under Hosts → content hosts → Details, in the Networking tab I just see 127.0.0.1 as IPv4 address, and not the real address. It looks like as the subscription-manager just reported the loopback device and not the ens162, as it does with our CentOS hosts.
Our architecture is x86_64. The architecture in our product/repo is amd64, though. I’ve read that there’s a bug that you don’t see any repos back if you use amd64. But subscription-manager repos --list does give us our repos…
Hi, thank you for the reply. We did this, manually installed PHP 7.4. After a while it shows up under Content Hosts → installed packages. But we do have an “Unknown subscription status”. Even after a subscription manager fresh etc.
I wonder what I am missing here…
I tried installing subscription-manager on Debian 11 (bullseye), but it fails due to several missing and not installable dependencies. They are only available in their python3 versions.
# dpkg -i python-subscription-manager_1.25.1-4_amd64.deb
(Reading database ... 42624 files and directories currently installed.)
Preparing to unpack python-subscription-manager_1.25.1-4_amd64.deb ...
Unpacking python-subscription-manager (1.25.1-4) over (1.25.1-4) ...
dpkg: dependency problems prevent configuration of python-subscription-manager:
python-subscription-manager depends on python-dateutil; however:
Package python-dateutil is not installed.
python-subscription-manager depends on python-ethtool; however:
Package python-ethtool is not installed.
python-subscription-manager depends on python-iniparse; however:
Package python-iniparse is not installed.
python-subscription-manager depends on python-six; however:
Package python-six is not installed.
python-subscription-manager depends on python-dbus; however:
Package python-dbus is not installed.
python-subscription-manager depends on python-rpm; however:
Package python-rpm is not installed.
python-subscription-manager depends on virt-what; however:
Package virt-what is not installed.
python-subscription-manager depends on python-debian; however:
Package python-debian is not installed.
python-subscription-manager depends on python-apt; however:
Package python-apt is not installed.
python-subscription-manager depends on python-gobject; however:
Package python-gobject is not installed.
python-subscription-manager depends on python-decorator; however:
Package python-decorator is not installed.
python-subscription-manager depends on apt-transport-katello; however:
Package apt-transport-katello is not installed.
dpkg: error processing package python-subscription-manager (--install):
dependency problems - leaving unconfigured
Processing triggers for dbus (1.12.20-2) ...
Processing triggers for mailcap (3.69) ...
Errors were encountered while processing:
python-subscription-manager
root@ethel-alcosiba:~# cat /etc/debian_version
11.0
The Ubuntu 20.04 version does not work, either, due to higher Python 3 version on bullsyeye.
# apt-get install -y python3-subscription-manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-subscription-manager is already the newest version (1.25.1-4).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
python3-subscription-manager : Depends: python3 (< 3.9) but 3.9.2-3 is to be installed
Depends: python3-dateutil but it is not going to be installed
Depends: python3-ethtool but it is not going to be installed
Depends: python3-iniparse but it is not going to be installed
Depends: python3-six but it is not going to be installed
Depends: python3-rpm but it is not going to be installed
Depends: virt-what but it is not going to be installed
Depends: python3-debian but it is not going to be installed
Depends: python3-decorator but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
Hi I am enjoying this discussion as I want to enroll Ubuntu clients with forman-katello.
I have used a minimal ubuntu vagrant image.
Everything is setup like Maximilian explained for ubuntu clients.
Client is correct registered and can download available packages. Only thing that I am missing (right now) is to see what packages are installed on the client (from foreman).
I know /usr/bin/package-profile-upload should do the job and when running it says only “No updates performed. See /var/log/rhsm/rhsm.log for more information” and with logging level on debug /var/log/rhsm/rhsm.log shows:
Connection built: host=xxxxx.lan port=443 handler=/rhsm auth=identity_cert ca_dir=/etc/rhsm/ca/ insecure=False.
Also tried frace to see if there is something that is blocking but no luck.
I have seen screenshots where a content host is displaying the packages that are available to that host.
Am I missing something?
apt-get install -y python3-subscription-manager failing with error
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-subscription-manager : Depends: python3-ethtool but it is not installable
Depends: python3-iniparse but it is not installable
Depends: python3-rpm but it is not installable
Depends: virt-what but it is not installable
Well, seems to be working fine, however I’m a bit surprised nobody mentioned these messages in /var/log/rhsm/rhsm.log:
…
2022-02-16 22:06:48,143 [WARNING] subscription-manager:180075:MainThread @repolib.py:124 - Configuration file of dnf plugin: “/etc/dnf/plugins/product-id.conf” cannot be read
…
I checked the code and that repolib.py is trying to read yum or dnf plugin configuration which doesn’t exist of course. Did I miss something?