Bug 1615899 - Pushing updates from katello 3.7 to CentOS 7.5 client not working
Summary: Pushing updates from katello 3.7 to CentOS 7.5 client not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.4.0
Assignee: Jonathon Turel
QA Contact: Jameer Pathan
URL:
Whiteboard:
: 1613237 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-14 13:52 UTC by Jonathon Turel
Modified: 2019-11-05 23:32 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-katello-3.7.0.20-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 19:17:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24523 0 None None None 2018-08-14 13:52:09 UTC

Description Jonathon Turel 2018-08-14 13:52:08 UTC
Reopen of Bug #24347, partially resolved.

Errors when browsing to a content host and then trying to update individual “applicable” packages that have been identified - despite the result being a “success”.

The "update all packages" now works as of Katello 3.7, but "upgrade selected" remains broken.

error output in /var/log/messages remains unchanged from Katello 3.6:

Aug  2 12:44:26 removed_host goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://removed_host.domain.com:5647
Aug  2 12:44:26 removed_host goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://removed_host.domain.com:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Aug  2 12:44:26 removed_host goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:92 - opened: proton+amqps://removed_host.domain.com:5647
Aug  2 12:44:26 removed_host goferd: [INFO][worker-0] gofer.messaging.adapter.connect:30 - connected: proton+amqps://removed_host.domain.com:5647
Aug  2 12:44:26 removed_host goferd: [INFO][worker-0] gofer.rmi.dispatcher:577 - call: Content.update() sn=50efe15e-05dc-418c-83e4-70f97fb27a17 data={u'task_id': u'7603d665-3c7d-401a-a94f-1fd3e30c4b68', u'consumer_id': u'ca5ccc28-961b-4a81-ac33-cc3d4f884890'}
Aug  2 12:44:26 removed_host env: Loaded plugins: enabled_repos_upload, fastestmirror, package_upload, product-id,
Aug  2 12:44:26 removed_host env: : search-disabled-repos, subscription-manager
Aug  2 12:44:30 removed_host env: Loading mirror speeds from cached hostfile
Aug  2 12:44:30 removed_host env: * epel: mirrors.coreix.net
*Aug  2 12:44:30 removed_host env: No Match for argument: *:rsyslog-8.24.0-16.el7_5.4.x86_64-*-*.**
Aug  2 12:44:30 removed_host goferd: [INFO][worker-0] gofer.agent.rmi:144 - Request: 50efe15e-05dc-418c-83e4-70f97fb27a17 processed in: 5.525 (seconds)
Aug  2 12:44:30 removed_host goferd: [INFO][worker-0] gofer.agent.rmi:190 - Request: 50efe15e-05dc-418c-83e4-70f97fb27a17, committed
Aug  2 12:44:30 removed_host goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:131 - closed: proton+amqps://removed_host.domain.com:5647
Aug  2 12:44:41 removed_host systemd: Removed slice User Slice of root.
Aug  2 12:44:41 removed_host systemd: Stopping User Slice of root.
Aug  2 12:45:45 removed_host chronyd[703]: Selected source removed_IP

Katello


Katello RPM's:

Server side:

foreman-installer-katello-3.7.0-1.el7.noarch
tfm-rubygem-katello-3.7.0-1.el7.noarch
pulp-katello-1.0.2-1.el7.noarch
katello-service-3.7.0-4.el7.noarch
katello-certs-tools-2.4.0-1.el7.noarch
katello-selinux-3.0.3-1.el7.noarch
katello-debug-3.7.0-4.el7.noarch
katello-default-ca-1.0-1.noarch
katello-common-3.7.0-4.el7.noarch
katello-3.7.0-4.el7.noarch
katello-server-ca-1.0-1.noarch
katello-repos-3.7.0-3.el7.noarch
tfm-rubygem-hammer_cli_katello-0.13.4-1.el7.noarch
katello-installer-base-3.7.0-1.el7.noarch

Client Side:

katello-ca-consumer-ueavmtest02.uea.ac.uk-1.0-1.noarch
katello-host-tools-fact-plugin-3.3.4-1.el7.noarch
katello-agent-3.3.4-1.el7.noarch
katello-client-repos-3.7.0-3.el7.noarch
katello-host-tools-3.3.4-1.el7.noarch


foreman debug uploaded as:
http://debugs.theforeman.org/foreman-debug-vcvEl.tar.xz

Comment 1 Jonathon Turel 2018-08-14 13:52:11 UTC
Created from redmine issue http://projects.theforeman.org/issues/24523

Comment 2 Jonathon Turel 2018-08-14 13:52:13 UTC
Upstream bug assigned to None

Comment 4 Satellite Program 2018-08-14 14:08:58 UTC
Upstream bug assigned to jturel

Comment 5 Satellite Program 2018-08-28 18:08:43 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24523 has been resolved.

Comment 7 Jameer Pathan 2018-09-18 12:22:41 UTC
verified:

@satellite 6.4.0 snap22

katello RPM's

Client side:
# rpm -qa | grep katello
katello-ca-consumer-<sat_host>-1.0-1.noarch
katello-host-tools-tracer-3.3.5-1.el7sat.noarch
katello-agent-3.3.5-1.el7sat.noarch
katello-host-tools-3.3.5-1.el7sat.noarch
katello-host-tools-fact-plugin-3.3.5-1.el7sat.noarch

server side:
# rpm -qa | grep katello
katello-server-ca-1.0-1.noarch
tfm-rubygem-hammer_cli_katello-0.13.4.1-1.el7sat.noarch
katello-installer-base-3.7.0.4-1.el7sat.noarch
katello-certs-tools-2.4.0-2.el7sat.noarch
tfm-rubygem-katello-3.7.0.28-1.el7sat.noarch
katello-3.7.0-7.el7sat.noarch
katello-service-3.7.0-7.el7sat.noarch
katello-default-ca-1.0-1.noarch
katello-selinux-3.0.3-2.el7sat.noarch
katello-debug-3.7.0-7.el7sat.noarch
katello-common-3.7.0-7.el7sat.noarch
foreman-installer-katello-3.7.0.4-1.el7sat.noarch
katello-ca-consumer-sat-r220-02.lab.eng.rdu2.redhat.com-1.0-6.noarch
pulp-katello-1.0.2-5.el7sat.noarch
katello-client-bootstrap-1.6.0-1.el7sat.noarch


steps:
1. set up a content host with katello-agent running
2. install a package which has an applicable update
3. go to hosts > content hosts > select host
4. go to Applicable Packages page of that host(Packages > Applicable)
4. select Packages, and click on "upgrade selected"

observation:
the selected applicable packages upgraded successfully.
No errors found in logs.

Comment 8 Bryan Kearney 2018-10-16 19:17:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927

Comment 9 Bryan Kearney 2018-11-02 11:50:10 UTC
*** Bug 1613237 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.