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 1466423 - cockpit broken after latest updates
Summary: cockpit broken after latest updates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dominik Perpeet
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-29 14:31 UTC by Marko Myllynen
Modified: 2017-07-04 16:51 UTC (History)
3 users (show)

Fixed In Version: cockpit-141-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-04 09:39:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1673 0 normal SHIPPED_LIVE cockpit bug fix and enhancement update 2017-07-04 13:39:47 UTC

Description Marko Myllynen 2017-06-29 14:31:52 UTC 
Description of problem:
After updates released on 2017-06-28 we see now the following packages being available:

cockpit-bridge-138-6.el7.x86_64
cockpit-dashboard-141-1.el7.x86_64
cockpit-docker-141-1.el7.x86_64
cockpit-kubernetes-141-1.el7.x86_64
cockpit-pcp-141-1.el7.x86_64
cockpit-system-138-6.el7.noarch
cockpit-ws-138-6.el7.x86_64

The version mismatch prevent e.g. the dashboard opening.
Comment 3 Dominik Perpeet 2017-06-29 15:32:58 UTC 
(In reply to Marko Myllynen from comment #0)
> Description of problem:
> After updates released on 2017-06-28 we see now the following packages being
> available:
> 
> cockpit-bridge-138-6.el7.x86_64
> cockpit-dashboard-141-1.el7.x86_64
> cockpit-docker-141-1.el7.x86_64
> cockpit-kubernetes-141-1.el7.x86_64
> cockpit-pcp-141-1.el7.x86_64
> cockpit-system-138-6.el7.noarch
> cockpit-ws-138-6.el7.x86_64
> 
> The version mismatch prevent e.g. the dashboard opening.

I can confirm this is happening and I see the cause - there's a wrong manifest.json dependency in the dashboard, ssh is also affected.
Comment 5 Dominik Perpeet 2017-06-29 15:42:16 UTC 
Workaround:

Edit the manifest.json files in /usr/share/cockpit:

/usr/share/cockpit/dashboard/manifest.json
-	"cockpit": "138.x"
+	"cockpit": "138"

and the same for /usr/share/cockpit/ssh/manifest.json
Comment 7 Marko Myllynen 2017-06-29 15:52:13 UTC 
(In reply to Dominik Perpeet from comment #5)
> Workaround:
> 
> Edit the manifest.json files in /usr/share/cockpit:
> 
> /usr/share/cockpit/dashboard/manifest.json
> -	"cockpit": "138.x"
> +	"cockpit": "138"
> 
> and the same for /usr/share/cockpit/ssh/manifest.json

Confirmed, this can be used to workaround the issue, thanks!
Comment 13 errata-xmlrpc 2017-07-04 09:39:58 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-2017:1673
Note You need to log in before you can comment on or make changes to this bug.