Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRafael Cavalcanti
2019-05-16 21:17:04 UTC
Description of problem:
"Updating all Packages" by going to "Hosts" => "Host Collections" => "<Host Collection Name> => "Package Installation, Removal, and Update" => And select the dropdown "Update All Packages - Via Katello Agent" does not create a task right away under "Monitor" => "Tasks".
On my LAB ENV the tasks were created randomly. Some of the tasks were created after 1 hour and some of them 6 hours later.
However, on the client side, we could see the gofer agent starting the updates right away.
If we run "subscription-manager facts --update" on client node, the tasks show up immediately under "Monitor" => "Tasks".
Not sure if this is the expected behavior.
Version-Release number of selected component (if applicable):
Satellite 6.4.3
How reproducible:
Steps to Reproduce:
1. Install katello-agent on client node
2. Go to "Hosts" => "Host Collections" => "<Host Collection Name> => "Package Installation, Removal, and Update" => And select the dropdown "Update All Packages - Via Katello Agent"
3. No task is created under "Monitor" => "Tasks"
4. On the client system under /var/log/messages we can see:
*
*
*
May 15 20:54:17 client01 yum[10527]: Updated: 1:grub2-pc-modules-2.02-0.76.el7.1.noarch
May 15 20:54:17 client01 yum[10527]: Updated: 1:grub2-common-2.02-0.76.el7.1.noarch
May 15 20:54:17 client01 yum[10527]: Updated: libaio-0.3.109-13.el7.x86_64
May 15 20:54:17 client01 yum[10527]: Updated: libsmartcols-2.23.2-59.el7_6.1.x86_64
May 15 20:54:17 client01 yum[10527]: Updated: bluez-libs-5.44-4.el7_4.x86_64
May 15 20:54:17 client01 yum[10527]: Updated: firewalld-filesystem-0.5.3-5.el7.noarch
May 15 20:54:17 client01 yum[10527]: Updated: python-magic-5.11-35.el7.noarch
May 15 20:54:17 client01 yum[10527]: Updated: python-ipaddress-1.0.16-2.el7.noarch
May 15 20:54:17 client01 yum[10527]: Updated: lz4-1.7.5-2.el7.x86_64
May 15 20:54:17 client01 yum[10527]: Updated: python-perf-3.10.0-957.10.1.el7.x86_64
May 15 20:54:17 client01 yum[10527]: Updated: 1:grub2-pc-2.02-0.76.el7.1.x86_64
May 15 20:54:17 client01 yum[10527]: Updated: python-schedutils-0.4-6.el7.x86_64
May 15 20:54:17 client01 yum[10527]: Updated: trousers-0.3.14-2.el7.x86_64
May 15 20:54:17 client01 yum[10527]: Updated: kbd-legacy-1.15.5-15.el7.noarch
May 15 20:54:17 client01 goferd: [INFO][worker-0] gofer.agent.rmi:193 - Request: 8815b19e-2f67-4d76-98a0-30a2cbc97b86, committed
May 15 20:54:17 client01 goferd: [INFO][worker-0] gofer.agent.rmi:147 - Request: 8815b19e-2f67-4d76-98a0-30a2cbc97b86 processed in: 3.404 (minutes)
May 15 20:54:17 client01 goferd: [ERROR][worker-0] gofer.messaging.adapter.proton.reliability:53 - Connection amqps://sat64.example.lab:5647 disconnected: Condition('amqp
:resource-limit-exceeded', 'local-idle-timeout expired')
May 15 20:54:27 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:131 - closed: proton+amqps://sat64.example.lab:5647
May 15 20:54:27 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://sat64.example.lab:5647
May 15 20:54:27 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://sat64.example.lab:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None
May 15 20:54:28 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:92 - opened: proton+amqps://sat64.example.lab:5647
May 15 20:54:28 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:30 - connected: proton+amqps://sat64.example.lab:5647
May 15 20:54:28 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:131 - closed: proton+amqps://sat64.example.lab:5647
Actual results:
No tasks are created under "Monitor" => "Tasks" page
Expected results:
Tasks created under "Monitor" => "Tasks" page
Additional info:
I have noticed that the tasks are created randomly under Monitor" => "Tasks" after some time(some of than after 1 hour, some of them after 6 hours).
Hi Rafael,
The behavior described is expected. For bulk actions for packages, there are no tasks created when katello-agent is used. There has been some discussion regarding this in the past; however, there are no current plans to change the behavior. Below are a couple of references for some of the historical discussion. Please do look them over for additional details and let us know if there any questions. Thanks!
https://bugzilla.redhat.com/show_bug.cgi?id=1108106#c15https://bugzilla.redhat.com/show_bug.cgi?id=1418993
*** This bug has been marked as a duplicate of bug 1418993 ***
Description of problem: "Updating all Packages" by going to "Hosts" => "Host Collections" => "<Host Collection Name> => "Package Installation, Removal, and Update" => And select the dropdown "Update All Packages - Via Katello Agent" does not create a task right away under "Monitor" => "Tasks". On my LAB ENV the tasks were created randomly. Some of the tasks were created after 1 hour and some of them 6 hours later. However, on the client side, we could see the gofer agent starting the updates right away. If we run "subscription-manager facts --update" on client node, the tasks show up immediately under "Monitor" => "Tasks". Not sure if this is the expected behavior. Version-Release number of selected component (if applicable): Satellite 6.4.3 How reproducible: Steps to Reproduce: 1. Install katello-agent on client node 2. Go to "Hosts" => "Host Collections" => "<Host Collection Name> => "Package Installation, Removal, and Update" => And select the dropdown "Update All Packages - Via Katello Agent" 3. No task is created under "Monitor" => "Tasks" 4. On the client system under /var/log/messages we can see: * * * May 15 20:54:17 client01 yum[10527]: Updated: 1:grub2-pc-modules-2.02-0.76.el7.1.noarch May 15 20:54:17 client01 yum[10527]: Updated: 1:grub2-common-2.02-0.76.el7.1.noarch May 15 20:54:17 client01 yum[10527]: Updated: libaio-0.3.109-13.el7.x86_64 May 15 20:54:17 client01 yum[10527]: Updated: libsmartcols-2.23.2-59.el7_6.1.x86_64 May 15 20:54:17 client01 yum[10527]: Updated: bluez-libs-5.44-4.el7_4.x86_64 May 15 20:54:17 client01 yum[10527]: Updated: firewalld-filesystem-0.5.3-5.el7.noarch May 15 20:54:17 client01 yum[10527]: Updated: python-magic-5.11-35.el7.noarch May 15 20:54:17 client01 yum[10527]: Updated: python-ipaddress-1.0.16-2.el7.noarch May 15 20:54:17 client01 yum[10527]: Updated: lz4-1.7.5-2.el7.x86_64 May 15 20:54:17 client01 yum[10527]: Updated: python-perf-3.10.0-957.10.1.el7.x86_64 May 15 20:54:17 client01 yum[10527]: Updated: 1:grub2-pc-2.02-0.76.el7.1.x86_64 May 15 20:54:17 client01 yum[10527]: Updated: python-schedutils-0.4-6.el7.x86_64 May 15 20:54:17 client01 yum[10527]: Updated: trousers-0.3.14-2.el7.x86_64 May 15 20:54:17 client01 yum[10527]: Updated: kbd-legacy-1.15.5-15.el7.noarch May 15 20:54:17 client01 goferd: [INFO][worker-0] gofer.agent.rmi:193 - Request: 8815b19e-2f67-4d76-98a0-30a2cbc97b86, committed May 15 20:54:17 client01 goferd: [INFO][worker-0] gofer.agent.rmi:147 - Request: 8815b19e-2f67-4d76-98a0-30a2cbc97b86 processed in: 3.404 (minutes) May 15 20:54:17 client01 goferd: [ERROR][worker-0] gofer.messaging.adapter.proton.reliability:53 - Connection amqps://sat64.example.lab:5647 disconnected: Condition('amqp :resource-limit-exceeded', 'local-idle-timeout expired') May 15 20:54:27 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:131 - closed: proton+amqps://sat64.example.lab:5647 May 15 20:54:27 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://sat64.example.lab:5647 May 15 20:54:27 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://sat64.example.lab:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None May 15 20:54:28 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:92 - opened: proton+amqps://sat64.example.lab:5647 May 15 20:54:28 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:30 - connected: proton+amqps://sat64.example.lab:5647 May 15 20:54:28 client01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:131 - closed: proton+amqps://sat64.example.lab:5647 Actual results: No tasks are created under "Monitor" => "Tasks" page Expected results: Tasks created under "Monitor" => "Tasks" page Additional info: I have noticed that the tasks are created randomly under Monitor" => "Tasks" after some time(some of than after 1 hour, some of them after 6 hours).