Bug 1405378 - remove RHEV branding from guest agent area - oVirt 4.2 Channel name deprecation
Summary: remove RHEV branding from guest agent area - oVirt 4.2 Channel name deprecation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.19.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.0
: 4.20.4
Assignee: Tomáš Golembiovský
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-16 10:33 UTC by Vinzenz Feenstra [evilissimo]
Modified: 2019-04-28 13:26 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1350334
Environment:
Last Closed: 2017-12-20 11:08:13 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1350334 0 medium CLOSED remove RHEV branding from guest agent area 2021-02-22 00:41:40 UTC
oVirt gerrit 68594 0 master MERGED virt: Identify new VDSM VMs by metadata 2020-07-07 11:42:32 UTC
oVirt gerrit 68595 0 master MERGED virt: Configurable name for guest agent channel 2020-07-07 11:42:32 UTC
oVirt gerrit 68722 0 master MERGED virt: Refactor name vmchannels.{,LEGACY_}DEVICE_NAME 2020-07-07 11:42:32 UTC
oVirt gerrit 69600 0 master MERGED backend: Guest agent channel rebrand 2020-07-07 11:42:32 UTC

Internal Links: 1350334

Description Vinzenz Feenstra [evilissimo] 2016-12-16 10:33:07 UTC 
This is a follow up BZ for the RHEV branding removal, due to the fact that the renaming of the agent channel cannot be done in one step to allow the upgrade of oVirt/RHV to smooth without generating warnings about non-responsive guest agents. 

Since guest agents on the Guest OS are more likely to be upgraded AFTER the Hypervisors and the engine have been upgraded.

The deprecation has been introduced in 4.1 and the removal is a follow up for 4.2


+++ This bug was initially created as a clone of Bug #1350334 +++
Comment 1 Petr Matyáš 2017-09-22 14:42:29 UTC 
Verified on vdsm-4.20.3-16.gitc4b244c.el7.centos and ovirt-engine-4.2.0-0.0.master.20170920172148.git8366a0b.el7.centos.noarch
Comment 2 Sandro Bonazzola 2017-12-20 11:08:13 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.