On 06/03/2016 01:39 PM, Nikhil Utane wrote:
> Thanks for your response Klaus.
> Any command to add the cluster name?
> All examples use 'pcs cluster setup' command. But if my cluster is
> already running, how do I update it?
> I tried with crm_attribute:
> crm_attribute -t crm_config -n cluster-name -v mycluster
>
> It has updated in cib but pcs status still doesn't show the cluster name.

Somewhere in the back of my mind something is telling me it wanted to
have the name in corosync.conf
as well.

totem {
...
    cluster_name: mycluster
...
}

>
>     <crm_config>
>       <cluster_property_set id="cib-bootstrap-options">
>         <nvpair id="cib-bootstrap-options-have-watchdog"
> name="have-watchdog" value="true"/>
>         <nvpair id="cib-bootstrap-options-dc-version"
> name="dc-version" value="1.1.14-5a6cdd1"/>
>         <nvpair id="cib-bootstrap-options-cluster-infrastructure"
> name="cluster-infrastructure" value="corosync"/>
>         <nvpair id="cib-bootstrap-options-cluster-name"
> name="cluster-name" value="mycluster"/>
>       </cluster_property_set>
>
> [root@airv_cu root]# pcs status
> Cluster name:
>
> -Regards
> Nikhil
>
>
> On Fri, Jun 3, 2016 at 4:46 PM, Klaus Wenninger <kwenn...@redhat.com
> <mailto:kwenn...@redhat.com>> wrote:
>
>     On 06/03/2016 01:03 PM, Nikhil Utane wrote:
>     > Hi,
>     >
>     > The node is up alright.
>     >
>     > [root@airv_cu pcs]# pcs cluster status
>     > Cluster Status:
>     >  Stack: corosync
>     >  Current DC: airv_cu (version 1.1.14-5a6cdd1) - partition
>     WITHOUT quorum
>     >  Last updated: Fri Jun  3 11:01:32 2016         Last change: Fri Jun
>     >  3 09:57:52 2016 by hacluster via crmd on airv_cu
>     >  2 nodes and 0 resources configured
>     >
>     > Upon entering command "pcs cluster standby airv_cu" getting
>     below error.
>     > Error: cannot load cluster status, xml does not conform to the
>     schema.
>     >
>     > What could be wrong?
>     >
>     > [root@airv_cu pcs]# pcs cluster cib
>     > <cib crm_feature_set="3.0.10" validate-with="pacemaker-2.4"
>     epoch="4"
>     > num_updates="5" admin_epoch="0" cib-last-written="Fri Jun  3
>     09:57:52
>     > 2016" update-origin="airv_cu" update-client="crmd"
>     > update-user="hacluster" have-quorum="0" dc-uuid="1">
>     >   <configuration>
>     >     <crm_config>
>     >       <cluster_property_set id="cib-bootstrap-options">
>     >         <nvpair id="cib-bootstrap-options-have-watchdog"
>     > name="have-watchdog" value="true"/>
>     >         <nvpair id="cib-bootstrap-options-dc-version"
>     > name="dc-version" value="1.1.14-5a6cdd1"/>
>     >         <nvpair id="cib-bootstrap-options-cluster-infrastructure"
>     > name="cluster-infrastructure" value="corosync"/>
>     Your cluster doesn't have a name. iirc pcs (at least I've seen
>     that in a
>     version I was working with) doesn't like that.
>
>     Something like:
>             <nvpair id="cib-bootstrap-options-cluster-name"
>     name="cluster-name" value="mycluster"/>
>
>     >       </cluster_property_set>
>     >     </crm_config>
>     >     <nodes>
>     >       <node id="1" uname="airv_cu"/>
>     >       <node id="2" uname="0005B9888880"/>
>     >     </nodes>
>     >     <resources/>
>     >     <constraints/>
>     >   </configuration>
>     >   <status>
>     >     <node_state id="1" uname="airv_cu" in_ccm="true" crmd="online"
>     > crm-debug-origin="do_state_transition" join="member"
>     expected="member">
>     >       <lrm id="1">
>     >         <lrm_resources/>
>     >       </lrm>
>     >       <transient_attributes id="1">
>     >         <instance_attributes id="status-1">
>     >           <nvpair id="status-1-shutdown" name="shutdown" value="0"/>
>     >         </instance_attributes>
>     >       </transient_attributes>
>     >     </node_state>
>     >   </status>
>     > </cib>
>     >
>     > -Thanks
>     > Nikhil
>     >
>     >
>     >
>     > _______________________________________________
>     > Users mailing list: Users@clusterlabs.org
>     <mailto:Users@clusterlabs.org>
>     > http://clusterlabs.org/mailman/listinfo/users
>     >
>     > Project Home: http://www.clusterlabs.org
>     > Getting started:
>     http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>     > Bugs: http://bugs.clusterlabs.org
>
>
>     _______________________________________________
>     Users mailing list: Users@clusterlabs.org
>     <mailto:Users@clusterlabs.org>
>     http://clusterlabs.org/mailman/listinfo/users
>
>     Project Home: http://www.clusterlabs.org
>     Getting started:
>     http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>     Bugs: http://bugs.clusterlabs.org
>
>

_______________________________________________
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to