Project

General

Profile

Actions

Bug #27901

closed

Failed to deploy Kubevirt VIrt-who-Configuration

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

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

Description

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

Description of problem:
Failed to deploy Kubevirt Virt-who-Configuration, raised an error: virt-who can't be started: no valid configuration found.

Version-Release number of selected component (if applicable):
snap21.0
satellite-6.6.0-7.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_virt_who_configure-0.0.4-1.el7sat.noarch
tfm-rubygem-foreman_virt_who_configure-0.4.4-1.el7sat.noarch
virt-who-0.24.7-1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a Kubevirt Virt-who-configuration via UI
2. Use hammer CLI to deploy the config
3. See the output
4. Check the log
5. Check the config file(/etc/virt-who.d/virt-who-config.conf)

Actual results:
3. Output:
[5/5] Enabling and restarting the virt-who service
Note: Forwarding request to 'systemctl enable virt-who.service'.
Redirecting to /bin/systemctl restart virt-who.service
Job for virt-who.service failed because the control process exited with error code. See "systemctl status virt-who.service" and "journalctl -xe" for details.

4. Can see error info from log:
2019-09-18 03:27:53,088 [virtwho.rhsm_log ERROR] MainProcess(11390):MainThread @config.py:init_config:1499 - [virt-who-config-3]: Option server needs to be set in config: 'virt-who-config-3'
2019-09-18 03:27:53,089 [virtwho.rhsm_log WARNING] MainProcess(11390):MainThread @config.py:init_config:1499 - [virt-who-config-3]: Ignoring unknown configuration option "env"
2019-09-18 03:27:53,089 [virtwho.rhsm_log WARNING] MainProcess(11390):MainThread @config.py:init_config:1499 - Dropping invalid configuration "virt-who-config-3"
2019-09-18 03:27:53,089 [virtwho.rhsm_log WARNING] MainProcess(11390):MainThread @config.py:init_config:1499 - No valid configurations found
2019-09-18 03:27:53,090 [virtwho.rhsm_log ERROR] MainProcess(11390):MainThread @main.py:main:143 - virt-who can't be started: no valid configuration found

5. The content of the config file:
[root@ent-02-vm-04 virt-who.d]# cat virt-who-config-3.conf
  1. This configuration file is managed via the virt-who configure plugin
  2. manual edits will be deleted.
    [virt-who-config-3]
    type=kubevirt
    hypervisor_id=hostname
    owner=Default_Organization
    env=Library
    server=
    username=''
    encrypted_password=59a7ed4786d35d6d913c6bdc6ddae8d98309e075ea0e647d8b125e6e89616009
    rhsm_hostname=ent-02-vm-04.lab.eng.nay.redhat.com
    rhsm_username=virt_who_reporter_3
    rhsm_encrypted_password=5bf06ab7a0f0b3d6da0edef418af4ca0daad5d968aa558a2dbbf77c449691259
    rhsm_prefix=/rhsm
    kubeconfig=/root/kube.conf

Expected results:
3. The config should be deployed successfully.

5. The username, server, encrypted_password should not be shown on the config file as there is no need for Kubevirt to use these params. After I delete them and restart the virt-who service, the config works fine.

Additional info:
Related Bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1714130
No need for kubevirt to config Hypervisor Server

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/113 added
Actions #2

Updated by Marek Hulán over 4 years ago

  • Subject changed from Failed to deploy Kubevirt VIrt-who-Configuration to Failed to deploy Kubevirt VIrt-who-Configuration
  • Fixed in Releases foreman_virt_who_configure-0.4.5 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