Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1405378

Summary:	remove RHEV branding from guest agent area - oVirt 4.2 Channel name deprecation
Product:	[oVirt] vdsm	Reporter:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Component:	Core	Assignee:	Tomáš Golembiovský <tgolembi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.19.0	CC:	bugs, lsurette, michal.skrivanek, mkenneth, pmatyas, pstehlik, rbalakri, riehecky, srevivo, vpagar, ykaul
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+ rule-engine: planning_ack+ rule-engine: devel_ack+ pstehlik: testing_ack+
Target Release:	4.20.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1350334	Environment:
Last Closed:	2017-12-20 11:08:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.