Project

General

Profile

Actions

Bug #27553

closed

filter_hosts in Virt-who-Config-file is different when configuring both filter hosts and filter host parents

Added by Marek Hulán over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Difficulty:
Triaged:
No
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1735670

Description of problem:
For ESX Hypervisor,filter_hosts in Virt-who-Config-file(/etc/virt-who.d/virt-who-config.conf) is different from what we configured when configuring both filter hosts and filter host parents

Version-Release number of selected component (if applicable):
satellite-6.6.0-5.beta.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_virt_who_configure-0.0.3-4.el7sat.noarch
tfm-rubygem-foreman_virt_who_configure-0.4.1-1.el7sat.noarch

How reproducible:
100%

Actual results:

[root@ent-02-vm-03 virt-who.d]# cat virt-who-config.conf |grep filter_hosts
filter_hosts=host-91,

the filter_hosts in virt-who-config.conf has an extra comma, it is different from what we configured in UI.

Expected results:
The filter_hosts in virt-who-config.conf should be the same as what we configured.

Actions #1

Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_virt_who_configure/pull/112 added
Actions #2

Updated by Marek Hulán over 4 years ago

  • Subject changed from filter_hosts in Virt-who-Config-file is different when configuring both filter hosts and filter host parents to filter_hosts in Virt-who-Config-file is different when configuring both filter hosts and filter host parents
  • Fixed in Releases foreman_virt_who_configure-0.4.4 added
Actions #3

Updated by Marek Hulán over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF