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 1858836

Summary:	Systemd support missing
Product:	[Fedora] Fedora EPEL	Reporter:	brandonjsnider
Component:	pgbouncer	Assignee:	Fabian Affolter <mail>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	brandonjsnider, devrim, mail, negativo17, praiskup, ricardo.arguello
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
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:59 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 brandonjsnider 2020-07-20 14:09:16 UTC

Description of problem:
This refers to the 1.13 package in EPEL.
The systemd unit file will not start the service because the systemd support flag was not used at compile time. The notify type was used, which is a puzzling choice given the lack of systemd support. From the pgbouncer install notes:
"To enable systemd integration, use the configure option --with-systemd. This allows using Type=notify service units as well as socket activation."

This unit file has no chance of working. Also, I tried every other type and none of them worked, which suggests there's more wrong with the systemd side of the packaging than just the service type.

I think the packaging scripts used by the postgresql folks should be used for the EPEL package, since there's some testing already behind those packages, and it should be placed in the testing area for awhile before being moved to stable EPEL.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
Try to start the service with systemctl

Actual results:


Expected results:


Additional info:

Comment 1 Simone Caronni 2020-07-22 09:02:23 UTC

If the program is not forking (like pgbouncer) you can just remove the type line and it will just work. The notify line was an unfortunate last minute addition.

I've updated the package.

Comment 2 Fedora Update System 2020-07-22 09:05:33 UTC

FEDORA-EPEL-2020-06912b5f25 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-06912b5f25

Comment 3 Fedora Update System 2020-07-22 09:05:36 UTC

FEDORA-2020-ee3cba948a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ee3cba948a

Comment 4 Fedora Update System 2020-07-22 09:05:39 UTC

FEDORA-2020-8d91442bf5 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8d91442bf5

Comment 5 Fedora Update System 2020-07-22 09:05:42 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 6 Fedora Update System 2020-07-23 01:39:41 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 7 Fedora Update System 2020-07-23 01:43:33 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 8 Fedora Update System 2020-07-23 01:50:21 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 9 Fedora Update System 2020-07-23 01:51:44 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 10 Fedora Update System 2020-07-30 18:55:59 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 11 Fedora Update System 2020-07-30 19:08:34 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 12 Fedora Update System 2020-08-06 04:26:50 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 13 Fedora Update System 2020-08-06 04:29:43 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.