Re: [Bug 1645644] Re: ntp is not restarted after writing /etc/ntp.conf by cloud-init

On Fri, Jan 6, 2017 at 9:28 AM, Nobuto Murata wrote: > @Ryan, > I used MAAS 2.1 since it puts its IP address as a local NTP server into > the vendor data for MAAS nodes by default. I believe just deploying one > mode using MAAS 2.1 reproduces the problem. > OK, thanks,

[Bug 1645644] Re: ntp is not restarted after writing /etc/ntp.conf by cloud-init

What ntp configuration do you provide in your vendor data? ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is

Re: [Bug 1645644] Re: ntp not using expected servers

On Fri, Jan 6, 2017 at 10:13 AM, Nobuto Murata wrote: > I don't have MAAS env right now at hand. But as I attached the log and > the code above. /etc/ntp.conf and vendor data were correct. Just > restarting the daemon by cloud-init was missing if I understand it >

[Bug 1675576] [NEW] cloud-init netplan renderer might need to delete baked in configuration

Public bug reported: 1. Zesty 2. 0.7.9-68-gef18b8ac-0ubuntu1 3. cloud-init with network configuration rendering to netplan config has exclusive control over networkd configuration 4. On images with existing netplan configuration (UC16 has an /etc/netplan/00-snapd-config.yaml); netplan generator

[Bug 1673860] Re: systemd-resolved unit should run Before=network-online.target

** Description changed: + === Begin SRU Template === + [Impact] + + For releases using systemd-resolved (yakkety and zesty); the unit + configuration does not require that the service be active before + allowing systemd to reach 'network-online.target' which is a special + target used to allow

[Bug 1663725] Re: root on raid device doesn't get /dev/disk/by-id/md-{name, uuid} symlinks after boot

> Are all of those included in the initramfs as well? (check with e.g. lsinitramfs) No; but they don't need to be; it's purely helpful symlinks to provide a "name" for a device that's independent of the disk (/dev/disk/by- dname/database -> /dev/vdc). drwxr-xr-x 2 root root0

[Bug 1671951] Re: networkd should allow configuring IPV6 MTU

This also needs some discussion w.r.t how to handle IPV6-only devices; namely if you want to set the IPV6 MTU to something higher than the underlying device's current setting then the device MTU would need to be raised as well. That needs to be implemented and added to the patch. -- You

[Bug 1663725] Re: root on raid device doesn't get /dev/disk/by-id/md-{name, uuid} symlinks after boot

** Attachment added: "curtin-dname-rules.tgz" https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1663725/+attachment/4848887/+files/curtin-dname-rules.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1675185] [NEW] cannot disable apt_configure via cloud-config

Public bug reported: 1. Zesty 2. 0.7.9-68-gef18b8ac-0ubuntu1 3. Boot instance with cloud-config like: #cloud-config apt_configure_enabled: False Or #cloud-config apt_configure: enabled: False cloud-init would not run the apt_configure config module 4. cloud-init cc_apt_configure.py does

[Bug 1673860] Re: systemd-resolved unit should run Before=network-online.target

I just tested the zesty-proposed version and it works as expected. % lxc launch ubuntu-daily:zesty z1 Creating z1 Starting z1 # confirm current version of systemd % lxc exec z1 -- apt-cache policy systemd systemd: Installed: 232-19 Candidate: 232-19 Version table: *** 232-19 500

Re: [Bug 1673860] Re: systemd-resolved unit should run Before=network-online.target

Working it now, sorry for the delay On Thu, Mar 23, 2017 at 1:07 PM, Brian Murray wrote: > Missing SRU information regarding Impact, Test Case, Regression > Potential. > > -- > You received this bug notification because you are subscribed to the bug > report. >

Re: [Bug 1669860] Re: cloud-init attempts to rename bonds

On Fri, Mar 17, 2017 at 8:59 PM, Scott Moser wrote: > I expected to be able to recreate this in a lxc container like below, > but that didnt show any errors at all in /var/log/cloud-init.log. > Try using non-knames, like interface0 and interface1. > > #!/bin/sh > name=$1 >

[Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

I've moved the systemd-resolved issue for unit ordering out of this bug/SRU into a new one so we can finish out this SRU and handle this last change to systemd-resolved separately. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860 -- You received this bug notification because you

[Bug 1673860] [NEW] systemd-resolved unit should run Before=network-online.target

Public bug reported: 1) Xenial, Yakkety and Zesty; (Xenial is affected if you're using networkd and resolved, but it's not the default) 2) 229-4ubuntu16, 231-9ubuntu3, 232-18ubuntu1 respectively to (1) 3) DNS resolution should be available once systemd has reached 'network-online.target'

[Bug 1669860] Re: cloud-init attempts to rename bonds

Fixed up network config for bond testing. ** Attachment added: "bond-rename-launch.sh" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1669860/+attachment/4841194/+files/bond-rename-launch.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is

Re: [Bug 1642652] Re: Install progress should display curtin reporter output

On Wed, Mar 15, 2017 at 8:05 PM, Michael Hudson-Doyle < michael.hudson...@canonical.com> wrote: > Is it easy to filter these out of the curtin log? It would be pretty > easy to do this from the subiquity side now. > curtin reporting[1] will return events as they happen with timestamps; However,

[Bug 1669860] Re: cloud-init attempts to rename bonds

Download a zesty cloud image and then create a qcow2 overlay: qemu-img create -b zesty-server-cloudimg-amd64.img -f qcow2 bond- rename.qcow2 Then invoke the script like: ./bond-rename-launch.sh ** Attachment added: "bond-rename-launch.sh"

[Bug 1669860] Re: cloud-init attempts to rename bonds

Getting this to trip is somewhat tricky and racy due to how fast/slow the bond is able to come up. However, if the bond is up before cloud- init.service runs it's net.apply_network_config_names() then we see the following: >>> r = net._get_current_rename_info(check_downable=True) >>> r {False:

[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

) DefaultDependencies=no -Before=networking.service +Before=network-pre.target +Wants=network-pre.target ** Changed in: resolvconf (Ubuntu) Status: Confirmed => Invalid ** Changed in: resolvconf (Ubuntu) Assignee: Ryan Harper (raharper) => (unassigned) -- You received th

[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

@Mercury Hi, please note that the change I've made is *only* against the resolvconf task; as you say and document the issue (and potential fix) is against dnsmasq; ergo there is no need for a resolvconf patch/change. You mention: "and resolvconf was not properly tracking how interfaces were

[Bug 1682456] Re: md devices may leave remnants in /sys/class/block after removal

I tested with the updated kernel and unfortunately, it does not resolve the issue. Since these are recently uncovered issues upstream, could you cherry pick those against the Zesty kernel? Once we know it's resolved in the latest kernel we can track down what changes needed for Xenial. -- You

[Bug 1682456] [NEW] md devices may leave remnants in /sys/class/block after removal

Public bug reported: 1. root@x1:~# cat /proc/version_signature Ubuntu 4.4.0-72.93-generic 4.4.49 2. attached 3. # lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 4. # apt-cache policy linux-image-`uname -r` linux-image-4.4.0-72-generic: Installed: 4.4.0-72.93

[Bug 1684092] Re: cloud-init in xenial generates bond configs that do not appear to work

Also, it's somewhat frustrating to see the physical devices appear sooner in this run vs. the failed runs we've seen; That is, the runtime error is different then the bond0 timeout when the slaves didn't bother showing up (ie, they somehow missed an ifup call). -- You received this bug

[Bug 1684092] Re: cloud-init in xenial generates bond configs that do not appear to work

RuntimeError: duplicate mac found! both 'bond0.101' and 'ens9f1' have mac 'a0:36:9f:2c:df:f1' Which cloud-init are you running (-updates or -proposed)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1684092] Re: cloud-init in xenial generates bond configs that do not appear to work

Also thinking... can we reproduce if we do the following: 1) allocate new baremetal instance 2) first boot fails to bring up network 3) reboot 4) second boot comes up (some of the time, right?) 5) login, rm -rf /var/log/cloud-init* /var/lib/cloud/* /etc/network/interfaces.d/* 6) reboot If we're

[Bug 1682456] Re: md devices may leave remnants in /sys/class/block after removal

After partitioning two disks with two 1G partitions each, then this script will create two RAID1 devices (md0, md1) to test mdadm --stop commands ** Attachment added: "script to create two mirror raid devices"

[Bug 1682456] Re: md devices may leave remnants in /sys/class/block after removal

I run this script to watch whether the sysfs md structure goes away after stopping the device. ** Attachment added: "simple sysfs path watch script" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682456/+attachment/4861364/+files/w.sh -- You received this bug notification because you

[Bug 1682456] Re: md devices may leave remnants in /sys/class/block after removal

To recreate: 1. partition two disks sized the same into two equal partitions (2G disk, two 1G partitions each) # cat /proc/partitions major minor #blocks name 252 322097152 vdc 252 331048576 vdc1 252 341047552 vdc2 252 482097152 vdd 252 49

[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

Script to generate a zesty cloud-image that can recreate the issue. ** Attachment added: "01-netplan-udev-recreate.sh" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+attachment/4834861/+files/01-netplan-udev-recreate.sh -- You received this bug notification because you are

[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

Here's the journal from a boot which fails. ** Attachment added: "netplan-udev-fail-journal.tgz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+attachment/4834860/+files/netplan-udev-fail-journal.tgz -- You received this bug notification because you are a member of Ubuntu

[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

Script which launches the image created with the previous script to recreate issue. ** Attachment added: "02-netplan-udev-launch.sh" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+attachment/4834862/+files/02-netplan-udev-launch.sh -- You received this bug notification

[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

I've attached the requested journal. I've also attached two scripts which can be used to recreate the issue for further investigation. ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1669860] [NEW] cloud-init attempts to rename bonds

Public bug reported: 1. Zesty amd64 2. cloud-init 0.7.9-47-gc81ea53-0ubuntu1 3. cloud-init boots with a bond network config and does not attempt to rename bond0 4. cloud-init init (net mode) fails when it attempts to rename a bond interface Running with the following network config (2 nics)

Re: [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

On Wed, Mar 8, 2017 at 5:03 AM, Dimitri John Ledkov wrote: > I wonder if following should be done (in netplan code that does the re- > trigger, or outside after .link files modified): > > $ sync > $ udevadm control --reload > $ udevadm trigger --verbose

[Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

Details about different release vs. network backend requirements ** Attachment added: "lp1649931-release-network-matrix.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4833940/+files/lp1649931-release-network-matrix.txt -- You received this bug notification

[Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

@racb I verified systemd 229-4ubuntu17 with both ifupdown and networkd configuration. The specific packages and features is somewhat complicated due to the different scenarios and change in networking behavior in yakkety+ I've attached a chart with details. Also viewable here:

[Bug 1668693] Re: netplan fails to parse 'mtu' key

I suggest that we merge/land this MTU support first; and then I'll file another bug specifically for IPV6 Mtu support for netplan once we resolve the systemd bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1668693] Re: netplan fails to parse 'mtu' key

I've filed a systemd bug for ipv6 mtu here (along with a potential patch) https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668693 Title:

[Bug 1671951] Re: networkd should allow configuring IPV6 MTU

I've a build of this fix here: https://launchpad.net/~raharper/+archive/ubuntu/cloud-init-dev (systemd=232-19ubuntu3~fixbuild1) I've tested this minimally in a Zesty VM and it's successfully applies an IPV6MTU in addition to the device mtu (if that's also included). -- You received this bug

[Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Patch added: "ipv6_mtu.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/4835554/+files/ipv6_mtu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671951

[Bug 1671951] [NEW] networkd should allow configuring IPV6 MTU

Public bug reported: 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this

[Bug 1669860] Re: cloud-init attempts to rename bonds

Then we need to detect duplicate macs and somehow sort out which one to ignore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669860 Title: cloud-init attempts to rename bonds To manage

[Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

** Description changed: Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached. This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd

[Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

For yakkety resolvconf update; I've updated the SRU test-case to include a more general netplan config for bringing up ethernet devices; the previous version only worked on lxd (or instances with devices named eth0). With the above change; it looks like yakkety/zesty (due to running

Re: [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

On Tue, Mar 7, 2017 at 6:27 AM, Dimitri John Ledkov wrote: > Should one not restart systemd-networkd after writing out .link et.al. > units? > systemd-networkd only deals with .netdev and .network files; .link files are handled by udev This occurs during boot, before

Re: [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

On Tue, Mar 7, 2017 at 9:41 AM, Dimitri John Ledkov <launch...@surgut.co.uk> wrote: > On 7 March 2017 at 14:37, Ryan Harper <1669...@bugs.launchpad.net> wrote: > > On Tue, Mar 7, 2017 at 6:27 AM, Dimitri John Ledkov < > launch...@surgut.co.uk> > > wrote: >

[Bug 1669564] [NEW] udevadm trigger subsystem-match=net doesn't always run rules

Public bug reported: root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 root@ubuntu:~# apt-cache policy udev udev: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500

[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

** Description changed: - root@ubuntu:~# lsb_release -rd + 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 - root@ubuntu:~# apt-cache policy udev + + 2. root@ubuntu:~# apt-cache policy udev udev: - Installed: 232-18ubuntu1 -

Re: [Bug 1683919] Re: installation fails with trusty and hwe-t kernel

https://certification.ubuntu.com/hardware/201509-19592/ Possibly a different driver is needed but in any case, MaaS needs to figure what driver is needed and if the system isn't configured correctly. On Tue, Apr 18, 2017 at 4:18 PM, Scott Moser wrote: > OK. > So what seems

[Bug 1683919] Re: installation fails with trusty and hwe-t kernel

Looking at the storage config vs. what's on the system, there is a disk 'sdb' with properties: model: MM1000GBKAL, name: sdb, serial: 3001438033c8e841 which is no longer present on the system. I suspect either a bad disk, or disk has been removed. As such the storage config sent by maas is not

Re: [Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

On Fri, Jun 30, 2017 at 3:06 PM, Blake Rouse wrote: > I think having MAAS tell curtin to set the grub2/update_nvram to False, > works fine. Since the path to the EFI loader should not change this is > acceptable. > > Having grub adjust the EFI vars because of an

Re: [Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

On Tue, Aug 1, 2017 at 2:39 PM, dann frazier <dann.fraz...@canonical.com> wrote: > On Mon, Jul 31, 2017 at 12:07 PM, Ryan Harper > <1642...@bugs.launchpad.net> wrote: > > On Fri, Jun 30, 2017 at 3:06 PM, Blake Rouse <blake.ro...@canonical.com> > > wrote: >

Re: [Bug 1701297] Re: NTP reload failure (causing deployment failures with MAAS)

that looks related to overlayfs use in ephemeral environment. On Thu, Jun 29, 2017 at 3:24 PM, Ryan Harper <ryan.har...@canonical.com> wrote: > [ 46.973551] audit: type=1400 audit(1498766510.281:15): > apparmor="STATUS" operation="profile_load" profile="un

Re: [Bug 1701297] Re: NTP reload failure (causing deployment failures with MAAS)

[ 46.973551] audit: type=1400 audit(1498766510.281:15): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=2936 comm="apparmor_parser" [ 48.051990] audit: type=1400 audit(1498766472.362:16): apparmor="DENIED" operation="getattr" info="Failed name lookup -

[Bug 1690430] Re: [Hyper-V] Advanced networking support on Azure

In addition to the above covering (a) of the SRU tests, on Azure, we've tested the following observing no failures. (b) Azure (upgrade instance with no sriov devices and reboot) 1. ssh in, add proposed, install cloud-init, reboot 2. ssh in and check for errors (c1) Azure (launch sriov

[Bug 1685927] [NEW] cloud-init network v2 config loses some settings when rendered

Public bug reported: Running a v2 network-config through cloud-init's net-convert we can see that we're not passing it through, but importing and re-rendering lossy. % cat simple-v2.yaml network: version: 2 # comment above ethernets ethernets: ens0: dhcp4: true

[Bug 1685944] [NEW] tools/net-convert: fix argument order for render_network_state

Public bug reported: % cat simple-v2.yaml network: version: 2 # comment above ethernets ethernets: ens0: dhcp4: true match: macaddress: 00:11:22:33:44:55 set-name: ens0 switchports: # all cards on second PCI bus; unconfigured by

[Bug 1685944] Re: tools/net-convert: fix argument order for render_network_state

** Merge proposal linked: https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/323083 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685944 Title: tools/net-convert: fix

[Bug 1686984] Re: appears to fail in appy_net.py

*** This bug is a duplicate of bug 1635560 *** https://bugs.launchpad.net/bugs/1635560 This was fixed in curtin revno 442, and released. Zesty currently has version bzr482 which includes the fix. It was also non-fatal. ** This bug has been marked a duplicate of bug 1635560 MAAS2:

Re: [Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

On Wed, Aug 2, 2017 at 8:12 AM, Blake Rouse wrote: > update_nvram is now default for curtin and re-ordering is also default > MAAS send update_nvram as True ? or False by default? > for UEFI installs. I don't think setting grub2/update_nvram in debconf > should be a

[Bug 1708192] Re: SRU pollinate 4.25

Trusty verification test results. Updated client now provides uptime string in USER_AGENT sent to pollen server, passing verification. ** Attachment added: "trusty sru verification log (passes)"

[Bug 1708192] Re: SRU pollinate 4.25

** Description changed: === Begin SRU Template === [Impact] The key change is that the user agent string as of Zesty and Artful now contains the contents of /proc/uptime. In aggregate, this gives us important performance data to detect improvements and regressions in Ubuntu boot

[Bug 1708192] Re: SRU pollinate 4.25

Xenial verification is complete. Everything looks correct with uptime now present in the USER_AGENT string sent to a pollen server. Attaching log of xenial verification test. ** Attachment added: "xenial verification script and results (passes)"

[Bug 1708192] Re: SRU pollinate 4.25

** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

Revisting this on an artful image, and nothing besides the driver replug (what netplan apply does) appears to work to process .link files. Something changed I suspect in systemd w.r.t the builtin-test setup_net_link path which would process .link files. -- You received this bug notification

[Bug 1709135] Re: add bond primary parameter

This maps to networkd Bond config parameter: PrimarySlave= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709135 Title: add bond primary parameter To manage notifications about this bug go to:

[Bug 1709135] [NEW] add bond primary parameter

Public bug reported: ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat

[Bug 1448924] Re: watchdogd doesn't start on boot

** Description changed: + [Impact] + + * The watchdog service in Xenial does not start automatically even after +being configured. This makes the service not function reliably. + +This affects the 5.14 release in Xenial only and is already fixed in +5.15 included in the

[Bug 1689944] Re: util.system_is_snappy needs additional checks

Also, ubuntu-core image has some required kernel flags in /proc/cmdline $ cat /proc/cmdline BOOT_IMAGE=(loop)/kernel.img root=LABEL=writable snap_core=core_x1.snap snap_kernel=pc-kernel_x1.snap ro net.ifnames=0 init=/lib/systemd/systemd console=tty1 console=ttyS0 panic=-1 Specifically,

Re: [Bug 1689410] Re: nplan with networkd + resolvconf without resolved, results in no DNS resolution

On Tue, May 9, 2017 at 11:23 AM, Steve Langasek < steve.langa...@canonical.com> wrote: > Hi Ryan, > > On Tue, May 09, 2017 at 02:20:17PM -, Dimitri John Ledkov wrote: > > > it does create the yaml and call generate, but it's not > > sufficient to create the symlink IIRC due to the code in

Re: [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

On Tue, May 9, 2017 at 10:32 AM, Dimitri John Ledkov wrote: > Maybe this is easier to read. > > root@xnox-iad-nr5:~# journalctl -o short-monotonic -u ifup@bond0.service > -- Logs begin at Tue 2017-05-09 10:57:18 UTC, end at Tue 2017-05-09 > 15:22:34 UTC. -- > [

Re: [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

On Wed, May 17, 2017 at 1:14 PM, Dimitri John Ledkov wrote: > I'm very naive, so please bear with me if this is a silly question. As > far as I can tell the existing MTU setting in networkd will apply to > both ipv4 and ipv6 simultaniously. Are you arguing that you want

[Bug 1689944] [NEW] util.system_is_snappy needs additional checks

Public bug reported: Recent core snap images (edge channel revision 1886) do not contain the previously known files used to detect that a system is ubuntu core. In this bug, we should collect as many known paths/files/commands so we're hopefully defensive against further changes. Ubuntu Core 16

[Bug 1686338] Re: cloud-init fails if no network config is set

Which datasource and what's included? If no config is provided a fallback configuration is generated, but this appears to suggest that a config was provided (but was empty)? That's certainly a bug; I'd like to fully understand what's going on though such that the datasource is returning an

[Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure

This is annoying: % journalctl -D var/log/journal -o short-precise Journal file var/log/journal/1fe5c5ed88c14c81bd52acb9f96f3a18/system.journal uses an unsupported feature, ignoring file. -- No entries -- Why can't xenial systemd journalctl read an artful one? That seems like a terrible idea

Re: [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure

What does your networkctl status eth0 show? On Wed, Jun 14, 2017 at 11:34 AM, Ryan Harper <ryan.har...@canonical.com> wrote: > It looks a lot like this issue: > > https://github.com/systemd/systemd/issues/1645 > > Where DHCP works, it has an ip and can sync time and other

[Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure

It looks a lot like this issue: https://github.com/systemd/systemd/issues/1645 Where DHCP works, it has an ip and can sync time and other items, but the wait service isn't happy. On Wed, Jun 14, 2017 at 10:46 AM, Steve Langasek < steve.langa...@canonical.com> wrote: > The journal shows, two

Re: [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure

This is a known issue w.r.t waiting for IPV6 LL, on Xenial KVM, qemu -net user does not provide IPV6 LL response (yakkety and newer do), so there's a delay; it does sound like the IPV6 LL timeout is longer than it used to be as I've seen a 5 to 10 second delay in VMs launched on KVM on xenial,

Re: [Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

I think this is related and should address things. http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/revision/503 This curtin is available in the daily PPA, and is in process for SRU'ing https://launchpad.net/~curtin-dev/+archive/ubuntu/daily If that's not applicable, I'm not aware of any

Re: [Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure

And what about /etc/netplan/*.yaml and /run/systemd/network/* If you can attach the journal binary file, we can query the state independently from you tar up /run/log/journal/ Thanks On Tue, Jun 13, 2017 at 11:33 AM, Stefan Bader wrote: > #> ifquery --list > lo >

Re: [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

On Tue, May 2, 2017 at 3:05 AM, Dimitri John Ledkov wrote: > Looking at the journal files from the netplan-udev that fail, I see that > links are already renamed, before cloud-init renders things: > > Mar 09 17:51:12 ubuntu kernel: virtio_net virtio0 ens3: renamed from

Re: [Bug 1448924] Re: watchdogd doesn't start on boot

It's not been released. I've just started the SRU process for getting it into xenial-updates. If you want to test, you can try out the package from the PPA: ppa:raharper/bugfixes On Thu, May 4, 2017 at 4:27 AM, Алексей wrote: > Ryan, but I couldnt find this version in

Re: [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

On Mon, May 8, 2017 at 9:06 AM, Dimitri John Ledkov wrote: > I thought we have systemd hotplugging as well, can we not generate > I'm not sure what this means > depedencies that ifup@bond0.5.service Wants= and After= > ifup@bond0.service? and prevent all of these

Re: [Bug 1448924] Re: watchdogd doesn't start on boot

Please review the SRU process here. https://wiki.ubuntu.com/StableReleaseUpdates When it lands in -proposed, your help in the verification process is most welcomed. On Thu, May 4, 2017 at 10:46 AM, Алексей wrote: > okay, is there any ETA for SRU process to be finished? > We

Re: [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules

On Tue, May 2, 2017 at 8:54 AM, Dimitri John Ledkov wrote: > Ideally, the following should happen: > * boot > * Created link configuration context > > * Check if link configuration needs reloading -> appears in the debug logs > * New MTU is successfully applied > Let me

Re: [Bug 1717176] Re: Fail to install wichita box

On Thu, Sep 14, 2017 at 1:44 AM, ChristianEhrhardt < 1717...@bugs.launchpad.net> wrote: > Full console log and Maas error report on the failed Xenial deploy > > ** Description changed: > > - Version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) > + Maas version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) >

[Bug 1691489] Re: fstab entries written by cloud-config may not be mounted

As far as I can tell, I don't think we can "delay" the fsck service due to how the systemd-fstab-generator works on /etc/fstab entries For entries with a no-zero value for fsck (6th column), then the generator will write out a .mount file that looks like this:

[Bug 1717598] Re: Traceback when passing user-data on GCE

Can we get the full cloud-init log and possible a tar of /var/lib/cloud? I upgraded an artful lxd container and ran the cloud-config you have via single which is working fine. The stack-trace looks like it may be related to how the user-data is passed in (as a mime-parthandler); so getting the

[Bug 1722311] [NEW] softlockups/rcu sched

Public bug reported: 1.$ lsb_release -rd Description:Ubuntu Artful Aardvark (development branch) Release:17.10 2. $ apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.11.12 Candidate: 4.13.0.11.12 Version table: *** 4.13.0.11.12 500 500

[Bug 1722311] Re: softlockups/rcu sched

** Attachment added: "lspci-vnvn log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722311/+attachment/4965976/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722311

[Bug 1722311] Re: softlockups/rcu sched

** Attachment added: "kernel version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722311/+attachment/4965975/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722311

[Bug 1721579] Re: azure: remove sriov device configuration

** Merge proposal linked: https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/332075 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721579 Title: azure: remove sriov device

[Bug 1715128] Re: Crashes in convert_ec2_metadata_network_config on ScalingStack bos01 (ppc64el)

It appears that Ec2Local Datasource gets searched before OpenStack (network mode) does and is selected. EC2Local should not enable without the positive id via UUID; that is (EC2-Strict-mode IIRC), if we're in a MAYBE mode (where we are searching all datasources) we can't select a DS if we've not

[Bug 1716028] [NEW] qemu 2.10 locks images with no feature flag

Public bug reported: 1) % lsb_release -rd Description:Ubuntu Artful Aardvark (development branch) Release:17.10 2) % apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 1:2.10~rc3+dfsg-0ubuntu1 Candidate: 1:2.10+dfsg-0ubuntu1 Version table: 1:2.10+dfsg-0ubuntu1

[Bug 1687923] Re: virtio disk drive was not detected as available

It appears that virtio-blk uses dynamic major numbers: https://lkml.org/lkml/2016/3/2/1035 That suggests that to support virtio-blk, it'll need some thing else to check out of probert output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1716028] Re: qemu 2.10 locks images with no feature flag

Kevin, Thanks for the information. A couple of points for feedback: 1) there doesn't appear to be a way to run qmp query-schema without spawning a qemu instance in -qmp mode and having a second client issue the query-schema; certainly a qemu-system-$arch -qmp-schema would be quite useful when

[Bug 1716028] Re: qemu 2.10 locks images with no feature flag

In our multipath case, the initial open succeeds (it's not locked by anything else) and the second lock attempt fails, however, IIUC the fcntl structure[1] includes the locking pid, which should be our invocation of QEMU; Can we not check if the locking pid matches the current pid and not fail?

[Bug 1713537] Re: iscsi-targets don't quit session on shutdown

The previous fix was not sufficient for raid over iscsi and I missed running that test case. ** Changed in: curtin (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning)

The cloud-init output shows that networking was up and working (shows a gateway and hitting the ubuntu archive). I wonder if the initial DHCP lease that happened in the initramfs was up and it dropped the lease? -- You received this bug notification because you are a member of Ubuntu Bugs,

Re: [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

On Fri, Aug 25, 2017 at 5:47 PM, Lee Trager wrote: > This is easily reproducible by booting into any MAAS ephemeral > environment(commissioning, testing, rescue mode). Apt works regardless > of /etc/resolv.conf being set as apt is configured to proxy through the > rack

<    2   3   4   5   6   7   8   9   10   11   >