Bug 1709764 - virt-who server and hosts managed by the server not in correct location in satellite
Summary: virt-who server and hosts managed by the server not in correct location in sa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.4.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Kunxin Huang
satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-14 09:47 UTC by pk
Modified: 2021-01-19 21:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-19 21:33:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description pk 2019-05-14 09:47:51 UTC
Description of problem:
1. Deployed capsule server on location TW
2. Created virt-who server and generated virt-who config on location TW
3. Deployed virt-who on capsule server mentioned in step1
4. /var/log/messages in virt-who server showing communication to satellite server.
5. virt-who status in satellite showing "Not Reporting"
6. api to virt-who server is pointing to the wrong location.

Guests managed by virt-who servers listed in all-host but in the incorrect location, not listed in location TW

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

How reproducible:
Always

Steps to Reproduce:
1.Restart virt-who, no change on Satellite UI
2.hammer host list --location tw not showing any hosts
3.hammer host list --location sg showing hosts that should be in tw

Actual results:
virt-who status should be showing OK
hosts should be in correct location

Expected results:
virt-who server and its guests should be in the correct location.

Additional info:
the satellite server is recently upgraded from v6.3 to v6.4. The capsule server is recently deployed with virt-who manager.

Comment 3 Mike McCune 2020-12-09 22:17:08 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in approximately a month. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 4 Mike McCune 2021-01-19 21:25:25 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact your Red Hat Account Team. Thank you.


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