I started with the assumption this is an selinux-policy issue, but since the issue occurs also when SELinux is in permissive mode, it is more likely to be a cockpit-specific issue (further, it does not occur in virt-manager)
I have not used cockpit since May or June, so I do not know when that issue was introduced. But given that I experienced it already in the last version (so the one that is currently in stable) and also in this new one, whereas I assume that several users use cockpit for managing virtual machines, I am not sure if that issue is reproducible always (can anyone confirm about remote viewer of virtual machines?). The maintainer might review the mentioned bug ticket. I assume it will be moved from the selinux-policy component to cockpit anyway.
This issue is specific to managing virtual machines in cockpit. Everything else seems to work.
Can anyone verify if they are able to start virtual machines in cockpit and then open the remote viewer?
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
With regards to my negative karma of yesterday: it seems in the bug ticket that another user has the same issue: remote viewer did no longer work. But there is a chance that the origin is that cockpit lost compatibility to some older VM configurations, which means that changing VM config to a setting supported by cockpit fixes the issue. I couldn't verify yet.
But there is a chance that the origin is that cockpit lost compatibility to some older VM configurations, which means that changing VM config to a setting supported by cockpit fixes the issue
It seems this sentence of my recent post is not correct. I think there is a bug in cockpit (likely already in earlier versions) and that the remote viewer button is broken, at least in some configurations. More in the bug ticket BZ#2310648.
I think this bug would not appear in the Test Case of cockpit. Not sure if someone can verify if the remote viewer button works for them? So, test if the issue described in BZ#2310648 also applies to them?
With regards to BZ#2310648, the bug was not in the package cockpitbut in cockpit-machines. It has been fixed with cockpit-machines-319-1.fc40. I thus change karma for cockpit
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for testing by packit.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Works for me..
This update has been pushed to testing.
There is an issue with cockpit. It affects at least the last version but also this new one: see https://bugzilla.redhat.com/show_bug.cgi?id=2310648
I started with the assumption this is an selinux-policy issue, but since the issue occurs also when SELinux is in permissive mode, it is more likely to be a cockpit-specific issue (further, it does not occur in
virt-manager)I have not used cockpit since May or June, so I do not know when that issue was introduced. But given that I experienced it already in the last version (so the one that is currently in stable) and also in this new one, whereas I assume that several users use cockpit for managing virtual machines, I am not sure if that issue is reproducible always (can anyone confirm about remote viewer of virtual machines?). The maintainer might review the mentioned bug ticket. I assume it will be moved from the
selinux-policycomponent tocockpitanyway.This issue is specific to managing virtual machines in cockpit. Everything else seems to work.
Can anyone verify if they are able to start virtual machines in cockpit and then open the remote viewer?
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
With regards to my negative karma of yesterday: it seems in the bug ticket that another user has the same issue: remote viewer did no longer work. But there is a chance that the origin is that cockpit lost compatibility to some older VM configurations, which means that changing VM config to a setting supported by cockpit fixes the issue. I couldn't verify yet.
It seems this sentence of my recent post is not correct. I think there is a bug in cockpit (likely already in earlier versions) and that the remote viewer button is broken, at least in some configurations. More in the bug ticket BZ#2310648.
I think this bug would not appear in the Test Case of cockpit. Not sure if someone can verify if the remote viewer button works for them? So, test if the issue described in BZ#2310648 also applies to them?
With regards to BZ#2310648, the bug was not in the package
cockpitbut incockpit-machines. It has been fixed with cockpit-machines-319-1.fc40. I thus change karma forcockpitThis update can be pushed to stable now if the maintainer wishes
This update has been obsoleted by cockpit-325-1.fc40.