Bug 2116385 - [RFE] Add deprecation warning/banner on Compute Resources page about deprecation of RHEV support
Summary: [RFE] Add deprecation warning/banner on Compute Resources page about deprecat...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.12.0
Assignee: Leos Stejskal
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-08 12:50 UTC by Ashish Humbe
Modified: 2022-11-16 13:35 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman_theme_satellite-10.0.0.4-1
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:35:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35365 0 High New Add deprecation warning about RHEV/Ovirt support 2022-08-15 08:22:25 UTC
Red Hat Issue Tracker SAT-12206 0 None None None 2022-09-21 14:26:01 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:35:22 UTC

Description Ashish Humbe 2022-08-08 12:50:58 UTC
Description of problem:

Add a deprecation warning/banner on Compute Resources page about the deprecation of RHEV support

With satellite 6.12 we are announcing the deprecation of RHEV as Compute Resource, we should add warning/note in the Satellite webui to educate customers like we added webui based warning/banner for katello-agent/ Puppet 

We should add a deprecation warning on the Compute Resources page( https://satellite.example.com/compute_resources) with the below conditions

1. If one had already created RHEV CR they should see the warning/banner.
2. If one is trying to create a new RHEV CR, they should also see the warning/banner.



Version-Release number of selected component (if applicable):
Satellite 6.12

Comment 1 Leos Stejskal 2022-08-15 08:20:34 UTC
Hi,
can I get some source of the information that can be linked in the warning message?
I assume that "Ovirt is deprecated" won't be enough and we should point users to some
article / page describing what is going on.

Comment 2 Leos Stejskal 2022-08-15 08:22:25 UTC
Created redmine issue https://projects.theforeman.org/issues/35365 from this bug

Comment 7 Lukáš Hellebrandt 2022-10-06 14:41:16 UTC
Verified with Sat 6.12 snap 13.0.

The following message (in a div with orange background) is now shown in these places:
Creating a new CR when selecting type==RHV.
Creating (or editing) a Compute Profile that is tied to the CR of type==RHV.
The page that is displayed when opening the CR info (Infrastructure -> Compute Resources -> <compute_resource>) of type==RHV.

No changes in Hammer (but the banner is correctly displayed in WebUI for RHV CRs created through Hammer). The CR can still be used the same way as before. The link "More information" points to document https://access.redhat.com/announcements/6960518 .

```
RHEV integration is deprecated.
On August 31, 2022, Red Hat Virtualization entered the Maintenance Support Phase. The Maintenance Support Phase runs until August 31, 2024, followed by the Extended Life Phase, which runs until August 31, 2026. More information

```

The only minor issue is on the CR page (Infra -> CRs -> <CR>), the banner is now shown in the table with CR info in the right column, with left column being empty. It would look better above the table. But that'ws not a reason not to verify this BZ. Given the temporary nature of the banner, I don't think I will even file a follow-up BZ about this.

Comment 11 errata-xmlrpc 2022-11-16 13:35:13 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 (Important: Satellite 6.12 Release), 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/RHSA-2022:8506


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