Bug#695221: xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet, netmask
Hello All, This bug has been fixed upstream, for the fix see: https://github.com/xen-org/xen-api/commit/abed1d6321a9f56822e5c7a5ce3b183e25c90bb9 If this could be applied to a patch that would be great. Cheers, Harrie -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695221: [Pkg-xen-devel] Bug#695221: xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask
On 12/05/2012 11:38 PM, Marc Lebel wrote: Package: xcp-xapi Version: 1.3.2-13 Severity: critical Hi, Thanks for this bug report. But in the future, could you please check the definition of the bugs seriousness? Reportbug says: critical: makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. This doesn't match *at all* your bug report. And I get network access this way. The problem is that my network isn't configured like this and I don't want to change it just to accomodate this setup. I also tried with other subnetmasks such as /25 /26 /27 ... and none of them worked except for /24. Any help is appreciated! This is likely to be a missing feature than a bug, so I'm downgrading this to severity: wishlist. Note that severity has very little to do with how much someone wants to fix an issue. In this case, you'll have to ask upstream about it, and not the package maintainer. Probably, asking in the xen-api list would be a good idea, if you want to see progress on this. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695221: xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask
Package: xcp-xapi Version: 1.3.2-13 Severity: critical I get this bug when installing XCP and configuring the network portion of it. When I issue the following command: xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.240 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3 My network interface looks like this (Broken): eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1942287 errors:0 dropped:0 overruns:0 frame:0 TX packets:1651769 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1808351392 (1.6 GiB) TX bytes:1811952536 (1.6 GiB) Interrupt:21 Base address:0x4000 xenbr2Link encap:Ethernet HWaddr 00:50:ec:24:c7:43 inet addr:10.0.0.10 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1941758 errors:0 dropped:9 overruns:0 frame:0 TX packets:1651725 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1780637266 (1.6 GiB) TX bytes:1809322340 (1.6 GiB) I lose total network connectivity. And this is bad since I usually configure this remotely. The only way I could get it working was with the following command: xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.0 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3 And my network interface looks like this (working): eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1945714 errors:0 dropped:0 overruns:0 frame:0 TX packets:1651770 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1808603886 (1.6 GiB) TX bytes:1811952596 (1.6 GiB) Interrupt:21 Base address:0x4000 xenbr2Link encap:Ethernet HWaddr 00:50:ec:24:c7:43 inet addr:10.0.0.10 Bcast:0.0.0.0 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1945174 errors:0 dropped:9 overruns:0 frame:0 TX packets:1651725 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1780827498 (1.6 GiB) TX bytes:1809322340 (1.6 GiB) And I get network access this way. The problem is that my network isn't configured like this and I don't want to change it just to accomodate this setup. I also tried with other subnetmasks such as /25 /26 /27 ... and none of them worked except for /24. Any help is appreciated! Marc -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xcp-xapi depends on: ii hwdata 0.233-1 ii libc6 2.13-37 ii libpam0g 1.1.3-7.1 ii libuuid1 2.20.1-5.2 ii libvhd02.0.90-1 ii libxen-4.1 4.1.3-4 ii libxenstore3.0 4.1.3-4 ii lsb-base 4.1+Debian8 ii pciutils 1:3.1.9-5 ii python 2.7.3~rc2-1 ii python-xenapi 1.3.2-13 ii stunnel4 [stunnel] 3:4.53-1 ii xcp-eliloader 0.1-4 ii xcp-fe 0.5.2-3+b1 ii xcp-networkd 1.3.2-13 ii xcp-squeezed 1.3.2-13 ii xcp-storage-managers 0.1.1-3 ii xcp-v6d1.3.2-13 ii xcp-xe 1.3.2-13 ii xen-hypervisor-4.1-amd64 [xen-hypervisor-4.1] 4.1.3-4 ii xen-utils-4.1 4.1.3-4 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages xcp-xapi recommends: ii cifs-utils 2:5.5-1 ii xcp-guest-templates 0.1-4 ii xcp-vncterm 0.1-2 xcp-xapi suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695221: xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask
control: severity -1 normal Downgrading the severity since this not a severe issue and its easy enough to workaround. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
