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 1317687 - katello-agent status is not updated in UI
Summary: katello-agent status is not updated in UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Kedar Bidarkar
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1314746 1323722 1325656 1335737 (view as bug list)
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2016-03-14 21:08 UTC by sthirugn@redhat.com
Modified: 2019-11-14 07:36 UTC (History)
8 users (show)

Fixed In Version: rubygem-katello-3.0.0.26-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:19:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14251 0 Normal Closed katello-agent status is not updated in UI 2021-02-09 12:30:13 UTC

Description sthirugn@redhat.com 2016-03-14 21:08:18 UTC
Description of problem:
katello-agent status is shown as not installed even after successfully installing it in the host

Version-Release number of selected component (if applicable):
Satellite 6.2.0-beta-snap3.1

How reproducible:
Always

Steps to Reproduce:
1. Provision a host in satellite using a libvirt compute resource and using activation key
2. Host provisioned successfully and katello agent is installed fine.  
3. goferd status is active and running in the Host
4. Review WebUI -> Hosts -> Content Hosts -> `Katello Agent` field

Actual results:
Katello Agent shows `Not Installed`

Expected results:
Katello Agent should reflect `Installed` status as goferd is successfully running in the host.

Additional info:
I ran `katello-package-upload` many times in the host and it ran successfully without errors.

Comment 2 Justin Sherrill 2016-03-17 14:35:16 UTC
Created redmine issue http://projects.theforeman.org/issues/14251 from this bug

Comment 3 Bryan Kearney 2016-03-17 20:02:20 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14251 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|71c08a3b2fbf4993463be354e42040dd28de7f95.

Comment 4 Brad Buckingham 2016-04-05 15:40:19 UTC
*** Bug 1323722 has been marked as a duplicate of this bug. ***

Comment 5 Brad Buckingham 2016-04-20 17:24:41 UTC
*** Bug 1325656 has been marked as a duplicate of this bug. ***

Comment 6 Brad Buckingham 2016-04-20 17:26:11 UTC
*** Bug 1314746 has been marked as a duplicate of this bug. ***

Comment 7 Fred van Zwieten 2016-05-15 21:18:19 UTC
*** Bug 1335737 has been marked as a duplicate of this bug. ***

Comment 8 Kedar Bidarkar 2016-05-24 09:33:43 UTC
Katello-agent status now shows GREEN and works fine.


VERIFIED with sat62-snap12.1

Comment 9 Bryan Kearney 2016-07-27 11:19:27 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.