After stop the resource p_neutron-dhcp-agent corosync does not start it

Bug #1462440 reported by Egor Kotko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Library (Deprecated)

Bug Description

{"build_id": "2015-06-02_16-28-25", "build_number": "497", "release_versions": {"2014.2.2-6.1": {"VERSION": {"build_id": "2015-06-02_16-28-25", "build_number": "497", "api": "1.0", "fuel-library_sha": "d757cd41e4f8273d36ef85b8207e554e5422c5b0", "nailgun_sha": "3830bdcb28ec050eed399fe782cc3dd5fbf31bde", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "4fc55db0265bbf39c369df398b9dc7d6469ba13b", "astute_sha": "cbae24e9904be2ff8d1d49c0c48d1bdc33574228", "fuel-ostf_sha": "f899e16c4ce9a60f94e7128ecde1324ea41d09d4", "release": "6.1", "fuelmain_sha": "bcc909ffc5dd5156ba54cae348b6a07c1b607b24"}}}, "auth_required": true, "api": "1.0", "fuel-library_sha": "d757cd41e4f8273d36ef85b8207e554e5422c5b0", "nailgun_sha": "3830bdcb28ec050eed399fe782cc3dd5fbf31bde", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-6.1", "production": "docker", "python-fuelclient_sha": "4fc55db0265bbf39c369df398b9dc7d6469ba13b", "astute_sha": "cbae24e9904be2ff8d1d49c0c48d1bdc33574228", "fuel-ostf_sha": "f899e16c4ce9a60f94e7128ecde1324ea41d09d4", "release": "6.1", "fuelmain_sha": "bcc909ffc5dd5156ba54cae348b6a07c1b607b24"}

Steps to reproduce:
1) Check the status of crm resources:
http://paste.openstack.org/show/266385/
2) Stop the p_neutron-dhcp-agent
crm resource stop p_neutron-dhcp-agent

Actual result:
After 10 min resource was not recovered:
http://paste.openstack.org/show/266387/

Tags: corosync
Revision history for this message
Egor Kotko (ykotko) wrote :
Revision history for this message
Alex Schultz (alex-schultz) wrote :

If you "crm resource stop p_neutron-dhcp-agent", you have stopped this resource and it won't start again until you tell it to start. Did you issue a start and it did you perhaps mean to do a "crm resource restart p_neutron-dhcp-agent" or were you trying to stop it on a single node only?

From the crm man page[0]:

       stop
           Stop a resource using the target-role attribute. If there are
           multiple meta attributes sets, the attribute is set in all of them.
           If the resource is a clone, all target-role attributes are removed
           from the children resources.

           For details on group management see options manage-children.

           Usage:

               stop <rsc>

[0] http://manpages.ubuntu.com/manpages/utopic/man8/crm.8.html

Changed in fuel:
status: New → Incomplete
Revision history for this message
Egor Kotko (ykotko) wrote :

Yep, this is invalid case to check dependability via stopping through crm.

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.