DragonFlow

VM isn't getting an IP using Nova api boot

Bug #1577121 reported by Shlomo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DragonFlow
Invalid
High
vikas choudhary

Bug Description

While creating a VM using the nova boot command, the VM isn't getting and IP address.
While creating a VM via the UI, the VM gets an IP address.

This bug can be reproduced only with the security groups application.
Without the SGApp, the VM gets an IP address.

Maybe the it's related to the default SG.

Revision history for this message
Gal Sagie (gal-sagie) wrote :

Please investigate this bug, even if its related to the default SG i dont see why there should be a difference between the CLI and the Web UI

Changed in dragonflow:
assignee: nobody → Shlomo (shlominar)
importance: Undecided → High
Revision history for this message
Shlomo (shlominar) wrote :

I have tried to investigate it and unfortunately have no clue why this happening.
Need to debug the SG code, because the bug isn't occur while the SGApp is disabled.

Changed in dragonflow:
assignee: Shlomo (shlominar) → nobody
vikas choudhary (choudharyvikas16)
Changed in dragonflow:
assignee: nobody → vikas choudhary (choudharyvikas16)
status: New → In Progress
Revision history for this message
Shlomo (shlominar) wrote :

I have used the nova boot command.

nova boot --image Image_Name --flavor m1.small --nic net-id=$netId1 --availability-zone nova:$computeNode

Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

I tried with both, UI and command line, VMs are getting IPs in both cases. I can also see sg flows getting added into br-int. Command i used is this:

nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.small --key-name key2 --nic net-id=fa9f89ac-715a-4ebc-b61e-a67d0ac3f6dc --security-groups default mytest_vm

stack@PRINHYLTPHP0400:/home/vikasc/devstack$ nova list
+--------------------------------------+-----------+--------+------------+-------------+--------------------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
 +--------------------------------------+-----------+--------+------------+-------------+--------------------------------------------------------+
| 63f6d716-d13d-4da8-a9fd-7045641fbd31 | mytest_vm | ACTIVE | - | Running | private=fded:a0d4:e98d:0:f816:3eff:fea6:6ee0, 50.0.0.4 |
 +--------------------------------------+-----------+--------+------------+-------------+-------------------------------------------------------

Please find attached snapshot also.

Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

I am marking it INVALID for now.

Changed in dragonflow:
status: In Progress → Invalid
Revision history for this message
Shlomo (shlominar) wrote :

Thanks for validating the bug.

Revision history for this message
Shlomo (shlominar) wrote :

I have just re-validated the bug, seams like it's not reproduce-able.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.