Bug 1293959 - The showed status of the resource does not equal the target-role
The showed status of the resource does not equal the target-role
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker (Show other bugs)
x86_64 Linux
unspecified Severity low
: rc
: ---
Assigned To: Ken Gaillot
Depends On:
  Show dependency treegraph
Reported: 2015-12-23 12:24 EST by Raoul Scarazzini
Modified: 2016-02-02 09:39 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-02 09:39:34 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Raoul Scarazzini 2015-12-23 12:24:42 EST
While playing with our ospd-ha 8 environment we got into this strange problem. We set the nova-compute-clone resource to disabled. E.g. see the following "target-role":

 Clone: nova-compute-clone
  Meta Attrs: interleave=true target-role=Stopped 
  Resource: nova-compute (class=ocf provider=openstack type=NovaCompute)
   Attributes: auth_url= username=admin password=KAcGkxF6Nkw2AgEFJ8yUqEQu2 tenant_name=admin domain=localdomain 
   Operations: stop interval=0s timeout=300 (nova-compute-stop-interval-0s)

Then we did a cleanup of nova-compute-clone in order to remove some of the failed actions associated with the resource that took place before disabling the resource.
After the cleanup we were surprised to observe the following:

 Clone Set: nova-compute-clone [nova-compute]
     Started: [ overcloud-novacompute-2 ]
     Stopped: [ overcloud-controller-0 overcloud-controller-1 overcloud-controller-2 overcloud-novacompute-0 overcloud-novacompute-1 overcloud-novacompute-3 ]

Eventually, after a bit more time, all nova-compute-clone resources became stopped.
But in our opinion it should never have even started one on novacompute-2 because
the nova-compute-clone resource was disabled.

We upload corosync.log (http://file.rdu.redhat.com/~rscarazz/scale-lab-controller-2-corosync.20151223.log.bz2) from the DC of the 3-node OSP cluster (+ 4 remoted). We do not have a very exact timing of the events as we did a lot of different tests today. The issue happened today after 08:50 EST.

We will try to add more details, should we spot this issue again.
Comment 4 Andrew Beekhof 2016-01-10 19:39:10 EST
Highly unlikely that we would have started it.
More likely, we found it running (ie. it hadn't been stopped prior to the cleanup being  run).
Comment 5 Ken Gaillot 2016-01-18 17:42:45 EST
It does look like nova-compute was somehow started outside cluster control.

I see target-role set to Stopped multiple times (04:17:54, 05:32:09, 05:36:27, 05:49:28, and 06:45:25).

After the last one, the cluster correctly ensures nova-compute is stopped on all compute nodes.

It appears that cleanup was run at 11:04:44. The cluster initiates probes (one-time monitor operations) on all 4 compute nodes, finds nova-compute running on overcloud-novacompute-1 and overcloud-novacompute-2, and stops them.

This implies that the service was started outside cluster control sometime between 06:45:25 and 11:04:44. (Pacemaker won't run the regular recurring monitor while the service is stopped, although it is possible to configure a recurring monitor for target-role=Stopped exactly for the purpose of catching cases like this sooner.)

If you want me to investigate further on the pacemaker side, let me know, but I think the issue is likely elsewhere.
Comment 6 Raoul Scarazzini 2016-02-02 04:01:05 EST
Ok, further investigations on this issue also ended up in additional problems with the resource agent, so I think that this bug can be closed, also because that lab is not available anymore.

Note You need to log in before you can comment on or make changes to this bug.