Rubygem-staypuft: HA: start-failure-is-fatal: this should be true. It was selectively set to false on some services in OSP4 to workaround other bugs that have been fixed in OSP5. Cluster Properties: cinder: running cluster-infrastructure: corosync dc-version: 1.1.10-32.el7_0-368c726 galera: running glance: running heat: running horizon: running keystone: running last-lrm-refresh: 1406197739 maca25400702875.example.com: memcached,rabbitmq,haproxy,galera,keystone,glance,nova,cinder,heat,horizon maca25400868092.example.com: memcached,rabbitmq,haproxy,galera,keystone,glance,nova,cinder,heat,horizon maca25400868093.example.com: memcached,rabbitmq,haproxy,galera,keystone,glance,nova,cinder,heat,horizon nova: running rabbitmq: running -------------------------------- start-failure-is-fatal: false -------------------------------- stonith-enabled: false
Patch posted: https://github.com/redhat-openstack/astapor/pull/335
Merged
start-failure-is-fatal not present because it no longer needed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1090.html