Bug 1399387

Summary:	systemd presets request - drbdlinksclean.service
Product:	[Fedora] Fedora	Reporter:	Robert Scheck <redhat-bugzilla>
Component:	fedora-release	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	26	CC:	dennis, jdisnard, kevin, mboddu, pbrobinson, sgallagh, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-02 00:13:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Robert Scheck 2016-11-29 00:16:07 UTC

* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)?
No.

* Does the service listen on a network socket for connections originating on a separate physical or virtual machine?
No.

* Is the service non-persistent (i.e. run once at startup and exit)?
Oneshot.

* What is the exact name (or names) of the systemd unit files to be enabled?
drbdlinksclean.service

* Is this request for all Fedora deliverables or only for some Editions (list them)?
All Fedora branches and EPEL 7.

Comment 1 Stephen Gallagher 2016-11-29 01:21:10 UTC

(In reply to Robert Scheck from comment #0)
> * Is this request for all Fedora deliverables or only for some Editions
> (list them)?
> All Fedora branches and EPEL 7.

This question is whether the service should be started by default everywhere or if it's only useful to Fedora Server, Fedora Workstation or Fedora Atomic. It looks to me like it's useful on all of them (or at least, any of them that install the drbdlinks package), so I proceeded under that assumption.

This process does not manage presets for EPEL 7, only Fedora. If you want it included there, you need to file a bug against the epel-release package. (I think; I'm not sure if EPEL allows presets that aren't provided by RHEL).

Pull requests sent to the fedora-release package:
https://pagure.io/fedora-release/pull-request/68 (F26/Rawhide)
https://pagure.io/fedora-release/pull-request/69 (F25)
https://pagure.io/fedora-release/pull-request/70 (F24)

Comment 2 Robert Scheck 2016-11-29 01:52:08 UTC

(In reply to Stephen Gallagher from comment #1)
> This question is whether the service should be started by default everywhere
> or if it's only useful to Fedora Server, Fedora Workstation or Fedora
> Atomic. It looks to me like it's useful on all of them (or at least, any of
> them that install the drbdlinks package), so I proceeded under that
> assumption.

I'm sorry for being imprecise here, your assumption is correct.

> This process does not manage presets for EPEL 7, only Fedora. If you want it
> included there, you need to file a bug against the epel-release package. (I
> think; I'm not sure if EPEL allows presets that aren't provided by RHEL).

In the past a preset from another package that I'm maintaining was silently
merged from Fedora to EPEL, but will file a separate bug - thanks!

Comment 3 Fedora End Of Life 2017-02-28 10:40:54 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 4 Kevin Fenzi 2018-02-02 00:13:44 UTC

Long ago fixed. :)