Bug 2400428
| Summary: | user/group openbao does not exist - using root | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Jiri Popelka <jpopelka> |
| Component: | openbao | Assignee: | Dave Dykstra <dwd> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel9 | CC: | dwd, go-sig, maxwell |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openbao-2.4.1-4.el9 openbao-2.4.1-3.el10_0 openbao-2.4.1-4.el8 openbao-2.4.1-3.el10_2 openbao-2.4.1-3.fc42 openbao-2.4.1-3.el10_1 openbao-2.4.1-3.fc41 openbao-2.4.1-3.fc43 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-10-09 00:57:22 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
Jiri Popelka
2025-09-30 11:30:14 UTC
Thank you for this report. I see those messages on both el8 and el9, but it's OK on el10. Maxwell, isn't the %sysusers_create_compat macro supposed to take care of that? Hi,
The macro seems to need a full path to the source. I tried doing
%sysusers_create_compat %{_builddir}/%{name}-fedora-%{package_version}/%{name}.conf
which didn't seem to work (I guess the builddir is cleaned up at the time the %pre scriptlet is evaluated), so I'd instead recommend that you commit the sysusers file to distgit, add it as an explicit source and call
%sysusers_create_compat %{SOURCEXXXX}
where XXXX is the Source number.
> (I guess the builddir is cleaned up at the time the %pre scriptlet is evaluated) Actually, I think it's the other way around. I believe the entire specfile is parsed before %prep (or any other section) runs, so the sources will only be unpacked after the %pre scriptlet is already evaluated. And https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/#_creation_of_users_and_groups_with_scriptlets explicitly says: > The sysusers file must be a separate Source file. So in any case, you need to add sysusers as a separate source FEDORA-EPEL-2025-b71e08d16b (openbao-2.4.1-4.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b71e08d16b FEDORA-EPEL-2025-5c945f7e07 (openbao-2.4.1-4.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5c945f7e07 Thank you, Maxwell. Jiri, see the above links for el8 & el9 builds of openbao-2.4.1-4. If you give them karma, they will be promoted to stable sooner. FEDORA-EPEL-2025-b71e08d16b (openbao-2.4.1-4.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2025-5c945f7e07 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5c945f7e07 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. I'm reopening this because it turns out the same fix is needed on EL10 and Fedora when the package is included as a dependency of another package. It gets the same symptoms warning: user openbao does not exist - using root warning: group openbao does not exist - using root warning: user openbao does not exist - using root warning: group openbao does not exist - using root warning: user openbao does not exist - using root FEDORA-EPEL-2025-f994ea4d43 (openbao-2.4.1-3.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f994ea4d43 FEDORA-2025-4074af998e (openbao-2.4.1-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-4074af998e FEDORA-2025-c822dd7106 (openbao-2.4.1-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c822dd7106 FEDORA-2025-fee19000f0 (openbao-2.4.1-3.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-fee19000f0 FEDORA-EPEL-2025-8894e2b490 (openbao-2.4.1-3.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2025-f994ea4d43 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f994ea4d43 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-4074af998e has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4074af998e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4074af998e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2025-08705355a6 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-08705355a6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-c822dd7106 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c822dd7106` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c822dd7106 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-fee19000f0 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-fee19000f0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-fee19000f0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2025-5c945f7e07 (openbao-2.4.1-4.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2025-08705355a6 (openbao-2.4.1-3.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-c822dd7106 (openbao-2.4.1-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2025-f994ea4d43 (openbao-2.4.1-3.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-fee19000f0 (openbao-2.4.1-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-4074af998e (openbao-2.4.1-3.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. |