Bug 1144443 - Can't delete virt-who created Hypervisor content hosts
Summary: Can't delete virt-who created Hypervisor content hosts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Li Bin Liu
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1142315
Blocks: 1132363
TreeView+ depends on / blocked
 
Reported: 2014-09-19 12:02 UTC by Stephen Benjamin
Modified: 2019-09-26 14:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When virt-who reports to katello, hypervisor content hosts are created. These hypervisor hosts could not be deleted from the Satellite Server because it was not being recognized as a pulp consumer, only a candlepin consumer. Changes were made to fix this and the ability has been added to delete a hypervisor content host.
Clone Of:
Environment:
Last Closed: 2014-11-13 22:29:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 7542 0 None None None 2016-04-22 15:04:20 UTC
Red Hat Product Errata RHBA-2014:1857 0 normal SHIPPED_LIVE Red Hat Satellite 6 server bug fix update 2014-11-14 03:28:23 UTC

Description Stephen Benjamin 2014-09-19 12:02:55 UTC 
Description of problem:
When virt-who reports to Katello, we create some Hypervisor objects which are basically dummy content hosts -- hosts without content, only a candlepin consumer.

Deleting them fails, we need to not attempt to destroy the pulp consumer on hypervisors.


Version-Release number of selected component (if applicable):
6.0.4 GA

How reproducible:
Always

Steps to Reproduce:
1. Use virt-who or virt-whom to report to Katello
2. Attempt to delete a hypervisor


Actual results:
Fails - can't find the pulp consumer

Expected results:
Succeeds
Comment 1 RHEL Program Management 2014-09-19 12:03:09 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Stephen Benjamin 2014-09-19 12:13:29 UTC 
Created redmine issue http://projects.theforeman.org/issues/7542 from this bug
Comment 4 Bryan Kearney 2014-09-21 20:05:11 UTC 
Upstream bug assigned to stbenjam
Comment 5 Bryan Kearney 2014-09-24 22:05:01 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/7542 has been closed
-------------
Anonymous
Applied in changeset commit:katello|13e4b3d5dca963e6f560ee8b172ee9da8a9e12c2.
Comment 8 gaoshang 2014-10-31 06:51:07 UTC 
This bug has been verified on RHEL-7.1-20141024.1 against sat6 zstream and passed.

Testing Steps:
1, register system to Satellite and configure virt-who in ESX mode
...
VIRTWHO_ESX=1
...
# Options for ESX mode
VIRTWHO_ESX_OWNER=Default_Organization
VIRTWHO_ESX_ENV=Library
VIRTWHO_ESX_SERVER=10.66.79.89
VIRTWHO_ESX_USERNAME=administrator
VIRTWHO_ESX_PASSWORD=qwer1234P!

2, Start virt-who service, check ESX hypervisor has been added to Satellite along with rhel system

3, Stop virt-who service, delete above ESX hypervisor in Satellite web, no error happened.

4, Restart virt-who service again, check ESX hypervisor added back.

So mark as VERIFIED.
Comment 10 errata-xmlrpc 2014-11-13 22:29:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2014:1857
Note You need to log in before you can comment on or make changes to this bug.