Bug 1293726 - rhel-osp-director: 8.0 - heat resources are stopped in "pcs status" output.
Summary: rhel-osp-director: 8.0 - heat resources are stopped in "pcs status" output.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 8.0 (Liberty)
Assignee: Jiri Stransky
QA Contact: Alexander Chuzhoy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-22 21:06 UTC by Alexander Chuzhoy
Modified: 2016-04-07 21:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-07 21:43:55 UTC
Target Upstream Version:


Attachments (Terms of Use)
logs from one controller. (4.56 MB, application/x-gzip)
2015-12-22 21:11 UTC, Alexander Chuzhoy
no flags Details
crm report from rhos 7.1 with the same issue (2.83 MB, application/x-bzip)
2016-01-14 03:38 UTC, Alexander Chuzhoy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0604 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 director Enhancement Advisory 2016-04-08 01:03:56 UTC

Description Alexander Chuzhoy 2015-12-22 21:06:02 UTC
rhel-osp-director: 8.0 - heat resources are stopped in "pcs status" output.

Environment:
python-heatclient-0.8.0-1.el7ost.noarch
openstack-heat-engine-5.0.0-1.el7ost.noarch
openstack-heat-common-5.0.0-1.el7ost.noarch
openstack-heat-api-cfn-5.0.0-1.el7ost.noarch
openstack-heat-api-cloudwatch-5.0.0-1.el7ost.noarch
openstack-heat-api-5.0.0-1.el7ost.noarch


Steps to reproduce:
1. Deploy HA overcloud (used Bare metal setup with network isolation).
2. Run  pcs status|grep -B2 -i stop


Result:
 Clone Set: openstack-heat-engine-clone [openstack-heat-engine]
     Started: [ overcloud-controller-0 overcloud-controller-2 ]
     Stopped: [ overcloud-controller-1 ]
--
 Clone Set: openstack-heat-api-clone [openstack-heat-api]
     Started: [ overcloud-controller-0 overcloud-controller-2 ]
     Stopped: [ overcloud-controller-1 ]
--
 Clone Set: openstack-heat-api-cloudwatch-clone [openstack-heat-api-cloudwatch]
     Started: [ overcloud-controller-0 overcloud-controller-2 ]
     Stopped: [ overcloud-controller-1 ]
--
 Clone Set: openstack-heat-api-cfn-clone [openstack-heat-api-cfn]
     Started: [ overcloud-controller-0 overcloud-controller-2 ]
     Stopped: [ overcloud-controller-1 ]


Expected result:
No stopped services.

Comment 2 Alexander Chuzhoy 2015-12-22 21:11:08 UTC
Created attachment 1108707 [details]
logs from one controller.

Comment 3 Alexander Chuzhoy 2015-12-22 21:16:11 UTC
Environment:
instack-undercloud-2.2.0-1.el7ost.noarch

Comment 4 Alexander Chuzhoy 2016-01-04 17:31:08 UTC
The issue doesn't re-occur on every deployment.

Comment 5 chris alfonso 2016-01-04 17:32:42 UTC
Sasha, please attach a crm report and we'll send it over to the HA team

Comment 6 Alexander Chuzhoy 2016-01-14 03:38:40 UTC
Created attachment 1114646 [details]
crm report from rhos 7.1  with the same issue

Comment 8 Hugh Brock 2016-02-05 14:43:20 UTC
Sasha can you retest this on the latest OSPd 8 puddle once we have one? We need a CRM report from the failure on that code base, if it is still recurring.

Comment 9 Alexander Chuzhoy 2016-02-23 17:23:02 UTC
Verified:

Environment:
python-heatclient-0.8.0-1.el7ost.noarch
openstack-heat-api-cfn-5.0.1-1.el7ost.noarch
openstack-heat-templates-0-0.1.20151019.el7ost.noarch
openstack-tripleo-heat-templates-0.8.7-12.el7ost.noarch
openstack-heat-api-5.0.1-1.el7ost.noarch
openstack-heat-engine-5.0.1-1.el7ost.noarch
openstack-tripleo-heat-templates-kilo-0.8.7-12.el7ost.noarch
openstack-heat-api-cloudwatch-5.0.1-1.el7ost.noarch
openstack-heat-common-5.0.1-1.el7ost.noarch



Deployed HA overcloud with network isolation: no stopped pcs resources .

Comment 12 errata-xmlrpc 2016-04-07 21:43:55 UTC
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.

https://rhn.redhat.com/errata/RHEA-2016-0604.html


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