Ankit1999Raikwar opened a new issue, #7457:
URL: https://github.com/apache/cloudstack/issues/7457
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
~~~
* Networking
* Virtual Machine
~~~
##### CLOUDSTACK VERSION
~~~
4.16.1.0
~~~
##### CONFIGURATION
~~~
Controller Nodes: 3
Compute Nodes: 4
Cloudstack Version: 4.16.1.0
Hypervisor: KVM
Network backend: VLAN
~~~
##### OS / ENVIRONMENT
~~~
Ubuntu Server 20.04 LTS on both Management and Compute Hosts
~~~
##### SUMMARY
We are created the L2-Network nic and attach that nic to the Vm then assign
the static ip to the nic inside the vm . for the backup purpose but when the
VM got reboot or start/stop from the cloudstack . after that l2 nic is
completely go into the disbale state and new nic comes up with the blank ip.
This affects Virtual Networks of type "L2". The vNIC from the L2 network
"vNIC" actually gets replaced with a new one everytime the VM is stopped and
started from the WebUI or API.
##### STEPS TO REPRODUCE
~~~
1. Create L2 network offering as per the infrastructure networking.
2. Create an L2 virtual network from that offering.
3. The L2 network will be successfully created.
4. Attach the L2 network to the Virtual Machine.
5. From inside the Virtual Machine, configure a Static IP for that NIC.
6. Stop the Virtual Machine from WebUI / API.
7. Start the Virtual Machine from WebUI / API.
8. The IP address configured on the VM's NIC is gone.
9. If we show "hidden devices", the NIC appears to be in "disabled" state
with the IP address configured, but is in "disabled" state.
10. On Linux-based Virtual Machines, the new NIC appears.
This is affected the most when this L2 network is a non-default NIC of the
Virtual Machine.
~~~
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The Static IP address should be present even after reboots.
~~~
##### ACTUAL RESULTS
~~~
The older NIC disappears, but the new NIC comes online.
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
