output from cluster update is not showing the latest cluster property

Bug #1646355 reported by Qiming Teng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
senlin
Invalid
Medium
Yanyan Hu

Bug Description

Output from the following command:

  senlin cluster-update -n new_name old_name

is not showing the cluster name changed to 'new_name'. It is still showing the 'old_name'.

We can only do cluster-list or cluster-show again to get the latest view.

This has to be changed.

Qiming Teng (tengqim)
Changed in senlin:
status: New → Confirmed
importance: Undecided → Medium
summary: - output cluster update is not showing the latest cluster property
+ output from cluster update is not showing the latest cluster property
Yanyan Hu (yanyanhu)
Changed in senlin:
assignee: nobody → Yanyan Hu (yanyanhu)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to senlin (master)

Fix proposed to branch: master
Review: https://review.openstack.org/409021

Changed in senlin:
status: Confirmed → In Progress
Revision history for this message
Yanyan Hu (yanyanhu) wrote :

The same problem exists for node-update.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/409029

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on senlin (master)

Change abandoned by Yanyan Hu (<email address hidden>) on branch: master
Review: https://review.openstack.org/409021
Reason: This is not a bug.

Revision history for this message
Yanyan Hu (yanyanhu) wrote :

This is not a bug for the cluster property has not been changed yet when response is sent back to requester. Will update API reference to explain this design.

Changed in senlin:
status: In Progress → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Yanyan Hu (<email address hidden>) on branch: master
Review: https://review.openstack.org/409029
Reason: This is not a bug.

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.