Status: New
Owner: ----

New issue 591 by [email protected]: Problem Network - New machines clients
http://code.google.com/p/ganeti/issues/detail?id=591

What software version are you running? Please provide the output of "gnt-
cluster --version" and "gnt-cluster version".

What distribution are you using?

root@pepito:~# gnt-cluster --version
gnt-cluster (ganeti v2.5.1) 2.5.1

root@sk2:~# gnt-cluster version
Software version: 2.5.1
Internode protocol: 2050000
Configuration format: 2050000
OS api version: 20
Export interface: 0



What steps will reproduce the problem?

1. First we create a VM Client with this command:

gnt-instance add -s 5G -o debootstrap+debianstable --net 0:link=eth1 -t drbd -B memory=512 -H xen-hvm -n pepito1.bcom.es:pepito2.bcom.es clientmachine

2. We start a machine client with this command:

gnt-instance start -H boot_order=d,cdrom_image_path=/mnt/debian-7.1.0-amd64-netinst.iso clientmachine


3. The boot cd is a debian but with a ubuntu versión 12.04 we have the same problem with a network.

When we need configure a network, we get a message on screen saying that the network is not available on the machine.
We've tried several linux distributions, in both gannetti nodes.

But only this happening with new machines we create, with the old clients created works correctly.


What is the expected output? What do you see instead?

In a /var/log/syslog we have this errors


[20670919.780310] eth1: port 12(tap66.0) entering forwarding state
[20670919.780323] eth1: port 12(tap66.0) entering forwarding state
[20670929.897751] tap66.0: no IPv6 routers present
[20671994.586537] eth1: port 12(tap66.0) entering forwarding state
[20671994.590392] eth1: port 12(tap66.0) entering disabled state
[20671994.590886] device tap66.0 left promiscuous mode
[20671994.590890] eth1: port 12(tap66.0) entering disabled state
[20671995.893553] xen-blkback:ring-ref 8, event-channel 11, protocol 1 (x86_64-abi)
[20671995.967431] eth1: port 11(vif66.0) entering disabled state
[20671995.967930] device vif66.0 left promiscuous mode
[20671995.967934] eth1: port 11(vif66.0) entering disabled state
[20671996.152519] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [20671996.152526] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [20671996.156642] xt_physdev: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore.



Please provide any additional information below.


root@pepito2:~# brctl show
bridge name     bridge id               STP enabled     interfaces
eth1            8000.464080fd35aa       no              peth1
                                                        tap11.0
                                                        tap14.0
                                                        vif11.0
                                                        vif14.0
                                                        vif47.0


root@pepito2:~# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif59.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif59.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif55.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif55.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif54.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif54.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif47.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif47.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif34.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif34.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif20.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif20.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif16.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif16.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif15.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif15.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif14.1 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif14.1 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif14.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif14.0 ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED PHYSDEV match --physdev-out vif11.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif11.0

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination



cat /etc/network/interficies

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 80.34.95.18
netmask 255.255.255.0
gateway 80.34.95.10

auto eth1
iface eth1 inet static
address 172.26.0.2
netmask 255.255.255.0


auto eth2
iface eth2 inet static
address 172.26.2.102
netmask 255.255.255.0






--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply via email to