Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1511308

Summary: No remind info in the log when set filter_host_parents or exclude_host_parents in xen/hyperv mode
Product: Red Hat Enterprise Linux 7 Reporter: Liushihui <shihliu>
Component: virt-whoAssignee: Jiri Hnidek <jhnidek>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: medium Docs Contact:
Priority: high    
Version: 7.5CC: csnyder, hsun, jhnidek, lmiksik, sgao, yuefliu
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: virt-who-0.21.1-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 16:22:26 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:

Description Liushihui 2017-11-09 06:33:58 UTC
Description of problem:
In xen/hyperv mode, configure filter_host_parents or exclude_host_parents in /etc/virt-who.d/xxx.config, virt-who hasn't shown any remind info in the log.

Version-Release number of selected component (if applicable):
virt-who-0.21.0-1.el7.noarch
subscription-manager-1.20.5-1.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Register system to satellite6.2.12
2. Configure virt-who run at xen/hyperv mode with filter_host_parents or exclude_host_parents in /etc/virt-who.d/xxx.config
[root@xen-RHEL-7 virt-who.d]# cat xen.conf 
[xen]
type=xen
server=10.73.131.203
username=root
password=Welcome1
owner=Default_Organization
env=Library
filter_host_parents=host_parents
3. Restart virt-who and check virt-who's log in /var/log/rhsm/rhsm.log

Actual results:
Although it send h/g mapping info normally, it hasn't show remind info "filter_host_parents is not supported in xen mode, ignoring it"

Expected results:
Since filter_host_parents/exclude_host_parents is not supported on hyperv/xen mode, it should show remind info "filter_host_parents/exclude_host_parents is not supported in xen/hyperv mode, ignoring it" in rhsm.log

Additional info:
It hasn't this problem on virt-who-0.20.4-1.el7sat.noarch

Comment 3 Liushihui 2017-12-01 06:19:10 UTC
Verify it on virt-who-0.21.1-1.el7.noarch, when filter_host_parents exist on /etc/virt-who.d/xxx.conf, it's correct to show remind info "Ignoring unknown configuration option "filter_host_parents". Therefore, verify it.

Comment 6 errata-xmlrpc 2018-04-10 16:22:26 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/RHEA-2018:0895