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 1229826 - Please consider adding a note that "pcs cluster create" and block of further commands defining resources etc. should be run after certain amount of time to prevent a failure
Summary: Please consider adding a note that "pcs cluster create" and block of further ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-High_Availability_Add-On_Administration
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 1194761 1229822 1872490
Blocks: 1251196
TreeView+ depends on / blocked
 
Reported: 2015-06-09 17:47 UTC by Jan Pokorný [poki]
Modified: 2020-08-26 14:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1229822
: 1251196 (view as bug list)
Environment:
Last Closed: 2015-11-24 21:05:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Pokorný [poki] 2015-06-09 17:47:52 UTC 
...at least until --wait is provided for the former akin to subcommands
already covered:

+++ This bug was initially created as a clone of Bug #1229822 +++

In clufter's pcs-commands output (meant for little-to-no-edit execution)
an obstacle was found with "cluster create --start" followed immediately
with "cluster cib-push" because -- apparently -- cluster stack is not
up and running by this time yet.

Workaround is to put a fixed-time sleep in between:
https://github.com/jnpkrn/clufter/commit/a197f61d4ebe404902a8693473ec2c71bd0967c0

Better solution would be to make pcs do a proper job and *not* return
until cluster has started (or return with appropriate exit status
when this hadn't been successful as soon as a failure is detected).
Comment 1 Jan Pokorný [poki] 2015-06-09 17:49:22 UTC 
Or alternatively, after "pcs cluster status" indicates the stack is
already running.
Comment 3 Steven J. Levine 2015-08-06 16:46:07 UTC 
Cloning this for RHEL 6 since this note should be there as well.
Comment 4 Steven J. Levine 2015-08-06 17:35:23 UTC 
Two questions for Chris Feist:

1.
The description of this BZ refers to the "pcs cluster create" command -- but I think that should be the "pcs cluster setup" command. Chris:  Is that correct?

2.
When I document the "pcs cluster setup" command -- in both the Reference Guide and in the admin/procedure guide -- would this work as a note:

Note:
When you create a cluster with the [pcs cluster setup] command, there may be a slight delay before the cluster is up and running. Before performing any subsequent actions on the cluster and its configuration, it is recommended that you use the "pcs cluster status" command to be sure that the cluster is up and 
running.


-----
Although it seems that same note could apply to a variety of pcs commands. Checking the status at each step is already part of the administration procedure we provide, and this will be emphasized in the planned "troubleshooting" documentation. But for now, would a note this simple address the issue in this BZ?
Comment 5 Steven J. Levine 2015-08-06 19:03:15 UTC 
Followup:  Re, question 1:  Oh, sorry. Yes, "pcs cluster start" -- the problem is that in the documented procedures we use pcs cluster setup --start. So I have the answer to that question, although maybe I need to add something about "pcs cluster start" to the reference manual.

Question 2 is the main question here....
Comment 6 Chris Feist 2015-08-31 21:44:07 UTC 
Steven,

For #2 yes that note will work.

Also in the future we will most likely add the "--wait" command to 'cluster start' & 'cluster setup --start' so pcs will do the waiting for you.
Comment 7 Steven J. Levine 2015-09-01 20:24:07 UTC 
I have added that note to the description of the cluster setup command in the Reference manual and to the cluster setup configuration step in the administration manual.
Comment 8 Steven J. Levine 2015-11-05 20:20:03 UTC 
Moving the VERIFIED in preparation for 7.2 GA, since Chris approved the change.
Note You need to log in before you can comment on or make changes to this bug.