Chandan Purushothama created CLOUDSTACK-152:
-----------------------------------------------

             Summary: Routes on the User VM are programmed incorrectly on a VM 
present on both an Isolated and Shared Guest Networks
                 Key: CLOUDSTACK-152
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-152
             Project: CloudStack
          Issue Type: Bug
          Components: Management Server
    Affects Versions: pre-4.0.0
            Reporter: Chandan Purushothama
             Fix For: pre-4.0.0



==================
Steps to Reproduce:
==================

1. As the Admin of ROOT domain, Create a shared guest network using the 
DefaultNetworkOfferingforSharedNetworks.
2. Login as a Regular User. Create an isolated guest network using the 
"DefaultNetworkOfferingwithSourceNATService"
3. Register a CentOS6.3_x86_64 ISO
4. Deploy a VM on the Isolated and Shared Guest Network using the ISO. Make 
sure that the Isolated Guest Network is chosen as the default Guest Network.
5. View the VM's Console. Observe that the only IP Address present on the VM is 
the loopback address.
6. Edit the two ifcfg-ethx files present under /etc/sysconfig/network-scripts/. 
Set the ONBOOT parameter to yes.
7. Reboot the VM or restart the network service.
8. Observe the routes on the VM after the Reboot.

==========
Observations:
==========

[root@B-regnet-shdnet-iso-vm-4 ~]# history
    1  ifconfig
    2  reboot
    3  history
[root@B-regnet-shdnet-iso-vm-4 ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 02:00:47:BD:00:06
          inet addr:10.1.1.48  Bcast:10.1.1.255  Mask:255.255.255.0
          inet6 addr: fe80::47ff:febd:6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:379 (379.0 b)  TX bytes:1116 (1.0 KiB)
          Interrupt:165

eth1      Link encap:Ethernet  HWaddr 06:74:B6:00:00:3A
          inet addr:10.223.137.78  Bcast:10.223.137.127  Mask:255.255.255.192
          inet6 addr: fe80::474:b6ff:fe00:3a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:108 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9425 (9.2 KiB)  TX bytes:10289 (10.0 KiB)
          Interrupt:164

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


**Observe that except the second and the third route all the remaining routes 
are wrong. Notice that 10.1.1.48 is on eth0 while 10.223.137.78 is on eth1**

[root@B-regnet-shdnet-iso-vm-4 ~]# ip route
10.1.1.1 dev eth1  scope link
10.223.137.64/26 dev eth1  proto kernel  scope link  src 10.223.137.78
10.1.1.0/24 dev eth0  proto kernel  scope link  src 10.1.1.48
169.254.0.0/16 dev eth0  scope link  metric 1002
169.254.0.0/16 dev eth1  scope link  metric 1003
default via 10.1.1.1 dev eth1

[root@B-regnet-shdnet-iso-vm-4 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
BOOTPROTO="dhcp"
HWADDR="02:00:47:BD:00:06"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
UUID="b74145e6-eaf5-4b53-b19a-9a4051fa4a75"

[root@B-regnet-shdnet-iso-vm-4 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE="eth1"
BOOTPROTO="dhcp"
HWADDR="06:74:B6:00:00:3A"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE="Ethernet"
UUID="a5afb535-0eb0-4196-a324-87aec613f38a"

[root@B-regnet-shdnet-iso-vm-4 ~]# cat /etc/redhat-release
CentOS release 6.3 (Final)

=======
Git Info:
=======

Git Revision: 54f9af1695bc359b02e9fc906b3b335cc0bfec41
Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to