Pushing updated from katello to CentOS 7.5 not working

Hi All,

I’m currently having an issue with a fresh katello installation.

I’ve deployed an all-in-one katello stack to a CentOS VM, and configured the katello product and repo’s according to the awesome how-to at https://www.linuxtechi.com/katello-download-yum-repositories-register-clients-for-patching/

Now, from a client side, all is good. I can yum update without issues. They install fine.

However, using the foreman console, browsing to a content host and then trying to apply any (or all) of the “applicable” patches that has been identified, I have a problem - despite the result being a “success”. The error is different if I use the “upgrade selected” or “Update all packages” button.

I’m Using:
Foreman 1.17.1
Centos 7.5

Output from /var/log/messages during the patching is as follows:

trying to update selected packages:

Jun 21 16:42:48 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://testserver02.removed.domain:5647
Jun 21 16:42:48 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://testserver02.removed.domain:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Jun 21 16:42:48 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:92 - opened: proton+amqps://testserver02.removed.domain:5647
Jun 21 16:42:48 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:30 - connected: proton+amqps://testserver02.removed.domain:5647
Jun 21 16:42:48 testserver05 goferd: [INFO][worker-0] gofer.rmi.dispatcher:577 - call: Content.update() sn=55fda7b7-9503-4d55-a5f8-3f151cd7744e data={u'task_id': u'68318777-7e99-484d-a3e3-df1f3fc2215b', u'consumer_id': u'ca5ccc28-961b-4a81-ac33-cc3d4f884890'}
Jun 21 16:42:48 testserver05 env: Loaded plugins: enabled_repos_upload, fastestmirror, package_upload, product-id,
Jun 21 16:42:48 testserver05 env: : search-disabled-repos, subscription-manager
Jun 21 16:42:49 testserver05 env: Loading mirror speeds from cached hostfile
Jun 21 16:42:49 testserver05 env: * epel: mirrors.coreix.net
Jun 21 16:42:49 testserver05 env: No Match for argument: *:kernel-3.10.0-862.3.3.el7.x86_64-*-*.*
Jun 21 16:42:49 testserver05 env: No Match for argument: *:kernel-tools-3.10.0-862.3.3.el7.x86_64-*-*.*
Jun 21 16:42:49 testserver05 env: No Match for argument: *:kernel-tools-libs-3.10.0-862.3.3.el7.x86_64-*-*.*
Jun 21 16:42:49 testserver05 env: No Match for argument: *:linux-firmware-20180220-62.2.git6d51311.el7_5.noarch-*-*.*
Jun 21 16:42:49 testserver05 goferd: [INFO][worker-0] gofer.agent.rmi:144 - Request: 55fda7b7-9503-4d55-a5f8-3f151cd7744e processed in: 2.238 (seconds)
Jun 21 16:42:49 testserver05 goferd: [INFO][worker-0] gofer.agent.rmi:190 - Request: 55fda7b7-9503-4d55-a5f8-3f151cd7744e, committed
Jun 21 16:42:49 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:131 - closed: proton+amqps://testserver02.removed.domain:5647

trying to update all packages:

Jun 21 16:45:05 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://testserver02.removed.domain:5647
Jun 21 16:45:05 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://testserver02.removed.domain:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Jun 21 16:45:05 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:92 - opened: proton+amqps://testserver02.removed.domain:5647
Jun 21 16:45:05 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:30 - connected: proton+amqps://testserver02.removed.domain:5647
Jun 21 16:45:05 testserver05 goferd: [INFO][worker-0] gofer.rmi.dispatcher:577 - call: Content.update() sn=b67479f3-f7e9-4b9d-9f2d-8b9e4ca75f9d data={u'task_id': u'e071907f-f4ca-478c-a4d4-7f942c72f42f', u'consumer_id': u'ca5ccc28-961b-4a81-ac33-cc3d4f884890'}
Jun 21 16:45:05 testserver05 goferd: [ERROR][worker-0] katello.agent.pulp.dispatcher:112 - Handler failed.
Jun 21 16:45:05 testserver05 goferd: [ERROR][worker-0] katello.agent.pulp.dispatcher:112 - Traceback (most recent call last):
Jun 21 16:45:05 testserver05 goferd: [ERROR][worker-0] katello.agent.pulp.dispatcher:112 -   File "/usr/lib/python2.7/site-packages/katello/agent/pulp/dispatcher.py", line 108, in update
Jun 21 16:45:05 testserver05 goferd: [ERROR][worker-0] katello.agent.pulp.dispatcher:112 -     _report = handler.update(units, dict(options))
Jun 21 16:45:05 testserver05 goferd: [ERROR][worker-0] katello.agent.pulp.dispatcher:112 -   File "/usr/lib/python2.7/site-packages/katello/agent/pulp/handler.py", line 150, in update
Jun 21 16:45:05 testserver05 goferd: [ERROR][worker-0] katello.agent.pulp.dispatcher:112 -     patterns = [Pattern(**u) for u in units]
Jun 21 16:45:05 testserver05 goferd: [ERROR][worker-0] katello.agent.pulp.dispatcher:112 - TypeError: __init__() takes at least 2 arguments (1 given)
Jun 21 16:45:05 testserver05 goferd: [INFO][worker-0] gofer.agent.rmi:144 - Request: b67479f3-f7e9-4b9d-9f2d-8b9e4ca75f9d processed in: 1.164 (seconds)
Jun 21 16:45:05 testserver05 goferd: [INFO][worker-0] gofer.agent.rmi:190 - Request: b67479f3-f7e9-4b9d-9f2d-8b9e4ca75f9d, committed
Jun 21 16:45:05 testserver05 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:131 - closed: proton+amqps://testserver02.removed.domain:5647

Can anyone shed any light on why this isn’t working, or have any pointers please?

Regards,
Rob.

@katello, any thoughts on this?

I have the same issue after setting up a test environment with a foreman+katello server and one CentOS 7 client host.

Do you mind opening a redmine issue around this? It looks like a bug related with updating all packages.

Done, created as Bug #24347

Upgrading to Katello 3.7 has fixed the “upgrade all packages” functionality, but “Upgrade selected” remains broken.

Bug #24523 opened for this.

bug closed after fix created.

after upgrading to 3.8 it looks like it now works OK! Thank you.