nova boot --number-instances with v4-fixed-ip

Bug #1318754 reported by Lawrance
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Aaron Rosen

Bug Description

we can not run multi instances with v4-fixed-ip, as we know , the special ip can only belong to one instance, so i think while we specific the v4-fixed-ip, we could't use --num-instances .

HOW to reproduce:

nova boot --image cirros --flavor 1 --num-instances 2 --nics net-id=759e99ad...,v4-fixed-ip=10.0.0.17 instance001

Revision history for this message
xuan.mingyi (xuan-mingyi) wrote :

I think it should reports an error msg

Changed in nova:
status: New → Confirmed
Tracy Jones (tjones-i)
tags: added: network
Revision history for this message
Aaron Rosen (arosen) wrote :

I agree, I think we should raise an error message if --num-instances > 2 && v4-fixed-ip are used in conjunction.

Changed in nova:
assignee: nobody → Aaron Rosen (arosen)
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/94691
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1181d5e65f5488bdd147ef28ffe3e14c09862cec
Submitter: Jenkins
Branch: master

commit 1181d5e65f5488bdd147ef28ffe3e14c09862cec
Author: Aaron Rosen <email address hidden>
Date: Wed May 21 11:15:20 2014 -0700

    Prevent max_count > 1 and specified ip address as input

    Previously, if one did:
       nova boot --num-instances 2 --nic net-id=<net_id>,v4-fixed-ip=10.0.0.17
    this would result in all of the instances failing to boot because neither
    nova-network or neutron allows multiple instances to have the same ip_address.
    This patch fixes this from occuring by checking for this and raising an error
    to the caller from nova-api.

    Change-Id: I7e44d58e66aeb10fb15c3553072f988f65ab823b
    Closes-bug: 1318754

Changed in nova:
status: In Progress → Fix Committed
tags: added: icehouse-backport-potential
Changed in nova:
milestone: none → juno-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: juno-2 → 2014.2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/icehouse)

Fix proposed to branch: stable/icehouse
Review: https://review.openstack.org/155608

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (stable/icehouse)

Change abandoned by yanheven (<email address hidden>) on branch: stable/icehouse
Review: https://review.openstack.org/155608
Reason: this is a 'medium' bug, and I don't think it deserves a higher level, since the bug is hit due to human error (partly). This means that it is not an appropriate commit for Icehouse, since Icehouse is in Support II Phase, which means only critical and security bug fixes are acceptable.

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.