Bug 2266344

Summary:	authselect-1.5.0-4.fc41 breaks ostree overlay of postgresql (possibly other things)
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	authselect	Assignee:	Pavel Březina <pbrezina>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	40	CC:	dustymabe, jlebon, jmarrero, pbrezina, travier
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	openqa AcceptedFreezeException
Fixed In Version:	authselect-1.5.0-5.fc40	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-03-01 18:13:50 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:
Bug Depends On:
Bug Blocks:	2187793

Description Adam Williamson 2024-02-27 16:44:40 UTC

In Fedora openQA, we have a test of "overlaying" packages on an atomic install. The test runs from a Fedora Silverblue install. It does `rpm-ostree install htop` then `rpm-ostree install postgresql-server`, then reboots, then checks the packages are present with `rpm -q postgresql-server` and `rpm -q htop`, then does `/usr/bin/postgresql-setup --initdb` (which is required to start the postgresql service, which is what it's really trying to test).

Since authselect-1.5.0-4.fc41, this step is failing. It prints an error:

runuser: user postgres does not exist or the user entry does not contain all the required fields

This seems to be ostree-specific - it does not seem to be affecting a database server test that runs on a non-atomic install of Fedora Server and also runs `postgresql-setup --initdb`.

Comment 1 Jonathan Lebon 2024-02-27 19:59:49 UTC

https://src.fedoraproject.org/rpms/authselect/pull-request/22 might fix this.

Comment 2 Adam Williamson 2024-02-27 20:40:18 UTC

Thanks, testing.

Comment 3 Adam Williamson 2024-02-28 01:56:03 UTC

That fix seems to work in testing. Thanks.

Comment 4 Pavel Březina 2024-02-28 10:59:52 UTC

https://bodhi.fedoraproject.org/updates/FEDORA-2024-bb02da5f27

Comment 5 Fedora Update System 2024-02-28 11:00:40 UTC

FEDORA-2024-76dab69b77 (authselect-1.5.0-5.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-76dab69b77

Comment 6 Fedora Update System 2024-02-29 01:07:36 UTC

FEDORA-2024-76dab69b77 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-76dab69b77`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-76dab69b77

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Adam Williamson 2024-02-29 01:14:45 UTC

Proposing as an FE for F40 Beta, we really shouldn't ship Beta like this.

Comment 8 Adam Williamson 2024-03-01 16:49:44 UTC

+3 in https://pagure.io/fedora-qa/blocker-review/issue/1486 , marking accepted.

Comment 9 Fedora Update System 2024-03-01 18:13:50 UTC

FEDORA-2024-76dab69b77 (authselect-1.5.0-5.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.