Failed to scale-down kub cluster

Bug #1509439 reported by Egor Guz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Vilobh Meshram

Bug Description

 eguz@ubuntu-vm:/mnt/hgfs/magnum-integration/kubectl$ magnum bay-update k8sbay replace node_count=1
 ERROR: 'Bay' object has no attribute 'bay_uuid' (HTTP 500)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

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

Changed in magnum:
assignee: nobody → Vilobh Meshram (vilobhmm)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/239062
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=f231a609425fc053b5bfd450b219aacaac3008e4
Submitter: Jenkins
Branch: master

commit f231a609425fc053b5bfd450b219aacaac3008e4
Author: Vilobh Meshram <email address hidden>
Date: Fri Oct 23 11:34:16 2015 -0700

    Fix the failure to scale-down k8s cluster

    Fix the failure to scale-down k8s cluster. We were getting this
    failure because as part of scaling, Bay needs to be retrieved for
    the respective k8s obj. But if the object passed is a Bay itself
    we need not retrieve the Bay. At present even for Bay object the
    code proceeds ahead to retrieve bay and cannot find bay_uuid
    attribute. This patch fixes this problem.

    We might need to backport this fix to stable/liberty as well.

    Change-Id: I7ed03af8bdbb8647851751bb550d9529d96b5cb4
    Closes-Bug: #1509439

Changed in magnum:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (stable/liberty)

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/239219

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (stable/liberty)

Reviewed: https://review.openstack.org/239219
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=2b17b77304464d35f03822ef99dd5ef9122a53f7
Submitter: Jenkins
Branch: stable/liberty

commit 2b17b77304464d35f03822ef99dd5ef9122a53f7
Author: Vilobh Meshram <email address hidden>
Date: Fri Oct 23 11:34:16 2015 -0700

    Fix the failure to scale-down k8s cluster

    Fix the failure to scale-down k8s cluster. We were getting this
    failure because as part of scaling, Bay needs to be retrieved for
    the respective k8s obj. But if the object passed is a Bay itself
    we need not retrieve the Bay. At present even for Bay object the
    code proceeds ahead to retrieve bay and cannot find bay_uuid
    attribute. This patch fixes this problem.

    This change has been back ported from master to stable/liberty.

    Change-Id: I7ed03af8bdbb8647851751bb550d9529d96b5cb4
    Closes-Bug: #1509439
    (cherry picked from commit f231a609425fc053b5bfd450b219aacaac3008e4)

tags: added: in-stable-liberty
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
status: Fix Committed → Fix Released
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.