Bug 1997136 - Capsule status does not reflect correctly
Summary: Capsule status does not reflect correctly
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule
Version: 6.10.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-24 13:31 UTC by Kenny Tordeurs
Modified: 2023-08-17 12:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19628 0 None None None 2023-08-17 12:49:38 UTC

Description Kenny Tordeurs 2021-08-24 13:31:18 UTC
Description of problem:
Status for Capsule is green while it actually has issues with the pulp workers.

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

How reproducible:
100%

Steps to Reproduce:
1. Have a Capsule with some pulp worker problems
2.
3.

Actual results:
Status is green

Expected results:
Status red

Additional info:
Capsule status is able to determine issues about different versions installed and so on. It stands to reason it would reflect this issue also in the status.

Comment 2 Sayan Das 2021-08-24 14:04:35 UTC
Kenny, The situation is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1993288 ??

Comment 3 Kenny Tordeurs 2021-08-24 14:19:10 UTC
@Sayan, maybe in part however I'm mainly focusing on the status message itself being wrong at this point, I really do have some failed services :-)

Comment 4 Sayan Das 2021-08-24 14:21:36 UTC
Ah ok.. 

For me in https://bugzilla.redhat.com/show_bug.cgi?id=1993288 , I don't have any failed services but still due to some reason, the overall status is reflected as green whereas , the Pulp related error is there. :(


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