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.

Bug 2193429

Summary: docbook-utils install fails against missing link in ostree rhel9
Product: Red Hat Enterprise Linux 9 Reporter: bgrech
Component: openjadeAssignee: Ondřej Sloup <osloup>
Status: CLOSED MIGRATED QA Contact: Vaclav Danek <vdanek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.3CC: belmouss, databases-maint, fjanus, hhorak, leiwang, osloup, ovasik, rhel-cs-apps-subsystem-qe, vdanek
Target Milestone: rcKeywords: MigratedToJIRA, TestBlocker, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openjade-1.3.2-69.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-04 23:42:20 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 bgrech 2023-05-05 16:14:21 UTC
Description of problem:
Installation of docbook-utils-0.6.14-54.el9 in an ostree environment (rhel9.3) looking for a missing or broken symbolic link. 

journalctl -t 'rpm-ostree(docbook-dtds.post)' shows
````localhost.localdomain rpm-ostree(docbook-dtds.post)[4353]: /usr/bin/chmod: cannot operate on dangling symlink '/etc/sgml/openjade.soc'```



How reproducible:
core-os, rawhide, or rhvios which utlze the rpm-ostree package manager can be used, 

this issue occurs 100% 


Steps to Reproduce:
# rpm-ostree install --apply-live --idempotent --allow-inactive docbook-utils



Actual results:
...
Resolving dependencies... done
Applying 4 overrides and 513 overlays
Processing packages... done
Running pre scripts... done
Running post scripts... done
error: Running %post for docbook-dtds: bwrap(/bin/sh): Child process killed by signal 1; run `journalctl -t 'rpm-ostree(docbook-dtds.post)'` for more information

Expected results:
error free installation 

Additional info:

# ll /sysroot/ostree/repo/extensions/rpmostree/private/commit/etc/sgml/openjade.soc
lrwxrwxrwx. 2 root root 25 May  5 16:12 /sysroot/ostree/repo/extensions/rpmostree/private/commit/etc/sgml/openjade.soc -> openjade-1.3.2-68.el9.soc

but its a broken link

---------
This is a blocker for enabling kernel storage/block/blktests RHIVOS Because the package is a requirement

Comment 2 Ondřej Sloup 2023-05-12 04:06:39 UTC
I reproduced the issue in the newest version of Fedora SilverBlue 38.

Comment 17 Ondřej Sloup 2023-07-10 10:45:07 UTC
*** Bug 2133025 has been marked as a duplicate of this bug. ***

Comment 19 Ondřej Sloup 2023-08-22 09:43:49 UTC
Due to the impending release deadline, this bug fix is scheduled for inclusion in version 9.4 (or in z-stream). It is advisable not to commence this fix within the current time frame.
If someone needs to be fixed in 9.3, please tag me, and I'll look into it.

Comment 21 Ondřej Sloup 2023-10-04 23:38: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.

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 the Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to request 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" = 2193429

If 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.

Comment 22 RHEL Program Management 2023-10-04 23:42:04 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 23 RHEL Program Management 2023-10-04 23:42:20 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.

Comment 24 Red Hat Bugzilla 2024-02-02 04:25:08 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days