Bug 1917011
Summary: | cockpit-ovirt-dashboard confilct with cockpit-bridge cockpit-system - Engine no longer boots | ||
---|---|---|---|
Product: | [oVirt] ovirt-distribution | Reporter: | penguinpages <jeremey.wise> |
Component: | ovirt-host | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavol Brilla <pbrilla> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4.4 | CC: | arachman, bugs, cshao, didi, gdeolive, lsvaty, mavital, michal.skrivanek, mperina, peyu, sbonazzo, shlei, sradco, weiwang, yaniwang |
Target Milestone: | ovirt-4.4.5 | Flags: | pm-rhel:
ovirt-4.4+
pm-rhel: planning_ack+ sbonazzo: devel_ack+ gdeolive: testing_ack+ |
Target Release: | 4.4.5 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-host-4.4.5-1 | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-04-13 10:40:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1921014 |
Description
penguinpages
2021-01-16 14:16:23 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again. Please note that Nir pushed another relevant patch [1]. Mine was enough for fixing 'dnf update', but I didn't verify the implications. [1] https://gerrit.ovirt.org/c/ovirt-host/+/113025 *** Bug 1911910 has been marked as a duplicate of this bug. *** QE: I didn't verify anything other than 'dnf install'. Please make sure that it's still possible to to a hosted-engine deployment from cockpit. If this requires installing additional packages, please detail which ones. Also please note that while the bug affects only Stream (right now), you should verify on el 8.3, as we currently postponed the plan to migrate oVirt to Stream. ..please note that while the bug affects only Stream (right now), you should verify on el 8.3, as we currently postponed the plan to migrate oVirt to Stream.... With CentOS being end of support.. I "Assumed" that conversion to streams would have been fairly simple.. It seems that was bad idea. And with this being one of those "core components" to manage the hardware.. once I did the switch, I ended up destroying the environment.. and their is no "going back" I understand the concept of CentOS Streams as a more "agile" OS .. and so I support it on some sides.. but without safety net with things like "oVirt engine" ... this makes me a bit more concerned. I considered going to use the RHEL (new 16 free subscriptions) but it will not help me (and others like me) where we learn on CentOS and avoid getting in trouble with $$ .. to feed into what we use in production... Also learn the tech before deciding path and process for production. But when I need more than base subscription channels.. the "16 free subscriptions" does little for me. I need gluster, HCI, and Identity Manager. aka.. datacenter in a small box... all of which are premium channel subscriptions. Question: 1) When will centos streams get oVirt support? 2) If, due premium feature "subscription" features... I have to stick with Streams.. will I be able to post and get feedback of issues here and get response/support, or be cut off as it is a "streams" issue? (In reply to penguinpages from comment #5) > Question: > 1) When will centos streams get oVirt support? We do not have concrete plans yet. We started working on this with the intention of full support in 4.4.5, but had to postpone this. > 2) If, due premium feature "subscription" features... I have to stick with > Streams.. will I be able to post and get feedback of issues here and get > response/support, or be cut off as it is a "streams" issue? Once oVirt supports CentOS Stream, it will be supported :-). Before that, if you do try it and file bugs, they'll definitely be handled, based on priority, just like any other bug - but please remember that bugs that require fixes in CentOS Stream, will have to wait until they are available there. (In reply to Yedidyah Bar David from comment #6) > Once oVirt supports CentOS Stream, it will be supported :-). According to the oVirt website, they have supported CentOS Stream since oVirt 4.4.1. So, almost exactly seven months. (In reply to Anthony from comment #7) > (In reply to Yedidyah Bar David from comment #6) > > Once oVirt supports CentOS Stream, it will be supported :-). > > According to the oVirt website, they have supported CentOS Stream since > oVirt 4.4.1. So, almost exactly seven months. Link, please. Thanks. If you refer to [1], it says "Tech Preview". See also bug 1907831. It currently targets 4.4.6, but I am not sure it will not be postponed further. [1] https://www.ovirt.org/download/ (In reply to Yedidyah Bar David from comment #8) > (In reply to Anthony from comment #7) > > (In reply to Yedidyah Bar David from comment #6) > > > Once oVirt supports CentOS Stream, it will be supported :-). > > > > According to the oVirt website, they have supported CentOS Stream since > > oVirt 4.4.1. So, almost exactly seven months. > > Link, please. Thanks. > > If you refer to [1], it says "Tech Preview". > > See also bug 1907831. It currently targets 4.4.6, but I am not sure it will > not be postponed further. > > [1] https://www.ovirt.org/download/ So the official Red Hat position is that the "Tech Preview" parenthetical, which appears to describe what CentOS Stream is, as well as the oVirt 4.4.1 release announcement[1] which states, "You can now use CentOS Stream as an alternative to CentOS Linux on non-production systems.", are not intended to be used as indicators that CentOS Stream is a supported operating system for oVirt? That's disappointing. [1] https://blogs.ovirt.org/2020/07/ovirt-4-4-1-now-available/ |