Manual Import Of Installed RPM's for SUSE Hosts

Expected outcome:


We are facing many dependence issues with katello-host-tools , subscription-manager and yum for suse 11/12/15 with forman+katello, Is there any plans or defined way to integrate suse hosts with katello like RHEL/CentOS. if we dont have any process other than katello-host-tools , subscription-manager and yum, we just thinking to follow below process, at least to manage the package management.

---- No subscription-manager/katello-host-tools –

Host register with puppet agent. – host register and facts collectd, host groups, proxy assign and content-view assigned.

prepare installed rpm data (using local commands).

import rpm data to katello server with the help of puppet agent. ( process required).

Calculate host errata based on that imported rpm data for that host.

REX/puppet module will use to manage the packages and patching activities.

Please let us know the process to import rpm data through api kind.

The workflow should be the same. If you take a look at Katello client for SLES 12 SP5 I opened about a month ago. @Bernhard_Suttner has worked on removing the yum dependency and @Jonathon_Turel is looking at updating the client repository which should solve the current problems.

@Dirk, Thanks for the update, so we have to wait until next client release.


Following are solved my issue for SUSE 12 Sp2. Few dependency packages are already there in suse repository and remaining downloaded from


Team, By default suse had yast/yast2/zypper package management tool but here we are installing yum based one, is there any specific reason for that?. & will it create any rpm db mismatch problems/conflict with zypper on existing running server?.

I / We know. This will be fixed with the new side clients which no longer have dependencies to yum. @Jonathon_Turel, I guess it’s time to create a new version.

The changes you worked on will be released in katello-host-tools-3.5.4 which is part of Katello 3.16, currently in RC1.

The yum dependency that @Rajeshunix13 is referring to likely comes from subscription-manager packaging. Not sure what the implications are of removing that for SLES systems. I’ll try to track down.

1 Like

Sub-man without yum dependencies simply works. Without a drawback.

1 Like