<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Ulrich,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Yes, I remembered you mentioned this multi target-role issue<br>
<a href="https://github.com/ClusterLabs/crmsh/issues/720" id="LPNoLPOWALinkPreview">https://github.com/ClusterLabs/crmsh/issues/720</a><br>
<div class="_Entity _EType_OWALinkPreview _EId_OWALinkPreview _EReadonly_1"></div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Users <users-bounces@clusterlabs.org> on behalf of Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de><br>
<b>Sent:</b> Thursday, June 2, 2022 2:08 PM<br>
<b>To:</b> users@clusterlabs.org <users@clusterlabs.org><br>
<b>Subject:</b> [ClusterLabs] Q: "Multiple attributes match name=target-role"</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi!<br>
<br>
We had some issue with a resource in SLES15 SP3, so I cleaned the error:<br>
h16:~ # crm_resource -C -r prm_xen_v07 -N h18 -n start<br>
Cleaned up prm_xen_v07 on h18<br>
Multiple attributes match name=target-role<br>
Value: Started (id=prm_xen_v07-meta_attributes-target-role)<br>
Value: Started (id=prm_xen_v07-meta_attributes-0-target-role)<br>
Value: Started (id=prm_xen_v07-meta_attributes-1-target-role)<br>
<br>
There have always been multiple target roles in the past, but I never saw this complaint, making me woner whether a recent update introduced that feature.<br>
<br>
crmsh-4.3.1+20220505.cf4ab649-150200.5.80.1.noarch<br>
pacemaker-2.0.5+20201202.ba59be712-150300.4.21.1.x86_64<br>
<br>
primitive prm_xen_v07 VirtualDomain \<br>
params config="/etc/xen/vm/v07.xml" hypervisor="xen:///system" remoteuri="xen+tls://%n.uni-regensburg.de" autoset_utilization_cpu=false autoset_utilization_hv_memory=false \<br>
op start timeout=120 interval=0 \<br>
op stop timeout=240 interval=0 \<br>
op monitor interval=600 timeout=90 \<br>
op migrate_to timeout=120 interval=0 \<br>
op migrate_from timeout=120 interval=0 \<br>
utilization utl_cpu=20 utl_ram=2048 \<br>
meta priority=8900 allow-migrate=true target-role=Started \<br>
meta 1: resource-stickiness=5 target-role=Started \<br>
meta 2: rule 0: date spec hours=7-19 weekdays=1-5 resource-stickiness=1000 target-role=Started<br>
<br>
AFAIR a crm resource start/stop set the target-role in every rule in the past.<br>
<br>
Finally: The resource is running fine on h16, but pacemaker keeps complaining it isn't started.<br>
Jun 02 08:03:21 h16 pacemaker-schedulerd[7494]: warning: Unexpected result (error: Failed to start virtual domain v07.) was recorded for start of prm_xen_v07 on h19 at Jun 1 09:19:46 2022<br>
Jun 02 08:03:21 h16 pacemaker-schedulerd[7494]: warning: Forcing prm_xen_v07 away from h19 after 1000000 failures (max=1000000)<br>
<br>
Also it does not try to stop it there. Could it be that this is another effect of the RAM corruption introduced with SLES15 SP3? h16 is DC...<br>
<br>
Regards,<br>
Ulrich<br>
<br>
<br>
<br>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/">https://www.clusterlabs.org/</a><br>
<br>
</div>
</span></font></div>
</body>
</html>