Bug 2053272

Summary: work around g_file_query_info() succeeding on such files for which the underlying lstat() fails with EACCES
Product: Red Hat Enterprise Linux 8 Reporter: Victor Toso <victortoso>
Component: libosinfoAssignee: Victor Toso <victortoso>
Status: CLOSED ERRATA QA Contact: Xiaodai Wang <xiaodwan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.6CC: cfergeau, desktop-qa-list, juzhou, kkiwi, lersek, mxie, rjones, tyan, tzheng, victortoso, vwu, xiaodwan, ymankad
Target Milestone: rcKeywords: Automation, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libosinfo-1.9.0-3.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2051559 Environment:
Last Closed: 2022-05-10 14:17:40 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:
Bug Depends On: 2051559    
Bug Blocks:    

Comment 8 Xiaodai Wang 2022-03-03 02:48:33 UTC
Verified this bug with libosinfo-1.9.0-3.el8.x86_64 and virt-v2v-1.42.0-18.module+el8.6.0+13447+4b5d0856.x86_64,
The v2v command can run successfully and a WARNING is reported.


[stdlog] 2022-03-02 21:32:49,347 process          L0658 INFO | Running 'su - v2v_auto -c 'HOME=/root LIBGUESTFS_BACKEND=direct /usr/bin/virt-v2v -i libvirt -ic vpx://root.x.x/data/x.x.x.x/?no_verify=1 -o json -of raw -os /home/v2v_auto --mac 00:50:56:ac:59:8d:network:default esx6.7-win2019-x86_64 -it vddk -io vddk-libdir=/home/v2v_auto/vddk_libdir/latest -io vddk-thumbprint=xxx -on esx6.7-win2019-x86_64vJRR -ip /tmp/v2v_vpx_passwd''
[stdlog] 2022-03-02 21:32:49,466 process          L0470 DEBUG| [stdout] [   0.0] Opening the source -i libvirt -ic vpx://root.x.x/data/x.x.x.x/?no_verify=1 esx6.7-win2019-x86_64 -it vddk  -io vddk-libdir=/home/v2v_auto/vddk_libdir/latest -io vddk-thumbprint=xxx
[stdlog] 2022-03-02 21:32:51,238 process          L0470 DEBUG| [stdout] [   1.8] Creating an overlay to protect the source from being modified
[stdlog] 2022-03-02 21:32:51,801 process          L0470 DEBUG| [stdout] [   2.3] Opening the overlay
[stdlog] 2022-03-02 21:33:15,266 process          L0470 DEBUG| [stdout] [  25.8] Inspecting the overlay
[stdlog] 2022-03-02 21:33:22,548 process          L0470 DEBUG| [stdout] [  33.1] Checking for sufficient free disk space in the guest
[stdlog] 2022-03-02 21:33:22,548 process          L0470 DEBUG| [stdout] [  33.1] Estimating space required on target for each disk
[stdlog] 2022-03-02 21:33:22,548 process          L0470 DEBUG| [stdout] [  33.1] Converting Windows Server 2019 Standard to run on KVM
[stdlog] 2022-03-02 21:33:26,221 process          L0470 DEBUG| [stderr]
[stdlog] 2022-03-02 21:33:26,221 process          L0470 DEBUG| [stderr] ** (process:7970): WARNING **: 21:33:26.221: Can't read path /root/.config/osinfo
[stdlog] 2022-03-02 21:33:34,463 process          L0470 DEBUG| [stdout] virt-v2v: This guest has virtio drivers installed.
[stdlog] 2022-03-02 21:33:37,512 process          L0470 DEBUG| [stdout] [  48.0] Mapping filesystem data to avoid copying unused and blank areas
[stdlog] 2022-03-02 21:33:38,076 process          L0470 DEBUG| [stdout] [  48.6] Closing the overlay
[stdlog] 2022-03-02 21:33:38,117 process          L0470 DEBUG| [stdout] [  48.7] Assigning disks to buses
[stdlog] 2022-03-02 21:33:38,117 process          L0470 DEBUG| [stdout] [  48.7] Checking if the guest needs BIOS or UEFI to boot
[stdlog] 2022-03-02 21:33:38,117 process          L0470 DEBUG| [stdout] [  48.7] Initializing the target -o json -os /home/v2v_auto
[stdlog] 2022-03-02 21:33:38,118 process          L0470 DEBUG| [stdout] [  48.7] Copying disk 1/1 to /home/v2v_auto/esx6.7-win2019-x86_64vJRR-sda (raw)
[stdlog] 2022-03-02 21:33:38,133 process          L0470 DEBUG| [stdout]     (0.00/100%)

So move the bug to VERIFIED.

Comment 10 errata-xmlrpc 2022-05-10 14:17:40 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 (libosinfo bug fix and enhancement update), 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/RHBA-2022:1914