[Bug 1329719] Re: cloud-init does not bring up all bridge interfaces created with openvswitch
It seems it's related to this but also: https://bugs.launchpad.net/cloud-init/+bug/1345433 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: [SRU] ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
What's version with patch applied. I want to test. Latest? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: [SRU] ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()
Yes I use openvswitch for everything. I tried to mix br-utils with openvswitch and gave me no goood results. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
I'm still seeing the problem with new kernels. It breaks my ceph installation badly. [1368555.197934] [ cut here ] [1368555.197945] WARNING: CPU: 3 PID: 4400 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [1368555.197947] name 'fs/nfsfs' [1368555.197949] Modules linked in: gspca_ov534 nls_iso8859_1 usb_storage xt_TCPMSS xt_tcpmss arc4 ppp_mppe ppp_async crc_ccitt vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev xt_multiport pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_conntrack ipt_REJECT veth ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph openvswitch gre vxlan ip_tunnel binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) kvm_amd kvm gspca_main videodev wacom serio_raw dm_multipath scsi_dh joydev edac_core edac_mce_amd k10temp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel btusb snd_hda _codec snd_hwdep snd_pcm bluetooth snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore sp5100_tco amd_iommu_v2 i2c_piix4 asus_atk0110 mac_hid parport_pc ppdev lp parport btrfs libcrc32c raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic hid_logitech_dj usbhid hid pata_acpi psmouse pata_atiixp ahci e1000e pata_marvell libahci firewire_ohci ptp firewire_core pps_core r8169 crc_itu_t mii floppy wmi [last unloaded: gspca_ov534] [1368555.198044] CPU: 3 PID: 4400 Comm: kworker/u12:1 Tainted: PW OX 3.13.0-37-generic #64-Ubuntu [1368555.198046] Hardware name: System manufacturer System Product Name/M4A79T Deluxe, BIOS 350305/06/2011 [1368555.198051] Workqueue: netns cleanup_net [1368555.198053] 0009 880119017c80 8171ed09 880119017cc8 [1368555.198057] 880119017cb8 8106773d 0005 [1368555.198060] a06e48a8 880323019ab0 0180 880119017d18 [1368555.198063] Call Trace: [1368555.198070] [8171ed09] dump_stack+0x45/0x56 [1368555.198074] [8106773d] warn_slowpath_common+0x7d/0xa0 [1368555.198079] [810677ac] warn_slowpath_fmt+0x4c/0x50 [1368555.198084] [81229839] remove_proc_entry+0x139/0x1b0 [1368555.198103] [a06c44e2] nfs_fs_proc_net_exit+0x62/0x70 [nfs] [1368555.198115] [a06ca5b2] nfs_net_exit+0x12/0x20 [nfs] [1368555.198118] [8161b409] ops_exit_list.isra.1+0x39/0x60 [1368555.198122] [8161bc90] cleanup_net+0x110/0x250 [1368555.198126] [810839c2] process_one_work+0x182/0x450 [1368555.198130] [810847b1] worker_thread+0x121/0x410 [1368555.198133] [81084690] ? rescuer_thread+0x430/0x430 [1368555.198137] [8108b492] kthread+0xd2/0xf0 [1368555.198140] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [1368555.198143] [8172f77c] ret_from_fork+0x7c/0xb0 [1368555.198146] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 [1368555.198148] ---[ end trace 007872efa0f6c8f7 ]--- [1372797.021226] libceph: osd0 172.16.0.119:6800 socket closed (con state OPEN) [1373904.941772] libceph: osd2 172.16.0.119:6805 socket closed (con state OPEN) [1374022.647670] [ cut here ] [1374022.647691] WARNING: CPU: 1 PID: 17323 at /build/buildd/linux-3.13.0/fs/proc/generic.c:511 remove_proc_entry+0x139/0x1b0() [1374022.647696] name 'fs/nfsfs' [1374022.647700] Modules linked in: gspca_ov534 nls_iso8859_1 usb_storage xt_TCPMSS xt_tcpmss arc4 ppp_mppe ppp_async crc_ccitt vhost_net vhost macvtap macvlan nf_conntrack_ipv6 nf_defrag_ipv6 xt_mac xt_physdev xt_multiport pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) xt_conntrack ipt_REJECT veth ip6table_filter ip6_tables ebtable_nat ebtables xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nbd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm rbd libceph openvswitch gre vxlan ip_tunnel binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt xfs snd_usb_audio snd_usbmidi_lib fglrx(POX) kvm_amd kvm gspca_main videodev wacom serio_raw dm_multipath scsi_dh joydev edac_core edac_mce_amd k10temp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel btusb snd_hda _codec snd_hwdep snd_pcm bluetooth snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
After updating kernel in ubuntu 14.04 I found this again. But this time with kernel panic. ct 12 00:56:30 red-compute kernel: [ 2139.850867] ovs-vswitchd[19280]: segfault at 0 ip 00459340 sp 7fff2d88c3e8 error 4 in ovs-vswitchd[40+133000] Oct 12 00:56:31 red-compute ovs-vswitchd: ovs|00010|daemon(monitor)|ERR|7 crashes: pid 19280 died, killed (Segmentation fault), core dumped, restarting Oct 12 00:57:01 red-compute CRON[19736]: (root) CMD (if [ -x /usr/share/mdadm/checkarray ] [ $(date +%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi) Oct 12 00:58:28 red-compute ovsdb-client: ovs|1|fatal_signal|WARN|terminating with signal 15 (Terminated) Oct 12 00:58:34 red-compute kernel: [ 2264.419340] init: neutron-plugin-openvswitch-agent main process (14411) killed by KILL signal Oct 12 00:58:56 red-compute kernel: [ 2286.159789] INFO: task jbd2/rbd1-8:10184 blocked for more than 120 seconds. Oct 12 00:58:56 red-compute kernel: [ 2286.159802] Tainted: PW OX 3.13.0-37-generic #64-Ubuntu Oct 12 00:58:56 red-compute kernel: [ 2286.159807] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 12 00:58:56 red-compute kernel: [ 2286.159812] jbd2/rbd1-8 D 88032fc54480 0 10184 2 0x Oct 12 00:58:56 red-compute kernel: [ 2286.159822] 88029baadbc8 0046 8802d1ac8000 88029baadfd8 Oct 12 00:58:56 red-compute kernel: [ 2286.159832] 00014480 00014480 8802d1ac8000 88032fc54d18 Oct 12 00:58:56 red-compute kernel: [ 2286.159840] 88032ffb1020 0002 811ee820 88029baadc40 Oct 12 00:58:56 red-compute kernel: [ 2286.159847] Call Trace: Oct 12 00:58:56 red-compute kernel: [ 2286.159864] [811ee820] ? generic_block_bmap+0x50/0x50 Oct 12 00:58:56 red-compute kernel: [ 2286.159875] [8172344d] io_schedule+0x9d/0x140 Oct 12 00:58:56 red-compute kernel: [ 2286.159884] [811ee82e] sleep_on_buffer+0xe/0x20 Oct 12 00:58:56 red-compute kernel: [ 2286.159892] [817238d2] __wait_on_bit+0x62/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.159899] [811ee820] ? generic_block_bmap+0x50/0x50 Oct 12 00:58:56 red-compute kernel: [ 2286.159907] [81723977] out_of_line_wait_on_bit+0x77/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.159916] [810ab010] ? autoremove_wake_function+0x40/0x40 Oct 12 00:58:56 red-compute kernel: [ 2286.159924] [811efb5a] __wait_on_buffer+0x2a/0x30 Oct 12 00:58:56 red-compute kernel: [ 2286.159933] [812888f0] jbd2_journal_commit_transaction+0xee0/0x1a70 Oct 12 00:58:56 red-compute kernel: [ 2286.159943] [810754ff] ? try_to_del_timer_sync+0x4f/0x70 Oct 12 00:58:56 red-compute kernel: [ 2286.159951] [8128d4ad] kjournald2+0xbd/0x250 Oct 12 00:58:56 red-compute kernel: [ 2286.159959] [810aafd0] ? prepare_to_wait_event+0x100/0x100 Oct 12 00:58:56 red-compute kernel: [ 2286.159967] [8128d3f0] ? commit_timeout+0x10/0x10 Oct 12 00:58:56 red-compute kernel: [ 2286.159974] [8108b492] kthread+0xd2/0xf0 Oct 12 00:58:56 red-compute kernel: [ 2286.159981] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 Oct 12 00:58:56 red-compute kernel: [ 2286.159988] [8172f77c] ret_from_fork+0x7c/0xb0 Oct 12 00:58:56 red-compute kernel: [ 2286.159995] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 Oct 12 00:58:56 red-compute kernel: [ 2286.160016] INFO: task init:10493 blocked for more than 120 seconds. Oct 12 00:58:56 red-compute kernel: [ 2286.160022] Tainted: PW OX 3.13.0-37-generic #64-Ubuntu Oct 12 00:58:56 red-compute kernel: [ 2286.160025] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 12 00:58:56 red-compute kernel: [ 2286.160028] initD 88032fc94480 0 10493 10443 0x Oct 12 00:58:56 red-compute kernel: [ 2286.160036] 8802eae2da28 0082 8802b37a3000 8802eae2dfd8 Oct 12 00:58:56 red-compute kernel: [ 2286.160043] 00014480 00014480 8802b37a3000 88032fc94d18 Oct 12 00:58:56 red-compute kernel: [ 2286.160050] 88032ffb7908 0002 812851c0 8802eae2daa0 Oct 12 00:58:56 red-compute kernel: [ 2286.160057] Call Trace: Oct 12 00:58:56 red-compute kernel: [ 2286.160066] [812851c0] ? start_this_handle+0x590/0x590 Oct 12 00:58:56 red-compute kernel: [ 2286.160074] [8172344d] io_schedule+0x9d/0x140 Oct 12 00:58:56 red-compute kernel: [ 2286.160081] [812851ce] sleep_on_shadow_bh+0xe/0x20 Oct 12 00:58:56 red-compute kernel: [ 2286.160088] [817238d2] __wait_on_bit+0x62/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.160095] [812851c0] ? start_this_handle+0x590/0x590 Oct 12 00:58:56 red-compute kernel: [ 2286.160103] [81723977] out_of_line_wait_on_bit+0x77/0x90 Oct 12 00:58:56 red-compute kernel: [
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
ovs-vsctl (Open vSwitch) 2.0.2 Compiled Aug 15 2014 14:31:02 I did: apport-collect 1336555 Package openvswitch not installed and no hook available, ignoring But no luck. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
Hi Nooope, I had to restart the computer and I think I don't have it. It didn't hapened for a while. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1329719] Re: cloud-init does not bring up all bridge interfaces created with openvswitch
This is a problem when installing metal with mass. This is related to this https://bugs.launchpad.net/juju-core/+bug/1271144 but not resolved. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
Hi, Is there a way I can get a core from this process? I suppose that leaving ulimit -c unlimited is not enough. And I don't know where it will be left. But I can try. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
To make it happen more ofter, is needed a lot of transfer connections through the network node. I have GB eth with two interfaces on each host to make it happen. But only 4-5 vmachines on the cloud. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336555] [NEW] ovs-vswitchd segfault every 2 days
Public bug reported: Hi I find that every 2 days or so I loose part of my cluster. It seems that openvswitch is crashing... The only message left on syslog is as follows: syslog:Jul 1 22:52:32 blue-compute kernel: [530482.190688] ovs- vswitchd[1935]: segfault at 0 ip 00459110 sp 7fff85804758 error 4 in ovs-vswitchd[40+133000] And this is the last message. I'm unable to reboot gracefully. I have to reset. (This can be because ceph not giving up also). And I can see a lot of traffic going around in the network. There so much traffic that some lowend routers/switches fail. Can be because another problem (machines stalled because the ovs fault and others trying to connect. Maybe it fails because much traffic). But I tell this for completeness. Now some info: Linux version 3.13.0-30-generic (buildd@allspice) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #54-Ubu ntu SMP Mon Jun 9 22:45:01 UTC 2014 (Ubuntu 3.13.0-30.54-generic 3.13.11.2) vendor_id : AuthenticAMD cpu family : 16 model : 4 model name : AMD Phenom(tm) II X4 810 Processor Ubuntu 14.04 LTS (server). ovs-vsctl --version ovs-vsctl (Open vSwitch) 2.0.1 Compiled Feb 23 2014 14:42:32 I can attach full logs but I think there's nothing useful because only one line referring the problem. NOTE: restarting ovs does not solve the problem. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
I will open another bug... sorry -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
root@red-compute:~# ovs-vsctl show 8d08d8e4-49f2-4243-b1db-7641984a8530 Bridge br-ex Port br-ex Interface br-ex type: internal Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal ovs_version: 2.0.1 root@red-compute:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down auto eth1 iface eth1 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down auto br-int iface br-int inet dhcp And when I boot up, cloudinit does not find the interfaces so no network is up. I have to take an screenshot of the issue. The problem is that rbd storage is not boot up because cloudinit does not find the interfaces to connect to the intranet (because it's a bridge), and all the system becomes a nightmare. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1329719] [NEW] cloud-init does not bring up all bridge interfaces created with openvswitch
Public bug reported: Hi, In my systems (all of them where I have openstack), I found that cloud- init does not perform well. Mainly because the bridges I have were created with ovs. Since they are not ready at boot time it seems that the system got stalled for a few mins. And after boot not all services recover. For example rbdmap is not called again after the net is up. It may be the order where the things are done. Or maybe something worse. The problem is that cloud-init stalls for 2 mins on boot. RBD doesn't run because cloud-init starts in nonet mode. And the whole system becomes broken. It's curious that ceph-osd are re-run after net is up. So some scripts are relaunched. In fact two times. So they start to work well. But some others no. root@red-compute:~# ovs-vsctl show 8d08d8e4-49f2-4243-b1db-7641984a8530 Bridge br-ex Port br-ex Interface br-ex type: internal Bridge br-int Port eth1 Interface eth1 Port br-int Interface br-int type: internal ovs_version: 2.0.1 root@red-compute:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down auto eth1 iface eth1 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down auto br-int iface br-int inet dhcp And when I boot up, cloudinit does not find the interfaces so no network is up. I have to take an screenshot of the issue. The problem is that rbd storage is not boot up because cloudinit does not find the interfaces to connect to the intranet (because it's a bridge), and all the system becomes a nightmare. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1329719 Title: cloud-init does not bring up all bridge interfaces created with openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1329719/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084028] Re: openvswitch based interfaces not started in time during boot
You should reopen it since it happens in trusty tahr to me. Someone can try it in this version of ubuntu, please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1084028 Title: openvswitch based interfaces not started in time during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
I have to clarify that I'm not sure that this has something to do with KVM, QEMU and the like. I think is more a problem of the linux bridge driver since It fails even if you don't have any vm running. Yes, it takes more time to fail but this can be because not enough traffic to make it fail. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
I've found this problem in my saucy installation. I just opened a bug cause I'm not sure if it's related. https://bugs.launchpad.net/ubuntu/+source/core-network/+bug/1255516 My problem is actually worse since host machine cannot get access to other machines on the network. Not even virtual machines but hardware machines, routers, NAS, and so on. The only way to recover from this situation is to ifdown ifup the bridge. Then it recovers until it happens again. When I remove the bridge no problems. But I was not able to test it since I need the bridge up. I'm investigating macvtap instead of bridge... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003656] Re: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot
I have the same problem with quantal (image installed by MAAS) I've just created a bridge br0 in the interfaces file and now the system does not boot. it seems br0 is not going up if I do a brcrl addbr br0 everything works. I have not the bonding one, but seems to be the same error. The output of initctrl list shows: upstart-udev-bridge is runing upstart-socket-bridge is running cloud-init is running... it seems that cloud-init needs the interface up to continue but it never goes up... Also, I've modified the /etc/network/if-pre.up.d/bridge to show what interfaces are up when the system stalls: It shows that $IF_BRIDGE_PORTS goes empty, and is executed twice... It should have the bridge port br0 in my case... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1003656] Re: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot
I added a rule in udev to bring up the port directly with brctl addbr br0 and now everything works. But I don't know the cause. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073287] [NEW] tgt-admin fails to read configuration
Public bug reported: Hello, It seems that configuration fails to read files inside the /var/lib/maas/ephemeral/tgt.conf.d/ directory. I was looking around and seems it's a globbing problem of the python library. I updated config to include the exact *.conf files and with this change everything works. I installed the MAAS server from the quantal distribution. Linux red-controller 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:32:08 UTC 2012 i686 i686 i686 GNU/Linux Any help on this? -- root@red-controller:~# tgt-admin -e Config::General The file /var/lib/maas/ephemeral/tgt.conf.d/*.conf does not exist within ConfigPath: /etc/tgt! at /usr/sbin/tgt-admin line 172 It also failed when updating images: sudo maas-import-pxe-files ... 2012-10-30 19:01:13 (496 KB/s) - “/var/lib/maas/ephemeral/.working/maas- import-ephemerals.w1pEFy/quantal/amd64/dist.tar.gz” guardado [291203883/291203883] Target iqn.2004-05.com.ubuntu:maas:maas-quantal-12.10-amd64-ephemeral-20121017 is currently not configured and does not exist in the config file - can't continue! failed tgt-admin add for maas-quantal-12.10-amd64-ephemeral-20121017 This bug is reported here: https://bugs.launchpad.net/maas/+bug/1073276 ** Affects: tgt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1073287 Title: tgt-admin fails to read configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1073287/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1067929] Re: maas-region-celeryd connects to the wrong queue.
I can say that for me does not disapear. And the PXE clients boots to a provisioning image and then shuts down automatically. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1067929 Title: maas-region-celeryd connects to the wrong queue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1067929/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
