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.
+++ This bug was initially created as a clone of Bug #2176555 +++
Description of problem:
image builder fails to make edge images that include npm
Version-Release number of selected component (if applicable):
osbuild-65-1.el8.noarch
osbuild-composer-62-3.el8_7.x86_64
osbuild-65-1.el9.noarch
osbuild-composer-62.1-3.el9_1.x86_64
How reproducible:
Everytime
Steps to Reproduce:
1.Create blueprint with npm or nodejs (which pulls in npm)
name = "RhelEdge"
description = ""
version = "0.0.1"
modules = []
groups = []
distro = ""
[[packages]]
name = "npm"
version = "*"
2. composer-cli compose start RhelEdge edge-commit
3.
Actual results:
Stage org.osbuild.ostree.preptree
Output:
/usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve specifier: uninitialized /etc detected, skipping
All rules containing unresolvable specifiers will be skipped.
Failed to open file "/sys/fs/selinux/checkreqprot": Read-only file system
ostree: machineid-compat: True
Traceback (most recent call last):
File "/run/osbuild/bin/org.osbuild.ostree.preptree", line 172, in <module>
r = main(args["tree"], args["options"])
File "/run/osbuild/bin/org.osbuild.ostree.preptree", line 122, in main
os.rename(f"{tree}/etc", f"{tree}/usr/etc")
FileExistsError: [Errno 17] File exists: '/run/osbuild/tree/etc' -> '/run/osbuild/tree/usr/etc'
Additional info:
This is also being discussed with HMS
https://issues.redhat.com/browse/HMS-1406https://github.com/coreos/rpm-ostree/issues/2003#issuecomment-1453354982
--- Additional comment from on 2023-03-13 15:42:09 UTC ---
opening [2177776 – npm's /usr/etc/ softlink to /etc/ is preventing osbuild from creating Edge images.](https://bugzilla.redhat.com/show_bug.cgi?id=2177776) to request if NPM can resolve this since npm is _currently_ the only package with content in /usr/etc
--- Additional comment from on 2023-03-15 12:48:11 UTC ---
RHEL 8 npm is a dead stream and we can't switch streams at this time so we need to fix this for RHEL 8 or we need to document that it's not possible to build a RHEL 8 Edge image with nodejs
Comment 1RHEL Program Management
2023-09-18 13:47:58 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 2RHEL Program Management
2023-09-18 13:49:48 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.