Bug 2035514 - cockpit-navigator won't work with cockpit-ws container (package dependencies)
Summary: cockpit-navigator won't work with cockpit-ws container (package dependencies)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cockpit-navigator
Version: 35
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: Stephen Gallagher
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-24 11:02 UTC by Johannes Pfau
Modified: 2022-01-16 00:57 UTC (History)
1 user (show)

Fixed In Version: cockpit-navigator-0.5.8-3.fc35 cockpit-navigator-0.5.8-3.fc34
Clone Of:
Environment:
Last Closed: 2022-01-08 01:19:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Johannes Pfau 2021-12-24 11:02:05 UTC
Description of problem:

cockpit-navigator currently depends on cockpit, which pulls in many more packages including cockpit-ws. For a containerized setup on Fedora CoreOS, the cockpit-ws part will run in a container and other components such as cockpit-navigator on the host.

However, the cockpit-ws container refuses to start if cockpit-ws is installed on the host. As cockpit-navigator pulls in the cockpit-ws dependency on the host, it therefore currently can't be used in this containerized setup.


Version-Release number of selected component (if applicable):
cockpit-navigator-0.5.8-1.fc35.noarch


Steps to Reproduce:
1. Use latest Fedora CoreOS
2. Run rpm-ostree install -n cockpit-navigator
3. See that cockpit-ws is installed as a dependency
4. Alternatively: Install using rpm-ostree install cockpit-navigator
5. Install cockpit-ws container
6. Reboot & try to start cockpit-ws container.

Actual results:
Starting cockpit-ws container complains "cockpit-ws must not be installed in the host" (https://github.com/cockpit-project/cockpit/blob/main/containers/ws/atomic-install#L26)

Expected results:
Container should start and be able to use cockpit-navigator.

Comment 1 Fedora Update System 2022-01-07 15:33:03 UTC
FEDORA-2022-c016c33b24 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c016c33b24

Comment 2 Fedora Update System 2022-01-07 15:33:06 UTC
FEDORA-2022-e1fcd1404a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e1fcd1404a

Comment 3 Fedora Update System 2022-01-08 01:09:39 UTC
FEDORA-2022-c016c33b24 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-c016c33b24`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c016c33b24

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2022-01-08 01:19:34 UTC
FEDORA-2022-e1fcd1404a has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2022-01-16 00:57:48 UTC
FEDORA-2022-c016c33b24 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.


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