Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1412244

Summary: pcs does not currently work with systemd's instantiated services
Product: Red Hat Enterprise Linux 7 Reporter: Jaroslav Reznik <jreznik>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.3CC: cfeist, cluster-maint, gfidente, idevat, michele, mjuricek, mlisik, omular, tojeline
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: pcs-0.9.152-10.el7_3.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1408476 Environment:
Last Closed: 2017-01-30 15:56:39 UTC Type: ---
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: 1408476    
Bug Blocks:    
Attachments:
Description Flags
proposed fix none

Description Jaroslav Reznik 2017-01-11 15:35:31 UTC
This bug has been copied from bug #1408476 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 3 Ivan Devat 2017-01-16 14:37:22 UTC
Created attachment 1241253 [details]
proposed fix

Comment 4 Ivan Devat 2017-01-16 14:45:36 UTC
Before Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-10.el7.x86_64

[vm-rhel72-1 ~] $ pcs resource create gettytest systemd:getty@tty3
Error: Unable to create resource 'systemd:getty@tty3', it is not installed on this system (use --force to override)


After Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-10.el7_3.1.x86_64

[vm-rhel72-1 ~] $ pcs resource create gettytest systemd:getty@tty3
[vm-rhel72-1 ~] $ pcs status
Cluster name: devcluster
Stack: corosync
Current DC: vm-rhel72-3 (version 1.1.15-8.el7-e174ec8) - partition with quorum
Last updated: Fri Jan  6 12:33:07 2017          Last change: Fri Jan  6 12:32:40 2017 by root via cibadmin on vm-rhel72-1

2 nodes and 2 resources configured

Online: [ vm-rhel72-1 vm-rhel72-3 ]

Full list of resources:

 xvm-fencing    (stonith:fence_xvm):    Started vm-rhel72-1
 gettytest      (systemd:getty@tty3):   Started vm-rhel72-3

Daemon Status:
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/enabled

Comment 8 errata-xmlrpc 2017-01-30 15:56:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0210.html