Thomas Moroder created CLOUDSTACK-7399:
------------------------------------------
Summary: broadcast_uri and possibly isolation_uri is not set
correctly with Basic Network
Key: CLOUDSTACK-7399
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7399
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.4.0
Environment: CentOS Linux 6.5 64Bit, KVM, Basic Network
Reporter: Thomas Moroder
Since updating to version 4.4.0 of Cloudstack I have noticed problems when
starting new VMs and also System-VMs.
After analyzing the database changes it seems that broadcast_uri and possibly
isolation_uri do not get set and/or do not get set correctly for new VM
instances in the nics table. E.g.:
mysql> select * from nics where instance_id=457;
+-----+--------------------------------------+-------------+-------------------+--------------+---------------+------------+---------+---------------+------------+------+-----------+----------+---------------------------+--------------------------------------+-----------+---------------------+---------------+-------------+-------------+---------+---------------------+---------+-------------+----------+--------------+-------------+
| id | uuid | instance_id | mac_address
| ip4_address | netmask | gateway | ip_type | broadcast_uri |
network_id | mode | state | strategy | reserver_name |
reservation_id | device_id | update_time |
isolation_uri | ip6_address | default_nic | vm_type | created |
removed | ip6_gateway | ip6_cidr | secondary_ip | display_nic |
+-----+--------------------------------------+-------------+-------------------+--------------+---------------+------------+---------+---------------+------------+------+-----------+----------+---------------------------+--------------------------------------+-----------+---------------------+---------------+-------------+-------------+---------+---------------------+---------+-------------+----------+--------------+-------------+
| 668 | ec1d8296-1bb5-4844-8485-00ada7c7a8f9 | 457 | 06:97:ae:00:00:5c
| 1.2.3.4 | 255.255.255.0 | 1.2.3.1 | Ip4 | NULL | 212 |
Dhcp | Allocated | Start | DirectPodBasedNetworkGuru |
e7b3de50-8cf0-43db-a7b2-4cc44d2d13c5 | 0 | 2014-08-22 10:12:17 | NULL
| NULL | 1 | User | 2014-08-22 08:12:09 | NULL |
NULL | NULL | 0 | 1 |
+-----+--------------------------------------+-------------+-------------------+--------------+---------------+------------+---------+---------------+------------+------+-----------+----------+---------------------------+--------------------------------------+-----------+---------------------+---------------+-------------+-------------+---------+---------------------+---------+-------------+----------+--------------+-------------+
With previous versions both broadcast_uri and isolation_uri where set in the
Basic Network mode to "vlan://untagged" and "ec2://untagged".
This causes failures to start the VMs with the cloudstack-agent on the single
hosts giving the following error message:
2014-08-22 02:43:08,457 WARN [cloud.agent.Agent] (agentRequest-Handler-5:null)
Caught:
java.lang.NullPointerException
at
com.cloud.network.Networks$BroadcastDomainType.getSchemeValue(Networks.java:160)
at
com.cloud.network.Networks$BroadcastDomainType.getValue(Networks.java:214)
at
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:96)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:4010)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3766)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3795)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1333)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2014-08-22 10:12:17,301 WARN [cloud.agent.Agent] (agentRequest-Handler-4:null)
Caught:
java.lang.NullPointerException
at
com.cloud.network.Networks$BroadcastDomainType.getSchemeValue(Networks.java:160)
at
com.cloud.network.Networks$BroadcastDomainType.getValue(Networks.java:214)
at
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:96)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:4010)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3766)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3795)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1333)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Also in the GUI the Secondary IP button is missing when looking at the NIC page
of the single instances (this was present in CS 4.3).
If I manually correct the database entries the instances start as planned.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
