"keypair_id" should be existent when creating a baymodel

Bug #1476500 reported by Peiyu Lin
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

When creating a baymodel with a invalid or non-existent keypair_id, the creation will be successful. But then the bay creation with baymodel created before will fail and report error.

ERROR: ERROR: Property error: : resources.kube_master.properties.key_name: : Error validating value u'testkey': The Key (testkey) could not be found.

Changed in magnum:
assignee: nobody → Martin Falatic (martinfalatic)
Changed in magnum:
assignee: Martin Falatic (martinfalatic) → nobody
Changed in magnum:
assignee: nobody → bharaththiruveedula (bharath-ves)
Changed in magnum:
status: New → In Progress
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/220746

Revision history for this message
bharaththiruveedula (bharath-ves) wrote :

@vikas, Please check the code here https://review.openstack.org/#/c/180158/. There we are checking the only input length of keypair. So it is not a duplicate bug, please double check it

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

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

commit 6249e776eb6330003e13f8bac2df2885da477164
Author: Bharath Thiruveedula <email address hidden>
Date: Sat Sep 5 23:45:07 2015 +0530

    "keypair_id" should be existent when creating a baymodel

    While creating the baymodel we must check existence of keypair-id,
    So that we can avoid keypair NotFound error while creating the bay.

    Change-Id: I3796503bac05a9aa1c9d155e93447a95fb567daf
    Closes-Bug: #1476500

Changed in magnum:
status: In Progress → Fix Committed
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.