rpc responce "status_reason" is not finally result

Bug #1545963 reported by zhaozhilong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
senlin
Fix Released
Low
Qiming Teng

Bug Description

1). we can see the response of senlin as below:
openstack.cluster.v1.cluster.Cluster(attrs={u'status': u'INIT', u'domain': None, u'policies': [], 'profile_id': u'c5603c40-9907-4bff-a6ec-4e48f5217eed', u'updated_at': None, 'min_size': 1, u'profile_name': u'bug1-oprofile-4mzpf4arsyk5', u'user': u'0818abde5a934a0ba7cfda39798cf7c5', u'data': {}, u'id': u'a0981eab-70f6-4fb8-8017-430f880e9ba5', 'max_size': 3, 'headers': {'Content-Length': '582', 'Connection': 'keep-alive', 'Location': 'http://192.168.122.1:8778/v1/clusters/a0981eab-70f6-4fb8-8017-430f880e9ba5', 'Date': 'Tue, 16 Feb 2016 07:38:56 GMT', 'Content-Type': 'application/json; charset=UTF-8', 'X-Openstack-Request-Id': 'req-9f5f1f78-e5c8-49bd-837b-816b3637c8ce'}, 'name': u'demo', u'init_at': u'2016-02-16T07:38:09', u'status_reason': u'Initializing', u'created_at': None, u'project': u'1acd0026829f4d28bb2eff912d7aad0d', 'desired_capacity': 2, 'timeout': 60, u'action': u'18f86486-a9f0-4629-a8c0-72c783313e60', u'nodes': [], 'metadata': {}}, loaded=False)

2). we can see the status_reason is 'Initializing', but my cluster really create false:
# senlin cluster-list
+----------+------+----------+------------+------------+
| id | name | status | created_at | updated_at |
+----------+------+----------+------------+------------+
| a0981eab | demo | ERROR | None | None
+----------+------+----------+------------+------------+

3). for it reason , heat can not identified cluster create successfully or not .

description: updated
no longer affects: heat
Qiming Teng (tengqim)
Changed in senlin:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Ethan Lynn (ethanlynn) wrote :

Hi zilong, I'm not sure what do you mean by 'heat can not identified cluster create successfully or not'. Heat check status, not status reason, when the status is 'active' or 'warning', heat will consider it as success. if status is 'error' heat will consider it as failed.

Qiming Teng (tengqim)
Changed in senlin:
milestone: none → mitaka-3
assignee: nobody → Qiming Teng (tengqim)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to senlin (master)

Reviewed: https://review.openstack.org/285619
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=86997e58dd32c355a2548b3af285a165fe2a06ee
Submitter: Jenkins
Branch: master

commit 86997e58dd32c355a2548b3af285a165fe2a06ee
Author: tengqm <email address hidden>
Date: Fri Feb 26 22:46:02 2016 -0500

    Fix cluster status_reason setting when actions failed

    There are cases where the create/update/delete actions failed but the
    cluster status_reason is not properly set. This patch fixes it.

    Change-Id: Ief266969c612465a3889e2c5101e24fa4f50b046
    Closes-Bug: #1545963

Changed in senlin:
status: Triaged → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/senlin 1.0.0.0b3

This issue was fixed in the openstack/senlin 1.0.0.0b3 development milestone.

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.