Bug 2236363

Summary:	ostree error log "ostree-prepare-root[771]: composefs: optional support failed: No such file or directory"
Product:	Red Hat Enterprise Linux 9	Reporter:	Xiaofeng Wang <xiaofwan>
Component:	ostree	Assignee:	RHCOS SST <rhcos-sst>
Status:	CLOSED MIGRATED	QA Contact:	RHCOS SST QE <rhcos-sst-qe>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	9.3	CC:	rhcos-sst, shdunne, walters
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: needinfo? (rhcos-sst)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-13 10:47:01 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 Xiaofeng Wang 2023-08-31 04:39:50 UTC

Description of problem:
I'm running into a new error log "ostree-prepare-root[771]: composefs: optional support failed: No such file or directory" in RHEL for Edge image since ostree update to ostree-2023.6-1.el9.x86_64. But pacakge installation, ostree upgrade and rollback are still working.

This error does not exist on ostree-2023.5-1.el9.x86_64

Version-Release number of selected component (if applicable):
ostree-2023.6-1.el9.x86_64

How reproducible:

Steps to Reproduce:
1. Deploy a RHEL 9.3 VM from PSI openstack
2. git clone https://github.com/virt-s1/rhel-edge.git
3. cd rhel-edge
4. DOWNLOAD_NODE=xxx ./ostree.sh

Actual results:
Test failed with new error log

Expected results:
Should not have ostree error log

Additional info:

Comment 2 Colin Walters 2023-08-31 17:36:55 UTC

Basically RHEL4Edge QE has a CI check that greps logs for the string "failed".  This removes the term "failed" for something that isn't a failure.  Fortunately before this was even reported I had already prepared and tested a PR for this for exactly the same reason.

This change is very low risk (but also, relatively low benefit; we could just change the test to skip this too, but customers may also be misled by it).

Comment 5 RHEL Program Management 2023-09-13 10:46:45 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 6 RHEL Program Management 2023-09-13 10:47:01 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.