Bug 2098167
| Summary: | Missing overrides information in cockpit/web console documentation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Steve Barcomb <sbarcomb> |
| Component: | Documentation | Assignee: | Mayur Patil <maypatil> |
| Documentation sub component: | default | QA Contact: | |
| Status: | CLOSED MIGRATED | Docs Contact: | Mayur Patil <maypatil> |
| Severity: | medium | ||
| Priority: | high | CC: | kwalker, lmanasko, maypatil, mpitt, rhel-docs, tcapek |
| Version: | 8.7 | Keywords: | Documentation, MigratedToJIRA, Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-15 13:03:14 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
Steve Barcomb
2022-06-17 13:24:22 UTC
> A correction to the upstream documentation though. The above links says to put this information into /etc/cockpit, but in testing this looks to be required in /usr/share/cockpit in each directory within that a customer wishes to disable. /usr/share/cockpit/$page/override.json was indeed the old location, before cockpit 265 [1]. That is refered to with "A file called override.json may be placed next to the manifest". But this is awkward, as /usr/share/ is package manager territory, and users/admins really should not write there. It's not even possible with OSTree systems like RHEL Edge or Fedora CoreOS. So possibly you tested on RHEL 8.6 or earlier? RHEL 8.7 supports this new path. > Additionally, the version of cockpit that I think is coming in RHEL8.7 cockpit-271 seems to allow disablement on a per user basis with those overrides files being placed in ~/.config/cockpit/<system> which does not yet seems to be documented upstream. If you mean that ~/.config/cockpit/systemd/override.json could override /usr/share/cockpit/systemd/manifest.json, then no, that's not supported (and not planned). See [2]. We only support ~/.config/cockpit/systemd.override.json (i.e. flat hierarchy in the cockpit/ directory, not a tree), and that is documented. [1] https://cockpit-project.org/blog/cockpit-265.html [2] https://github.com/cockpit-project/cockpit/commit/f0f497655b62b4efcef3ad0b31bb6d9137d184b5#diff-a5bc1c4fb29285eb87cb819cca5fb3183d556933bf927a0224ee12bbc7c2c634R409 Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |