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

Bug 1039696

Summary: rhel-6-server-rhev-mgmt-agent-rpms should be disabled by default on Virtualization product
Product: Red Hat Enterprise Virtualization Manager Reporter: Marina Kalinin <mkalinin>
Component: relengAssignee: Jay Greguske <jgreguske>
Status: CLOSED CURRENTRELEASE QA Contact: Entitlement Bugs <entitlement-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: acathrow, adahms, aedwards, chetan, dgregor, eedri, iheim, jgreguske, yeylon
Target Milestone: ---   
Target Release: 3.3.1   
Hardware: All   
OS: Linux   
Whiteboard: releng
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-17 13:08:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Rel-Eng RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 902971, 1039701    

Description Marina Kalinin 2013-12-09 20:08:11 UTC
Currently rhel-6-server-rhev-mgmt-agent-rpms is enabled by default on Virtualization product on RHSM.
This is confusing and misleading. This channel should be disabled by default. And set by request only on the machine that needs it.

Why?
1. rhel-6-server-rhev-mgmt-agent-rpms channel is required for hypervisor only, for installing vdsm and related packages. On a standard setup, vdsmd is not supposed to run on the same machine where engine is running and it is just a better practice to have this channel disabled, and request the customers to enable it when needed only. Otherwise, customers may install vdsm packages on engine, without understanding what they are doing and overcomplicated things without a reason.

2. the behavior on rhn is different - one needs to subscribe to this channel separately, and it makes it very clear, what channel is needed for RHEV hypervisor. the behaviour for RHSM should be same (for the sake of clarity and avoiding confusion).

Steps to reproduce:
1. On RHEL6.5, register to RHSM and add RHEV product:
# subscription-manager register
# subscription-manager list --available | grep -A8 "Red Hat Enterprise Virtualization"
# subscription-manager subscribe --pool=virt_pool_id

Actual results:
# yum repolist  --> we can see that rhev-mgmt-agent is enabled by default:
~~~
repo id  repo name                status
>> rhel-6-server-rhev-mgmt-agent-rpms Red Hat Enterprise Virtualization Management Agents (RPMs)                      212
rhel-6-server-cf-tools-1-rpms Red  Hat CloudForms Tools for RHEL 6 (RPMs)  31
rhel-6-server-rhev-agent-rpms Red  Hat Enterprise Virtualization Agents for RHEL 6 Server (RPMs)               32
rhel-6-server-rhevh-rpms           Red Hat Enterprise Virtualization Hypervisor (RPMs)                             77
rhel-6-server-rpms                 Red Hat Enterprise Linux 6 Server (RPMs)                             12,002
~~~

Expected results:
# yum repolist  | grep  mgmt-agent-rpms  -> returns nothing
# yum-config-manager --enable rhel-6-server-rhev-mgmt-agent-rpms
# yum repolist  | grep  mgmt-agent-rpms  -> returns:
This system is receiving updates from Red Hat Subscription Management.
rhel-6-server-rhev-mgmt-agent-rpms  Red Hat Enterprise Virtualization Man    212

Comment 1 John Sefler 2013-12-09 21:25:28 UTC
The default enablement of the rhel-6-server-rhev-agent-rpms repository is controlled by the content sets defined by the release-engineering team, not subscription-manager itself.

Setting NEEDINFO on dgregor from rel-eng team who can better explain how/who decides what the default enable yum configuration should be for repo rhel-6-server-rhev-agent-rpms.

Side note: similar to yum-config-manager, you should use the following command to manually disable repo rhel-6-server-rhev-agent-rpms
# subscription-manager repos --disable=rhel-6-server-rhev-agent-rpms

Comment 2 Jay Greguske 2013-12-10 20:46:16 UTC
I'm going to come out and say no layered product should have repositories enabled by default any more. Why?

- reason #2 from Marina above
- many layered products have multiple versions supported at the same time
- it causes confusion when trying integrate layered products together: some are enabled and some are not

Comment 3 Jay Greguske 2014-01-13 16:51:49 UTC
Cheryn, can we coordinate this change in a documentation update? We will be adding a step to enable the VDSM channel when using the certificate-based RHN.

Comment 4 Cheryn Tan 2014-01-28 00:12:13 UTC
Sorry Jay, I missed this needinfo. Bugs 1039701 and 973962 will track the documentation updates. Seeing as this change has been acked for 3.3.1 the docs will also reflect this change on the z-stream update.

Comment 5 Eyal Edri 2014-02-04 13:15:41 UTC
we're building 3.3.1 today and releasing to QE tomorrow, this bug is relevant for the release?

Comment 11 Red Hat Bugzilla 2023-09-14 01:55:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days