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 2084613 - qga-win: race condition in build
Summary: qga-win: race condition in build
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: mingw-qemu-ga-win
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Kostiantyn Kostiuk
QA Contact: dehanmeng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-12 14:09 UTC by Kostiantyn Kostiuk
Modified: 2022-11-15 11:20 UTC (History)
3 users (show)

Fixed In Version: mingw-qemu-ga-win-104.0.2-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:22:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-121882 0 None None None 2022-05-12 14:38:15 UTC
Red Hat Product Errata RHBA-2022:8107 0 None None None 2022-11-15 10:22:04 UTC

Description Kostiantyn Kostiuk 2022-05-12 14:09:28 UTC
Description of problem:


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


How reproducible:
this is a race condition bug, so it will be very difficult to reproduce.


Steps to Reproduce:
1. ./configure \
   --disable-docs \
   --disable-zlib-test \
   --target-list=x86_64-softmmu \
   --cross-prefix=i686-w64-mingw32- \
   --enable-guest-agent-msi \
   --enable-qga-vss 

2. make -j40 qemu-ga


Actual results:

built failed due to config-poison.h missing, but this header was generated after GCC fail.

[176/701] Compiling C++ object qga/vss-win32/qga-vss.dll.p/provider.cpp.obj
FAILED: qga/vss-win32/qga-vss.dll.p/provider.cpp.obj
fatal error: config-poison.h: No such file or directory


[180/701] Generating config-poison.h with a custom command (wrapped by meson to capture output)



Expected results:

The build should finish without any errors.


Additional info:

Solution:
you need to add "gen_h" to the sources of qga-vss.dll.

Comment 3 dehanmeng 2022-05-19 13:13:01 UTC
After function test with latest qga version mingw-qemu-ga-win-104.0.2-1.el9, although, there is only one minor problem with low priority https://bugzilla.redhat.com/show_bug.cgi?id=2087678, no other further urgent/high bug. so move this bug to VERIFIED.

Comment 6 errata-xmlrpc 2022-11-15 10:22:00 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 (mingw-qemu-ga-win 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:8107


Note You need to log in before you can comment on or make changes to this bug.