Bug 1976122

Summary: Unexpected behavior during crc setup in case 'virsh' requires interactive authentication.
Product: OpenShift Container Platform Reporter: Amos Mastbaum <amastbau>
Component: crcAssignee: Praveen Kumar <prkumar>
Status: CLOSED DEFERRED QA Contact: Tomáš Sedmík <tsedmik>
Severity: unspecified Docs Contact: Kevin Owen <kowen>
Priority: unspecified    
Version: 4.7CC: cfergeau, gbraad, kowen, tsedmik, veillard
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-09 01:03:59 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 Amos Mastbaum 2021-06-25 09:11:59 UTC
Description of problem:


crc setup flow  does not handle 
 'virsh --connect qemu:///system...' interactive  authentication.

see: https://access.redhat.com/discussions/672423



If:

$ virsh --connect qemu:///system net-undefine crc
Please enter your authentication name:



Then:
$ ./crc setup --log-level=debug
DEBU CodeReady Containers version: 1.28.0+08de64bd 
DEBU OpenShift version: 4.7.13 (embedded in executable) 
DEBU Running 'crc setup'                          
DEBU Checking if systemd-resolved.service is running 
DEBU Running 'systemctl status systemd-resolved.service' 
DEBU Command failed: exit status 3                
DEBU stdout: * systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

..
..
..  
INFO Checking if NetworkManager is installed      
DEBU Checking if 'nmcli' is available             
DEBU 'nmcli' was found in /usr/bin/nmcli          
INFO Checking if NetworkManager service is running 
DEBU Checking if NetworkManager.service is running 
DEBU Running 'systemctl status NetworkManager.service' 
DEBU NetworkManager.service is already running    
INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists 
DEBU Checking NetworkManager configuration        
DEBU NetworkManager configuration is good         
INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists 
DEBU Checking dnsmasq configuration               
DEBU dnsmasq configuration is good                
INFO Checking if libvirt 'crc' network is available 
DEBU Checking if libvirt 'crc' network exists     
DEBU Running 'virsh --connect qemu:///system net-info crc'


...
...
...

DEBU Command failed: exit status 1                
DEBU stdout: Please enter your authentication name: Please enter your password:  
DEBU stderr: error: failed to connect to the hypervisor
error: authentication failed: Failed to start SASL negotiation: -1 (SASL(-1): generic failure: All-whitespace username.) 

DEBU exit status 1 : error: failed to connect to the hypervisor
error: authentication failed: authentication failed 

Failed to create libvirt 'crc' network: exit status 1 - error: failed to connect to the hypervisor
error: authentication failed: authentication failed



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


How reproducible:
100%


Steps to Reproduce:
1.ensure virsh --connect qemu:///system prompts for authentication.
2.run crc setup (using virtlib).
3.

Actual results:



Expected results:


Additional info:

$ crc version
CodeReady Containers version: 1.28.0+08de64bd

Comment 1 Christophe Fergeau 2021-06-28 18:39:15 UTC
You did not really detail how to achieve step 1., but the access.redhat.com discussion you link to refers to ovirt.
See this upstream bug for ovirt authentication issues https://github.com/code-ready/crc/issues/1847
The libvirt-go work has been merged, so we should be able to move forward in crc/machine-driver-libvirt to try and fix this.

Comment 2 Shiftzilla 2023-03-09 01:03:59 UTC
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-8905