2.21-2-B40:ip_address parameter in VM name is resulting in incorrect IP being assigned to the VM instance.
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Medium
|
Ashok Singh | |||
R2.21.x |
Fix Committed
|
Medium
|
Ashok Singh | |||
R2.22.x |
Fix Committed
|
Medium
|
Ashok Singh | |||
R3.0 |
Fix Committed
|
Medium
|
Ashok Singh | |||
R3.0.2.x |
Fix Committed
|
Medium
|
Ashok Singh | |||
R3.1 |
In Progress
|
Medium
|
Ashok Singh | |||
Trunk |
Fix Committed
|
Medium
|
Ashok Singh |
Bug Description
A VM is created from horizon with the VM name defined as "vm2 --ip_address=
Steps to replicate :
1. Create an Image and a Virtual Network (for ex. 50.50.50.0/24)
2. Launch Horizon, go to Project -> Instances -> Launch Instance.
3. In the Instance Name, key in "vm2 --ip_address=
4. Launch the instance the usual way by populating other fields.
Once the VM is launched, the VM takes the IP address 50.50.50.200 instead of picking a free IP address from the VN 50.50.50.0/24.
Maybe, ip_address is a valid parameter and should not be used in VM name ? Please add some GUI validation allowing user not to launch an instance should that be the case.
Greetings,
Sandeep.
This is how it is supposed to behave, keys are passed like this.
Config already has a bug of allocating dup IIP's.