[
https://issues.apache.org/jira/browse/CLOUDSTACK-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568508#comment-13568508
]
Marcus Sorensen commented on CLOUDSTACK-1115:
---------------------------------------------
I am so far unable to duplicate with the 4.0.1 release candidate. He says he is
running network-refactor branch, but also lists 4.0.2 as to fix for. So either
it's in master or the network-refactor stuff.
create shared net 1 as 10.50.0.0/24, vlan id 300, defaultsharednetworkoffering
create shared net 2 as 10.60.0.0/24, vlan id 301, defaultsharednetworkoffering
create VM attached to both shared net 1 and shared net 2, with default on
shared net 1
log into vm template. I see that eth0 is shared net 1, has ip of 10.50.0.13,
default router of 10.50.0.1. Eth1 has no ip because it has no config telling it
to use dhcp. I run 'dhclient eth1', and it gets 10.60.0.14, but default gateway
stays as 10.50.0.1. Good news.
tell eth1 to use dhcp, reboot. get same addresses/gateway.
assign ip address of 10.50.0.1/24 on KVM host's cloudVirBr300, so I have
something to test connectivity to vm with. attempt ssh login to 10.50.0.13 from
kvm host. success
assign ip address of 10.60.0.1/24 on KVM host's cloudVirBr301, so I have
something to test connectivity to vm with. attempt ssh login to 10.60.0.14 from
kvm host. success
I'll attempt with master later, but I think we need some more info on the
specific test setup, and for example is this network that is default for the VM
verified working with another single attached vm?
> In multiple shared network unable to login with default nic - KVM
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-1115
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1115
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.1.0
> Environment: KVM - Advanced zone
> This build from network-re factor branch
> Reporter: Rayees Namathponnan
> Assignee: Sheng Yang
> Fix For: 4.0.2, 4.1.0
>
>
> Step 1 Create advanced zone in KVM
> Step 2 create a user account
> Step 3 Create two shared Networks (shared 1 and shared 2) (scope=ALL,
> different IP ranges)
> Step 4 deployVirtualMachine in both the above networkids within the user
> account
> Make sure shared 1 default one
> Step 5 Go to - > Instances -> Select newly created VM -> NIC tab
> Step 6 Get the ip address of your default NIC and login
> Expected Result
> You should be able login the default nic's IP address
> Actual result
> Unable to login with default nic's IP address, but i can login with sec nic's
> ip address
--
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
