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 1745964

Summary: no indication of insights connectivity
Product: Red Hat Enterprise Linux 8 Reporter: Andreas Nilsson <anilsson>
Component: cockpitAssignee: Marius Vollmer <mvollmer>
Status: CLOSED ERRATA QA Contact: Jan Ščotka <jscotka>
Severity: medium Docs Contact: Lucie Vařáková <lmanasko>
Priority: high    
Version: 8.1CC: csnyder, lmanasko, mpitt, mvollmer, wchadwic
Target Milestone: rcKeywords: Triaged
Target Release: 8.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: If a system is not registered with insights, this fact is now highlighted when logging into a system via the Cockpit Web Console. Reason: While it is necessary to subscribe a system in order to register with Insights, Insights is the real value. Users who subscribed, but don't use Insights are not taking advantage of their RHEL subscription.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:03:23 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:

Description Andreas Nilsson 2019-08-27 10:49:47 UTC
With the work landing soon in https://github.com/candlepin/subscription-manager/pull/2089 for adding the capability to connect your system to Insights as part of registering the system, we need a way to indicate easily when a system is not connected to Insights. In fact, this should be treated as a sub-optimal state of a system, since it's not making full use of the value the subscription gives.

This is more or less the same as bug #1745534, but for the web console instead of the terminal.

Related Jira ticket: https://projects.engineering.redhat.com/browse/COCKPIT-475

Comment 1 Marius Vollmer 2019-09-09 08:25:38 UTC
This needs changes to the "System" overview page, not to the subscription manager UI.  I'll move this bug to us.

Comment 4 Martin Pitt 2019-09-09 20:10:00 UTC
The RHEL 8 specific implementation on Cockpit's system page is ready to land now: https://github.com/cockpit-project/cockpit/pull/12737

Comment 9 Martin Pitt 2019-10-11 06:56:13 UTC
Adding release note to avoid forgetting about it, but this isn't visible in 8.1 yet until the corresponding subscription-manager part lands (in 8.2 most probably)

Comment 11 errata-xmlrpc 2019-11-05 22:03:23 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-2019:3518