Re: [ClusterLabs] meta-target role stopped in one resource in a group ( SLEHA 11.4 )

[Kristoffer Grönlund]

Cristiano Coltro  writes:

> I have some questions:
>
>
> 1) I believe that the command crm resource stop 
> pri_fs_oracle_FS1_sapdata1 has inserted the instruction meta 
> target-role="Stopped" and this will force the resource to stay offline when 
> the grp_all_FS1 will be online again. Am I correct?

Yes

>
> 2) I believe he can easily delete or maybe a crm resource start 
> pri_fs_oracle_FS1_sapdata1 will delete the instruction. Am I correct again? 
> Testing also in my lab.
>

Yes, again :)

Running "crm resource start" might change it to say
"target-role=Started" but the effect should be the same as not setting
target-role at all.

Cheers,
Kristoffer

> Thanks in advance
> Cristiano
>
>
> Cristiano Coltro
> Premium Support Engineer
>
> mail: cristiano.col...@microfocus.com
> mobile: +39 335 1435589
> phone +39 02 36634936
> __
> [microfocus-logo]
>
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.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

-- 
// Kristoffer Grönlund
// kgronl...@suse.com

___
Users mailing list: Users@clusterlabs.org
http://lists.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

[ClusterLabs] meta-target role stopped in one resource in a group ( SLEHA 11.4 )

[Cristiano Coltro]

Hi all
A customer of mine has a resource group : grp_all_FS1 so compiled:

Resource Group: grp_all_FS1
 pri_lvm_vgFS1  (ocf::heartbeat:LVM):   Started xita1868 (unmanaged)
 pri_lvm_vgFS1ascs  (ocf::heartbeat:LVM):   Started xita1868 (unmanaged)
 pri_lvm_vgFS1data  (ocf::heartbeat:LVM):   Started xita1868 (unmanaged)
 pri_lvm_vgFS1log   (ocf::heartbeat:LVM):   Started xita1868 (unmanaged)
 pri_fs_oracle_FS1  (ocf::heartbeat:Filesystem):Started xita1868 
(unmanaged)
 pri_fs_oracle_FS1_112_64   (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_libelle  (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_libelle_ff   (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_mirrlogA (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_mirrlogB (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_origlogA (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_origlogB (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_sapreorg (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_usr_sap_FS1_SCS78   (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_sapdata1 (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_sapdata2 (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_sapdata3 (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_sapdata4 (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_sapdata5 (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_sapdata6 (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_libelle_arch (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_oracle_FS1_oraarch  (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_ip_sapsmfs1_bond0  (ocf::heartbeat:IPaddr2):   Started 
xita1868 (unmanaged)
 pri_lvm_vgFS1ci(ocf::heartbeat:LVM):   Started xita1868 (unmanaged)
 pri_fs_usr_sap_FS1_DVEBMGS77   (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_usr_sap_FS1_solmanup(ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)
 pri_fs_usr_sap_ccms_FS1_77 (ocf::heartbeat:Filesystem):Started 
xita1868 (unmanaged)


The group was put in UNMANAGED state:

For an ERROR he has executed the command  "crm resource stop 
pri_fs_oracle_FS1_sapdata1".
Obviously nothing has happened.

But now if he compare 2 similar resources he can see:

xita1869:~ # crm configure show pri_fs_oracle_FS1_sapdata2
primitive pri_fs_oracle_FS1_sapdata2 ocf:heartbeat:Filesystem \
params device="/dev/vgFS1data/lvoracle_FS1_sapdata2" 
directory="/oracle/FS1/sapdata2" fstype="ext3" 
options="noauto,acl,user_xattr,noatime,nodiratime,barrier=0,data=writeback"

mentre nella configurazione la risorsa che ho erroneamente stoppato risulta 
ovviamente :

primitive pri_fs_oracle_FS1_sapdata1 ocf:heartbeat:Filesystem \
params device="/dev/vgFS1data/lvoracle_FS1_sapdata1" 
directory="/oracle/FS1/sapdata1" fstype="ext3" 
options="noauto,acl,user_xattr,noatime,nodiratime,barrier=0,data=writeback" \
meta target-role="Stopped"


So the meta target-role="Stopped" was added, as it seems

I have some questions:


1) I believe that the command crm resource stop pri_fs_oracle_FS1_sapdata1 
has inserted the instruction meta target-role="Stopped" and this will force the 
resource to stay offline when the grp_all_FS1 will be online again. Am I 
correct?

2) I believe he can easily delete or maybe a crm resource start 
pri_fs_oracle_FS1_sapdata1 will delete the instruction. Am I correct again? 
Testing also in my lab.

Thanks in advance
Cristiano


Cristiano Coltro
Premium Support Engineer

mail: cristiano.col...@microfocus.com
mobile: +39 335 1435589
phone +39 02 36634936
__
[microfocus-logo]

___
Users mailing list: Users@clusterlabs.org
http://lists.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