Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1478589 - [RFE] [6.3] Note About Virt-Who Must Come From Red Hat Satellite Tools Repository.
Summary: [RFE] [6.3] Note About Virt-Who Must Come From Red Hat Satellite Tools Reposi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Virtual Instances Guide
Version: 6.2.10
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: Michaela Slaninkova
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-04 21:20 UTC by Bernie Hoefer
Modified: 2019-09-26 16:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-14 14:34:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bernie Hoefer 2017-08-04 21:20:48 UTC
Document URL:
<https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/virtual_instances_guide/prerequisites#installing_virt-who>


Section Number and Name:
4.5. Installing virt-who


Describe the issue:
The guide contains the following note:

  The virt-who package must be obtained from the
  Red Hat Satellite Tools repository as this provides
  the latest version.

This caused a customer confusion, as despite having both the rhel-7-server-rpms and rhel-7-server-satellite-tools-6.2-rpms repositories enabled, yum only showed the virt-who package from the rhel-7-server-rpms repository.  Example:


# yum info virt-who | grep -E ^Name\|^Version\|^Release\|^Repo
Name        : virt-who
Version     : 0.19
Release     : 2.el7sat
Repo        : rhel-7-server-rpms/7Server/x86_64


Once the customer was informed that when 2 repositories contain the same package at the same version & release level, yum (apparently) will use the 1st repository it found it in.  Yum will not mention the 2nd repository.  Disabling the rhel-7-server-rpms proves this to be true:


# yum --disablerepo rhel-7-server-rpms info virt-who | grep -E ^Name\|^Version\|^Release\|^Repo
Name        : virt-who
Version     : 0.19
Release     : 2.el7sat
Repo        : rhel-7-server-satellite-tools-6.2-rpms/x86_64



Suggestions for improvement:
Maybe change the note to read:
  To ensure one installs the latest virt-who package,
  enable the Red Hat Satellite Tools repository.  If both it
  and the Red Hat Enterprise Linux repository contain
  the latest package, yum may pull it from either.

Comment 1 Rich Jerrido 2017-08-07 01:51:09 UTC
It is NOT universally true that the version of virt-who provided in the Satellite tools channel is the newest. 

Which version of virt-who the users gets is dependent on 

- the RHEL release cadence. 
- whether or not a newer version is _required_ to be shipped in the Satellite tools repo. 


As a general rule, the only time a new version of virt-who is shipped in the Satellite tools repo is when there are a number of fixes or enhancements that Satellite requires that are needed in a quicket cadence than the RHEL release cycle (every 6-8 months). 

As this scenarios cannot be known in advance, the only sane course of action to tell the end user is

- on the system that runs virt-who, enable the Satellite Tools repo. 
- let yum pick _whichever_ package is the latest.

Comment 2 Andrew Dahms 2017-08-09 02:35:18 UTC
Assigning to Misha for review.

Misha - looks like we need to update the note in question to say that the virt-who package is available from either channel, and that the latest version, whichever repo it comes from, is the one that we should install.

Comment 6 Michaela Slaninkova 2017-08-14 14:36:19 UTC
Hello,

These changes are now live on the customer portal.

Comment 7 Andrew Dahms 2018-01-16 00:12:57 UTC
Updating the doc type.


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