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.
Bug 1135620 - yum install katello-agent is not updating katello-agent status in UI
Summary: yum install katello-agent is not updating katello-agent status in UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
: 1201514 1337776 (view as bug list)
Depends On:
Blocks: 1130651
TreeView+ depends on / blocked
 
Reported: 2014-08-29 19:44 UTC by sthirugn@redhat.com
Modified: 2020-08-13 22:20 UTC (History)
12 users (show)

Fixed In Version: katello-agent-2.5.0-5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:08:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15012 0 Normal Closed yum install katello-agent is not updating katello-agent status in UI 2020-10-01 14:17:14 UTC
Red Hat Knowledge Base (Solution) 1385683 0 None None None 2020-08-13 22:20:01 UTC

Description sthirugn@redhat.com 2014-08-29 19:44:21 UTC 
Description of problem:
yum install katello-agent is not updating katello-agent status in UI

Version-Release number of selected component (if applicable):
GA Snap 7 - Satellite-6.0.4-RHEL-6-20140828.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.23-1.el6_5.noarch
* candlepin-common-1.0.1-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.23-1.el6_5.noarch
* candlepin-tomcat6-0.9.23-1.el6_5.noarch
* elasticsearch-0.90.10-6.el6sat.noarch
* foreman-1.6.0.42-1.el6sat.noarch
* foreman-compute-1.6.0.42-1.el6sat.noarch
* foreman-gce-1.6.0.42-1.el6sat.noarch
* foreman-libvirt-1.6.0.42-1.el6sat.noarch
* foreman-ovirt-1.6.0.42-1.el6sat.noarch
* foreman-postgresql-1.6.0.42-1.el6sat.noarch
* foreman-proxy-1.6.0.30-1.el6sat.noarch
* foreman-selinux-1.6.0.14-1.el6sat.noarch
* foreman-vmware-1.6.0.42-1.el6sat.noarch
* katello-1.5.0-30.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.62-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* openldap-devel-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-4.el6sat.noarch
* pulp-nodes-common-2.4.1-0.5.rc1.el6sat.noarch
* pulp-nodes-parent-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-tools-2.4.1-0.5.rc1.el6sat.noarch
* pulp-rpm-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-selinux-2.4.1-0.5.rc1.el6sat.noarch
* pulp-server-2.4.1-0.5.rc1.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch


How reproducible:
Always

Steps to Reproduce:
I performed the following actions in the content-host side and monitored the UI katello-agent status of content-host:

1. Registered a client (with katello-agent installed)  - GREEN - PASS
2. #service goferd stop   - still GREEN - OK for now
3. #yum remove katello-agent - Turned YELLOW - PASS
4. #yum install katello-agent - Still YELLOW - FAIL
5. #service goferd restart - Still YELLOW

Actual results:
After Step 4, Sat6 UI katello-agent status was still YELLOW

Expected results:
After Step 4, Sat6 UI katello-agent status should be GREEN

Additional info:
Comment 2 mlessard 2014-10-29 15:25:04 UTC 
By executing katello-package-upload, the status is updated.
Comment 3 Ken Hitchcock 2016-02-05 15:09:42 UTC 
still happening in satellite 6.1.5 05 Feb 2016. Installed Katello from yum not ISO.
Comment 4 sthirugn@redhat.com 2016-02-05 16:18:27 UTC 
I think this needs https://bugzilla.redhat.com/show_bug.cgi?id=1201514 for immediate status update otherwise it will take sometime until the content host report to satellite.  Anyways, manually triggering 'katello-package-upload' after registration should solve this for now.
Comment 5 Brad Buckingham 2016-05-09 18:48:29 UTC 
*** Bug 1201514 has been marked as a duplicate of this bug. ***
Comment 6 Brad Buckingham 2016-05-09 18:51:32 UTC 
Per bug 1201514, the resolution to this bug could be triggering katello-package-upload as part of the katello-agent install.
Comment 7 Stephen Benjamin 2016-05-11 16:59:14 UTC 
Created redmine issue http://projects.theforeman.org/issues/15012 from this bug
Comment 8 Bryan Kearney 2016-05-12 16:03:48 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/15012 has been closed
Comment 9 Kedar Bidarkar 2016-05-20 12:24:53 UTC 
step 4) yum install katello-agent -GREEN OK ( goferd service is seen running when we install the package)


VERIFIED with sat62-snap12.1
Comment 11 Kedar Bidarkar 2016-05-25 12:00:09 UTC 
This is working fine now and was VERIFIED with sat62-snap12.1 ( which is a Pre-GA Build, but Post-Beta Build )
Comment 12 Stephen Benjamin 2016-05-25 14:31:27 UTC 
*** Bug 1337776 has been marked as a duplicate of this bug. ***
Comment 13 Bryan Kearney 2016-07-27 11:08:05 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/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.