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

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 1144443

Summary:	Can't delete virt-who created Hypervisor content hosts
Product:	Red Hat Satellite	Reporter:	Stephen Benjamin <stbenjam>
Component:	Content Management	Assignee:	Stephen Benjamin <stbenjam>
Status:	CLOSED ERRATA	QA Contact:	Li Bin Liu <liliu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	achan, bbuckingham, cwelton, greartes, jmontleo, liliu, sgao, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/7542
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-13 22:29:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1142315
Bug Blocks:	1132363

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