Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1321041 - Content Host status is green, but shows "Warning" [NEEDINFO]
Content Host status is green, but shows "Warning"
Status: CLOSED WONTFIX
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Hosts (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity high (vote)
: GA
: Unused
Assigned To: John Mitsch
Perry Gagne
http://projects.theforeman.org/issues...
: Triaged
: 1325956 (view as bug list)
Depends On:
Blocks: 1321771
  Show dependency treegraph
 
Reported: 2016-03-24 10:20 EDT by John Mitsch
Modified: 2018-09-04 13:43 EDT (History)
8 users (show)

See Also:
Fixed In Version: rubygem-katello-3.0.0.26-1,rubygem-katello-3.0.0.48-1,rubygem-katello-3.0.0.58-1
Doc Type: Known Issue
Doc Text:
Hosts provisioned by Satellite, but not registered, are showing a green icon, indicating they are covered by a subscription. These should show a red icon, indicating they are not covered by a subscription. If this occurs during the 6.3 Beta and blocks your completion or evaluation of the Beta please contact Satellite Engineering via the beta email list for assistance.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-09-04 13:43:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
bkearney: needinfo? (dlah)


Attachments (Terms of Use)
host status as 'OK' with green dot (37.95 KB, image/png)
2016-05-13 08:31 EDT, Sachin Ghai
no flags Details
host subscription status as fully entitled (24.01 KB, image/png)
2016-05-13 08:31 EDT, Sachin Ghai
no flags Details
on content-host index page, subscription status "green" dot for atomic host (31.56 KB, image/png)
2016-05-17 08:11 EDT, Sachin Ghai
no flags Details
"Fully Entitled" on details page (60.91 KB, image/png)
2016-05-17 08:12 EDT, Sachin Ghai
no flags Details
"red" dot on subscriptions tab -> subscription status (30.97 KB, image/png)
2016-05-17 08:12 EDT, Sachin Ghai
no flags Details
error on "provisioning details" -> status and dot is green (61.79 KB, image/png)
2016-06-27 10:24 EDT, Sachin Ghai
no flags Details
warning on "provisioning details" -> status and dot is green (62.31 KB, image/png)
2016-06-27 10:26 EDT, Sachin Ghai
no flags Details
warning on "provisioning details" and dot is green, should be 'yellow' (62.17 KB, image/png)
2016-07-19 02:24 EDT, Sachin Ghai
no flags Details
provisioning details -> tick sign w/ warning text (44.47 KB, image/png)
2017-11-02 05:04 EDT, Sachin Ghai
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 14372 None None None 2016-04-26 13:01 EDT
Foreman Issue Tracker 14401 None None None 2016-04-06 09:46 EDT
Foreman Issue Tracker 15334 None None None 2016-06-07 15:44 EDT
Foreman Issue Tracker 15890 None None None 2016-07-28 14:13 EDT

  None (edit)
Description John Mitsch 2016-03-24 10:20:39 EDT
Description of problem:
The content host status is a green dot, but it shows "Warning" 

Version-Release number of selected component (if applicable):


How reproducible:
Easy

Steps to Reproduce:
1. Install a capsule normally
2. Check the content host details - provisioning details tab for that capsule.

Actual results:
In the status field - the dot is green but shows a warning

Expected results:
In the status field the dot should either be yellow and show Warning or Green and show "Fully entitled" (or a similar successful message)

Additional info:
screenshot http://www.clipular.com/c/5666756448747520.png?k=yqroXkU_JomZrASQPepyfKhKElQ
Comment 2 John Mitsch 2016-03-29 11:09:53 EDT
Created redmine issue http://projects.theforeman.org/issues/14372 from this bug
Comment 3 John Mitsch 2016-04-06 10:08:08 EDT
PR Merged https://github.com/Katello/katello/pull/5925
Comment 4 Bryan Kearney 2016-04-06 10:10:50 EDT
Moving to POST since upstream bug http://projects.theforeman.org/issues/14372 has been closed
-------------
John Mitsch
Applied in changeset commit:katello|d31dff1eaa26ee3e7390c820457c129a58e5d413.
Comment 5 Sachin Ghai 2016-04-19 03:48:43 EDT
*** Bug 1325956 has been marked as a duplicate of this bug. ***
Comment 6 Brad Buckingham 2016-04-19 08:18:52 EDT
When verifying this bug, recommend verifying the behavior for both an atomic and non-atomic host.  Refer to duplicate bug 1325956 for details on the atomic scenario.
Comment 7 Brad Buckingham 2016-04-25 13:33:05 EDT
WORKAROUND: 

The correct status is represented by the text (e.g. Warning) and not the color.  As an alternative, the user can also view the status by doing the following in the UI:
- Go to Hosts -> All Hosts
- Select the host
- View the Properties -> Status
Comment 8 Sachin Ghai 2016-05-13 08:29:25 EDT
Verified with sat6.2 GA snap10

I can see host status 'Green' with text 'OK' under content host details - provisioning details and Subscription Status as 'Fully Entitled'. Please see the attached screenshot.
Comment 9 Sachin Ghai 2016-05-13 08:31 EDT
Created attachment 1157107 [details]
host status as 'OK' with green dot
Comment 10 Sachin Ghai 2016-05-13 08:31 EDT
Created attachment 1157109 [details]
host subscription status as fully entitled
Comment 11 Sachin Ghai 2016-05-13 08:33:19 EDT
Need to check for atomic host, so keeping it in on_qa
Comment 12 Sachin Ghai 2016-05-17 08:09:07 EDT
Ok, I provisioned atomic host via satellite6.2 snap11.0 and on content-host -> indev page, I can see the "Green" dot under "subscription status.

under "provisioning details" ->  "yellow" dot and text "Warning"

under subscription tab -> subscription status - "Red" dot

Under atomic content-host -> details -> subscription status -> Full entitled.


Since host is already associated with "Red Hat Atomic host ostree contents" subscription then  subscription tab -> subscription status  shouldn't show "Red" dot.

@John: Could you please confirm if its expected behaviour ?. thanks
Comment 13 Sachin Ghai 2016-05-17 08:11 EDT
Created attachment 1158258 [details]
on content-host index page, subscription status "green" dot for atomic host
Comment 14 Sachin Ghai 2016-05-17 08:12 EDT
Created attachment 1158259 [details]
"Fully Entitled" on details page
Comment 15 Sachin Ghai 2016-05-17 08:12 EDT
Created attachment 1158261 [details]
"red" dot on subscriptions tab -> subscription status
Comment 16 Sanket Jagtap 2016-05-30 07:58:29 EDT
Similar issue with snap13.1 build.
Comment 17 John Mitsch 2016-06-07 11:39:21 EDT
Sachin,

Sorry for the delayed response, I do not believe that is correct behavior and I am looking into it further. I will update here when I figure out further information and what I think the next steps should be.
Comment 18 John Mitsch 2016-06-07 13:30:55 EDT
Sachin,

Looks like that is an issue that needs to be fixed as part of this BZ. I am setting this back to assigned and am looking into it.
Comment 19 Bryan Kearney 2016-06-07 14:15:07 EDT
Upstream bug component is Provisioning
Comment 20 John Mitsch 2016-06-07 15:56:07 EDT
Added an issue for the aforementioned issue with the content host details > subscription tab showing the wrong sub status. This seems to be happening across all hosts.

PR here - https://github.com/Katello/katello/pull/6107
Comment 21 Bryan Kearney 2016-06-07 16:13:39 EDT
Upstream bug component is Hosts
Comment 22 Bryan Kearney 2016-06-08 08:17:30 EDT
John... is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1337522
Comment 23 John Mitsch 2016-06-08 09:15:41 EDT
Bryan,

That BZ (1337522) is a different issue, it addresses subscription status showing green instead of red. 

I am fixing:

1) Showing incorrect text with a color (i.e. green dot with "Warning")
2) Content Host details > Subscriptions tab > Subscription status always showing a red status with no text.

Let me know if I can further clarify anything.
Comment 24 Sachin Ghai 2016-06-27 09:01:08 EDT
Verified with sat62 GA snap17. the reported issue is still reproducible with sat6.2 snap17.

Under provisioning details -> status: I can see Error, with green dot for one host. and for another host warning (with green dot).
Comment 25 Sachin Ghai 2016-06-27 10:24 EDT
Created attachment 1172890 [details]
error on "provisioning details" -> status and dot is green
Comment 26 Sachin Ghai 2016-06-27 10:26 EDT
Created attachment 1172891 [details]
warning on "provisioning details" -> status and dot is green
Comment 27 John Mitsch 2016-06-27 10:42:58 EDT
Sachin,

Can you provide me with the steps you took to reproduce this error?
Comment 28 Sachin Ghai 2016-06-28 03:07:05 EDT
Hey John, 

Just provision a new host with hostgroup from satellite but without associating activation-key to hostgroup and you will see green dot, with "warning". In other words, host provisioned via satellite should not be registered with server.

The other issue "Error" with green dot is something when host is not reachable to Satellite server. Its hard to reproduce. I'll see if I can reproduce it.
Comment 30 John Mitsch 2016-06-28 09:10:06 EDT
Sure thing, will look into it ASAP
Comment 31 John Mitsch 2016-07-05 15:19:17 EDT
Made the fix upstream and referenced the original issue - https://github.com/Katello/katello/pull/6166
Comment 32 Sachin Ghai 2016-07-19 02:23:09 EDT
Verified with Sat62 GA snap20.2.

Case1 - For registered and provisioned atomic host via satellite:
==================================================================

Under Details tab:
- katello-agent yellow(dot) - not installed
- subscription - green(dot) - Fully entitled

under "provisioning details"
  - yellow(dot) with Warning text
  - green(dot) with Fully entitled.

Case2- For registered and provisioned via Satellite host:
=================================================

Under Details tab:
- katello-agent green(dot) - Installed
- subscription - green(dot) - Fully entitled

under "provisioning details"
  - Green(dot) with OK text 
  - green(dot) with Fully entitled.


Case3 - For unregistered host but provisioned via Satellite:
====================================================
Under Details tab:
no subscription status, as host is not registered

under "provisioning details"
  - Green(dot) with Warning text


Please note that case3 is not working as expected. I should see 'yellow' dot with warning text instead of green.
Comment 33 Sachin Ghai 2016-07-19 02:24 EDT
Created attachment 1181416 [details]
warning on "provisioning details" and dot is green, should be 'yellow'
Comment 35 John Mitsch 2016-07-19 15:05:41 EDT
Sachin,

Can you give some more details on how you provisioned the host? It would make it easier for me to reproduce as this mismatch seems to be happening on very specific cases.
Comment 36 Sachin Ghai 2016-07-20 02:01:10 EDT
Hey John,

I provisioned the host via Satellite but without associating hostgroup and activation key. This way host was provisioned successfully but didn't get registered.
Comment 39 Corey Welton 2017-10-24 08:24:04 EDT
qa -> pgagne
Comment 40 Sachin Ghai 2017-11-02 04:59:47 EDT
In 6.3 presentation of content host subscriptions status changed from colored dots to "tick" mark, though I can still see the original reported issue.


Steps to reproduce:

a) Provision a host through satellite
b) do not associate activation-key when creating  a new host
c) once host is provisioned, goto -> content-host-provisioning details tab
Comment 41 Sachin Ghai 2017-11-02 05:04 EDT
Created attachment 1346896 [details]
provisioning details -> tick sign w/ warning text

Please note that tick sign shouldappear w/ 'OK' text and "!" appears w/ warning.

So here either we should "tick" ok OR "!warning" but not "tick warning". Hope I'm clear :)
Comment 42 John Mitsch 2017-11-02 09:09:03 EDT
note to self for reproducing: provision host w/ no host group + no activation key using UI, check provision tab
Comment 44 Bryan Kearney 2018-09-04 13:43:01 EDT
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

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