Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1858814

Summary: pgbouncer systemd unit file change breaks startup
Product: [Fedora] Fedora EPEL Reporter: Thomas J. Baker <tjb>
Component: pgbouncerAssignee: Fabian Affolter <mail>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: epel7CC: devrim, mail, negativo17, praiskup, ricardo.arguello
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: pgbouncer-1.14.0-2.fc32 pgbouncer-1.14.0-2.fc31 pgbouncer-1.14.0-2.el7 pgbouncer-1.14.0-2.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-30 18:55:57 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 Thomas J. Baker 2020-07-20 13:21:29 UTC
Description of problem:

The addition of the Type=notify statement to the pgbouncer systemd unit file causes systemd to timeout and kill pgbouncer after the configured 5 minutes of waiting for something (perhaps some type of notification?).

Version-Release number of selected component (if applicable):
pgbouncer-1.13.0-2.el7.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Upgrade pgbouncer to pgbouncer-1.13.0-2.el7.x86_64
2.
3.

Actual results:
Systemd starts pgbouncer but waits from a notification that doesn't ever come? and then kills pgbouncer.

Expected results:
systemd starts pgbouncer and returns almost immediately.

Additional info:
Commenting out the Type=notify returns things to normal operation.

Comment 1 Simone Caronni 2020-07-22 09:04:19 UTC
The addition of the notify line was an unfortunate last minute change.
Now Fedora and EPEL 8 packages are compiled with systemd support, which give notify and socket access. For EPEL 7 a different systemd unit is in place and no notify/socket access is in place as this requires newer systemd.

Comment 2 Fedora Update System 2020-07-22 09:05:30 UTC
FEDORA-2020-ee3cba948a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ee3cba948a

Comment 3 Fedora Update System 2020-07-22 09:05:31 UTC
FEDORA-2020-8d91442bf5 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8d91442bf5

Comment 4 Fedora Update System 2020-07-22 09:05:32 UTC
FEDORA-EPEL-2020-f76ab6075a has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f76ab6075a

Comment 5 Fedora Update System 2020-07-23 01:39:40 UTC
FEDORA-EPEL-2020-f76ab6075a has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f76ab6075a

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

Comment 6 Fedora Update System 2020-07-23 01:43:32 UTC
FEDORA-2020-ee3cba948a has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ee3cba948a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ee3cba948a

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

Comment 7 Fedora Update System 2020-07-23 01:50:20 UTC
FEDORA-2020-8d91442bf5 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8d91442bf5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8d91442bf5

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

Comment 8 Fedora Update System 2020-07-23 01:51:43 UTC
FEDORA-EPEL-2020-06912b5f25 has been pushed to the Fedora EPEL 6 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-06912b5f25

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

Comment 9 Fedora Update System 2020-07-30 18:55:57 UTC
FEDORA-2020-ee3cba948a has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2020-07-30 19:08:32 UTC
FEDORA-2020-8d91442bf5 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2020-08-06 04:26:48 UTC
FEDORA-EPEL-2020-f76ab6075a has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2020-08-06 04:29:42 UTC
FEDORA-EPEL-2020-06912b5f25 has been pushed to the Fedora EPEL 6 stable repository.
If problem still persists, please make note of it in this bug report.