Bug 1229826
| Summary: | 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 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Pokorný [poki] <jpokorny> | |
| Component: | doc-High_Availability_Add-On_Administration | Assignee: | Steven J. Levine <slevine> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 7.2 | CC: | abeekhof, cfeist, cluster-maint, cluster-qe, fdinitto, phagara, slevine, tojeline | |
| Target Milestone: | rc | Keywords: | Documentation, FutureFeature | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1229822 | |||
| : | 1251196 (view as bug list) | Environment: | ||
| Last Closed: | 2015-11-24 21:05:15 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: | ||||
| Bug Depends On: | 1194761, 1229822, 1872490 | |||
| Bug Blocks: | 1251196 | |||
|
Description
Jan Pokorný [poki]
2015-06-09 17:47:52 UTC
Or alternatively, after "pcs cluster status" indicates the stack is already running. Cloning this for RHEL 6 since this note should be there as well. 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? 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.... 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. 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. Moving the VERIFIED in preparation for 7.2 GA, since Chris approved the change. |