similar to: Bug#663352: xcp-networkd: fails to install

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Thu, 27 Dec 2012 13:05:06 +0000 Source: xen-api Binary: xcp-xapi python-xenapi xcp-squeezed xcp-v6d libxenapi-ocaml-dev xcp-xapi-debug xcp-xe xcp-networkd Architecture: source amd64 all Version: 1.3.2-14 Distribution: unstable Urgency: low Maintainer: Pkg Xen <pkg-xen-devel at lists.alioth.debian.org> Changed-By:

Accepted: libxenapi-ocaml-dev_1.3.2-9_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-9_amd64.deb python-xenapi_1.3.2-9_all.deb to main/x/xen-api/python-xenapi_1.3.2-9_all.deb xcp-networkd_1.3.2-9_amd64.deb to main/x/xen-api/xcp-networkd_1.3.2-9_amd64.deb xcp-squeezed_1.3.2-9_amd64.deb to main/x/xen-api/xcp-squeezed_1.3.2-9_amd64.deb xcp-v6d_1.3.2-9_amd64.deb to

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 03 Nov 2012 19:12:36 +0000 Source: xen-api Binary: xcp-xapi python-xenapi xcp-squeezed xcp-v6d libxenapi-ocaml-dev xcp-xapi-debug xcp-xe xcp-networkd Architecture: source amd64 all Version: 1.3.2-13 Distribution: unstable Urgency: low Maintainer: Pkg Xen <pkg-xen-devel at lists.alioth.debian.org> Changed-By:

Package: xen-utils-common Version: 4.1.2-1 Severity: important User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts

Package: xcp-guest-templates Version: 0.1-4 Severity: important User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts

libxenapi-ocaml-dev_1.3.2-2_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-2_amd64.deb python-xenapi_1.3.2-2_all.deb to main/x/xen-api/python-xenapi_1.3.2-2_all.deb (new) xcp-networkd_1.3.2-2_amd64.deb extra admin daemon to manage network configuration for xcp-xapi The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, with

Package: blktap-dkms Version: 2.0.91-1 Severity: important User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean

Package: xcp-networkd Version: 1.3.2-11 Severity: normal Given that openvswitch is one of the networking modes, it should be in the Recommends: than being in the Depends: -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64

Hi I install the xcp from the http://wiki.xen.org/wiki/XAPI_on_Ubuntu. But I got this error while configuring xcp-xapi: xcp-networkd (1.3.2-1ubuntu1~oneiric1) wird eingerichtet ... Starting the XCP networking daemon: .............................. * failed to start xcp-networkd. invoke-rc.d: initscript xcp-networkd, action "start" failed. when I comment the

On 4 Oct 2017 6:51 pm, <m.roth at 5-cent.us> wrote: James Hogarth wrote: > On 4 Oct 2017 3:13 pm, "Kenneth Porter" <shiva at sewingwitch.com> wrote: > > On 10/3/2017 8:14 PM, Phil Manuel wrote: > >> systemd-networkd doesn't use those files at all. >> >> If you look at the appropriate ifcfg files eg >>

Package: xcp-xapi Version: 1.3.2-6 Severity: important Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present. root at debian:~# aptitude install xcp-xapi The following NEW packages will be installed: blktap-dkms{a} blktap-utils{a}

Okay sorry about that. No Idea if it will work in CentOS, but is it worth trying to turn off ipv6 for a single nic as as outlined at https://coreos.com/os/docs/latest/network-config-with-networkd.html ? On Wed, Oct 4, 2017 at 4:14 PM, Phil Manuel <phil at zomojo.com> wrote: > Hi Clint, > > systemd-networkd doesn't use those files at all. > > > > On Wed, 4 Oct

On 4 Oct 2017 3:13 pm, "Kenneth Porter" <shiva at sewingwitch.com> wrote: On 10/3/2017 8:14 PM, Phil Manuel wrote: > systemd-networkd doesn't use those files at all. > > If you look at the appropriate ifcfg files eg > /etc/sysconfig/network-scripts/ifcfg-em1 do you see IPV6_FAILURE_FATAL=no > ? > Where does systemd-networkd store its settings, then?

On 10/3/2017 8:14 PM, Phil Manuel wrote: > systemd-networkd doesn't use those files at all. > > If you look at the appropriate ifcfg files eg > /etc/sysconfig/network-scripts/ifcfg-em1 do you see IPV6_FAILURE_FATAL=no ? Where does systemd-networkd store its settings, then?

James Hogarth wrote: > On 4 Oct 2017 3:13 pm, "Kenneth Porter" <shiva at sewingwitch.com> wrote: > > On 10/3/2017 8:14 PM, Phil Manuel wrote: > >> systemd-networkd doesn't use those files at all. >> >> If you look at the appropriate ifcfg files eg >> /etc/sysconfig/network-scripts/ifcfg-em1 do you see >> IPV6_FAILURE_FATAL=no >> ?

On 10/04/2017 01:40 PM, James Hogarth wrote: > Nope. And find /etc/systemd -name network gives zilch. Yes, systemd-networkd does store its configuration in /etc/systemd/network, but the directory isn't created by the RPM; you need to create it yourself. As noted, systemd-networkd is in the RHEL extras (or somesuch) repo, so it isn't supported by Red Hat on RHEL. It's basically

Hi Clint, systemd-networkd doesn't use those files at all. On Wed, 4 Oct 2017 at 13:55 Clint Dilks <clintd at scms.waikato.ac.nz> wrote: > On Wed, Oct 4, 2017 at 3:46 PM, Phil Manuel <phil at zomojo.com> wrote: > > > Hi, > > > > If I disable ipv6 via the kernel command line, ipv6.disable=1, then > > systemd-networkd fails to bring up any

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was debian at abeckmann.de). > usertags 669005 piuparts Bug#669005: uninstallable on sid (might just need require a rebuild) There were no usertags set. Usertags are now: piuparts. > affects 669005 + shogun-python-static shogun-python-modular

On Wed, Oct 4, 2017 at 3:46 PM, Phil Manuel <phil at zomojo.com> wrote: > Hi, > > If I disable ipv6 via the kernel command line, ipv6.disable=1, then > systemd-networkd fails to bring up any interfaces. > > Removing the option and networking works as expected. > Hi, If you look at the appropriate ifcfg files eg /etc/sysconfig/network-scripts/ifcfg-em1 do you see