Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1744196

Summary: Incorrect message displayed for initial few seconds when launching subscription-manager from desktop
Product: Red Hat Enterprise Linux 8 Reporter: Rehana <redakkan>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED DUPLICATE QA Contact: Red Hat subscription-manager QE Team <rhsm-qe>
Severity: low Docs Contact:
Priority: medium    
Version: 8.1CC: candlepin-bugs, csnyder, jsefler, jstavel, mpitt
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 12:00:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
error
none
autorefresh none

Description Rehana 2019-08-21 13:52:01 UTC
Description of problem:


Version-Release number of selected component (if applicable):
subscription-manager-initial-setup-addon-1.25.14-1.el8.x86_64
cockpit-podman-4-1.module+el8.1.0+4016+4220c060.noarch
cockpit-bridge-196.2-1.el8.x86_64
cockpit-packagekit-197.2-1.el8.noarch
subscription-manager-1.25.14-1.el8.x86_64
subscription-manager-rhsm-certificates-1.25.14-1.el8.x86_64
subscription-manager-cockpit-1.25.14-1.el8.noarch
cockpit-system-196.2-1.el8.noarch
cockpit-196.2-1.el8.x86_64
subscription-manager-plugin-container-1.25.14-1.el8.x86_64
cockpit-ws-196.2-1.el8.x86_64
cockpit-storaged-197.2-1.el8.noarch


How reproducible:
Rhel8.1

Steps to Reproduce:
1.install GUI RHEL 8.1 --> during install I successfully registered and subscribed system from initial setup  
2.go to activities --> type "subscription-manage"
3.Click on the subscription-manager icon 

Actual results:
Message "Couldn't get system subscription status . please ensure subscription-manager is installed" (PFA : error.png) ; After few seconds the window refreshes and get the correct status as show in this screenshot ( autorefresh.png)

Expected results:
would nice if we can avoid the wrong message that appeared for few seconds 

Additional info:

Comment 1 Rehana 2019-08-21 13:52:36 UTC
Created attachment 1606549 [details]
error

Comment 2 Rehana 2019-08-21 13:53:23 UTC
Created attachment 1606550 [details]
autorefresh

Comment 11 Pino Toscano 2022-05-17 12:00:09 UTC

*** This bug has been marked as a duplicate of bug 1822242 ***