Bug 1275370 - Issues with virt-who after upgrade
Issues with virt-who after upgrade
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Docs Install Guide (Show other bugs)
Unspecified
Unspecified Unspecified
medium Severity medium (vote)
: GA
: 6.2
Assigned To: satellite-doc-list
satellite-doc-list
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-26 13:06 EDT by Deon Ballard
Modified: 2016-10-26 01:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
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: 
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server.html#sect-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server-Upgrading_Red_Hat_Satellite

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:
https://bugzilla.redhat.com/show_bug.cgi?id=1275365

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