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 2219590 has been marked as a duplicate of this bug. ***
Comment 8RHEL Program Management
2023-10-10 10:30:07 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 9RHEL Program Management
2023-10-10 10:32:07 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Deploy virt-who config by script failed for Error in libvirt backend Version-Release number of selected component (if applicable): Satellite6.14 snapshot6.0 virt-who-1.30.14-1.el8.noarch katello-4.9.0-1.el8sat.noarch rubygem-foreman_virt_who_configure-0.5.15-1.el8sat.noarch rubygem-hammer_cli_foreman_virt_who_configure-0.0.9-2.el8sat.noarch How reproducible: 100% Steps to Reproduce: 1. Create virt-who config by UI 2. Register guest to satellite 3. Download deploy script 4. Deploy virt-who config by script [root@dell-per740-68-vm-08 ~]# ./deploy.sh == [1/5] == Running unlocking of package versions ================================================================================ Unlock packages: [OK] -------------------------------------------------------------------------------- Running ForemanMaintain::Scenario ================================================================================ Install packages: [OK] -------------------------------------------------------------------------------- Running locking of package versions ================================================================================ Lock packages: [OK] -------------------------------------------------------------------------------- == [2/5] == == [3/5] == == [4/5] == == [5/5] == == Finished == Finished successfully /var/log/rhsm/rhsm.log 2023-07-04 09:11:28,154 [virtwho.main DEBUG] MainProcess(33546):MainThread @executor.py:terminate:225 - virt-who is shutting down 2023-07-04 09:11:28,228 [virtwho.destination_-537109678696197058 DEBUG] MainProcess(33546):Thread-3 @virt.py:run:426 - Thread 'destination_-537109678696197058' terminated 2023-07-04 09:11:29,305 [virtwho.parser WARNING] MainProcess(34028):MainThread @parser.py:read_config_env_variables:237 - The use of environment variables and the use of the sysconfig file to configure virt-who are deprecated. Their use will be ignored in the next major release. 2023-07-04 09:11:29,354 [virtwho.rhsm_log DEBUG] MainProcess(34028):MainThread @config.py:init_config:1594 - [global]: Value for "print_" not set, using default: False 2023-07-04 09:11:29,355 [virtwho.rhsm_log DEBUG] MainProcess(34028):MainThread @config.py:init_config:1594 - [global]: Value for "log_per_config" not set, using default: False 2023-07-04 09:11:29,355 [virtwho.rhsm_log DEBUG] MainProcess(34028):MainThread @config.py:init_config:1594 - [global]: Value for "configs" not set, using default: [] 2023-07-04 09:11:29,355 [virtwho.rhsm_log DEBUG] MainProcess(34028):MainThread @config.py:init_config:1594 - [global]: Value for "reporter_id" not set, using default: dell-per740-68-vm-08.lab.eng.pek2.redhat.com-3b324b81a6fa41449ea1aff98eb2d702 2023-07-04 09:11:29,355 [virtwho.rhsm_log DEBUG] MainProcess(34028):MainThread @config.py:init_config:1594 - [global]: Value for "log_file" not set, using default: rhsm.log 2023-07-04 09:11:29,356 [virtwho.rhsm_log DEBUG] MainProcess(34028):MainThread @config.py:init_config:1594 - [global]: Value for "log_dir" not set, using default: /var/log/rhsm 2023-07-04 09:11:29,356 [virtwho.rhsm_log WARNING] MainProcess(34028):MainThread @config.py:init_config:1594 - [global]: Ignoring unknown configuration option "no_proxy" 2023-07-04 09:11:29,356 [virtwho.rhsm_log INFO] MainProcess(34028):MainThread @executor.py:__init__:54 - Using config named 'virt-who-config-1' 2023-07-04 09:11:29,356 [virtwho.rhsm_log INFO] MainProcess(34028):MainThread @main.py:main:176 - Using configuration "virt-who-config-1" ("libvirt" mode) 2023-07-04 09:11:29,356 [virtwho.rhsm_log INFO] MainProcess(34028):MainThread @main.py:main:178 - Using reporter_id='dell-per740-68-vm-08.lab.eng.pek2.redhat.com-3b324b81a6fa41449ea1aff98eb2d702' 2023-07-04 09:11:29,359 [virtwho.main DEBUG] MainProcess(34028):MainThread @executor.py:run:187 - Starting infinite loop with 7200 seconds interval 2023-07-04 09:11:29,371 [rhsm.https DEBUG] MainProcess(34028):MainThread @https.py:<module>:56 - Using standard libs to provide httplib and ssl 2023-07-04 09:11:29,401 [virtwho.main DEBUG] MainProcess(34028):Thread-2 @virt.py:run:407 - Thread 'virt-who-config-1' started 2023-07-04 09:11:29,402 [virtwho.destination_1388930080526647943 DEBUG] MainProcess(34028):Thread-3 @virt.py:run:407 - Thread 'destination_1388930080526647943' started 2023-07-04 09:11:29,403 [virtwho.main INFO] MainProcess(34028):Thread-2 @libvirtd.py:_connect:280 - Using libvirt url: qemu:///system?no_tty=1 2023-07-04 09:11:29,403 [virtwho.main ERROR] MainProcess(34028):Thread-2 @libvirtd.py:_connect:288 - Error in libvirt backend Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/virtwho/virt/libvirtd/libvirtd.py", line 286, in _connect v = libvirt.openReadOnly(url) File "/usr/lib64/python3.6/site-packages/libvirt.py", line 350, in openReadOnly raise libvirtError('virConnectOpenReadOnly() failed') libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory 2023-07-04 09:11:29,406 [virtwho.main ERROR] MainProcess(34028):Thread-2 @virt.py:run:416 - Thread 'virt-who-config-1' fails with error: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory 2023-07-04 09:11:29,406 [virtwho.main INFO] MainProcess(34028):Thread-2 @virt.py:_send_data:986 - Report for config "virt-who-config-1" gathered, placing in datastore 2023-07-04 09:11:29,407 [virtwho.main INFO] MainProcess(34028):Thread-2 @virt.py:run:440 - Waiting 7200 seconds before performing action again 'virt-who-config-1' 2023-07-04 09:11:30,404 [virtwho.destination_1388930080526647943 DEBUG] MainProcess(34028):Thread-3 @subscriptionmanager.py:_connect:148 - Authenticating with RHSM username virt_who_reporter_1 2023-07-04 09:11:30,404 [virtwho.destination_1388930080526647943 INFO] MainProcess(34028):Thread-3 @subscriptionmanager.py:_connect:159 - X-Correlation-ID: 62557509b90c45388fba6962cf1ab237 2023-07-04 09:11:30,404 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:__init__:211 - Environment variable NO_PROXY= will be used 2023-07-04 09:11:30,406 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:__init__:310 - Connection built: host=dell-per740-68-vm-08.lab.eng.pek2.redhat.com port=443 handler=/rhsm auth=basic username=virt_who_reporter_1 2023-07-04 09:11:30,407 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_request:779 - Making request: GET /rhsm/status/ 2023-07-04 09:11:30,490 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_update_smoothed_response_time:884 - Response time: 0.008281469345092773, Smoothed response time: 0.008281469345092773 2023-07-04 09:11:30,491 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_request:861 - Response: status=200, request="GET /rhsm/status/" 2023-07-04 09:11:30,492 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_request:779 - Making request: GET /rhsm/status 2023-07-04 09:11:30,551 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_update_smoothed_response_time:884 - Response time: 0.007537841796875, Smoothed response time: 0.008207106590270996 2023-07-04 09:11:30,552 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_request:861 - Response: status=200, request="GET /rhsm/status" 2023-07-04 09:11:30,553 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_load_manager_capabilities:1110 - Server has the following capabilities: ['instance_multiplier', 'derived_product', 'vcpu', 'cert_v3', 'hypervisors_heartbeat', 'remove_by_pool_id', 'syspurpose', 'storage_band', 'cores', 'multi_environment', 'hypervisors_async', 'org_level_content_access', 'guest_limit', 'ram', 'batch_bind', 'combined_reporting'] 2023-07-04 09:11:30,554 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_request:779 - Making request: PUT /rhsm/hypervisors/Default_Organization/heartbeat?reporter_id=dell-per740-68-vm-08.lab.eng.pek2.redhat.com-3b324b81a6fa41449ea1aff98eb2d702 2023-07-04 09:11:30,840 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_update_smoothed_response_time:884 - Response time: 0.0069468021392822266, Smoothed response time: 0.008081076145172119 2023-07-04 09:11:30,841 [rhsm.connection DEBUG] MainProcess(34028):Thread-3 @connection.py:_request:861 - Response: status=200, request="PUT /rhsm/hypervisors/Default_Organization/heartbeat?reporter_id=dell-per740-68-vm-08.lab.eng.pek2.redhat.com-3b324b81a6fa41449ea1aff98eb2d702" 2023-07-04 09:11:30,842 [virtwho.destination_1388930080526647943 DEBUG] MainProcess(34028):Thread-3 @virt.py:_send_data:666 - ErrorReport received for source: virt-who-config-1 Actual results: Deploy virt-who config by script failed for Error in libvirt backend Expected results: Deploy virt-who config by script should work well in libvirt Additional info: