Bug 1275370 - Issues with virt-who after upgrade
Issues with virt-who after upgrade
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Docs Upgrading and Updating Red Hat Satellite (Show other bugs)
Unspecified Unspecified
medium Severity medium (vote)
: GA
: 6.3
Assigned To: Russell Dickenson
Melanie Corr
Depends On:
  Show dependency treegraph
Reported: 2015-10-26 13:06 EDT by Deon Ballard
Modified: 2017-12-19 16:18 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-19 16:16:30 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Deon Ballard 2015-10-26 13:06:44 EDT
Document URL: 

A consultant encountered some issues when he was working with a customer to upgrade their environment from 6.0 to 6.1. For their virtual instances, they had some issues when upgrading virt-who:

* There is no virt-who upgrade information. 

* How does virt-who handle passwords with special characters during upgrade?

* If hypervisor UUIDs are converted to hostnames, Satellite treats them as new hypervisors and it requires that any subscriptions be reassigned and  old entries to be deleted manually.
    --> Is changing from a UUID to a hostname/FQDN as the identifier even supported?

Somewhat related bug:
Comment 2 Andrew Dahms 2017-11-20 19:08:11 EST
Assigning to Russell for review.

Russell - the Virtual Instances Guide since gained a note about changing from UUID to host name, and as per our conversation on IRC, it looks like the main work now is to call out that virt-who is an RPM upgrade that doesn't really require any special steps in the Upgrade Guide.

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