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.

Description of problem:
Results from osbuild when using the v2 manifest are unordered objects.  This causes test failures when the result order doesn't match the expected one.

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


How reproducible:
The result ordering isn't deterministic, so it's difficult to know exactly how reproducible this is.  Practically, it's not very frequent.

Steps to Reproduce:
1. Check out or download the source for osbuild composer v28.4
2. Run the tests for the "osbuild1" package: go test ./internal/osbuild1/...
3. Clear the test cache: go clean -testcache
4. Repeat from 2.

Actual results:
After a few runs, the test should fail.

Expected results:
Test should always succeed.

Additional info:
As mentioned above, the ordering of the results is not stable, so several test runs may be required to reproduce.

Fixed upstream (and included in the rebase) in https://github.com/osbuild/osbuild-composer/pull/1330 . We haven't seen this issue for a long time, therefore I'm setting this as preverified.

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 (osbuild 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-2021:4273