** 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 argumen
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 thems
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
matc
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
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 notificati
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.
https://bugs.launchpad.net/bugs/16
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 to be the issue here
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
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 r
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
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"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682456/+attachment/4861363/+fi
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
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
Candid
@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 add
onf(8)
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 receiv
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
> 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 Mar
** 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.
https://bugs.launchpad.net
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 received
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
** 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 ot
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.
> https://bugs.launchpad.net/bugs/16
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 no
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 su
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: {
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"
https://bugs.launchpad.net/ubuntu/+source/cloud-ini
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
> [ -n "$name" ] || {
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 ar
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' state
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,
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.
https://bugs.launchpad.n
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:
** 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
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
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 not
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 notificati
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 becau
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 subscri
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 a
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
Bu
@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:
http://paste.ubu
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 be
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 --subsystem-match=net --action=add
>
> This
On Tue, Mar 7, 2017 at 9:41 AM, Dimitri John Ledkov
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:
> >
> >> Should one n
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 systemd-networkd starts.
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
systemd-resol
** 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 +
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)
co
** 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
-
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 http://archive.ubun
On Thu, Mar 2, 2017 at 4:56 AM, Stefan Bader
wrote:
> I created a modified patch and verified that
> - bcache base devices again are numbered 0,1,...
> - partioning a bcache device creates the expected bcacheXpY devices
> Will submit this change upstream (and for pre-stable zesty).
>
> ** Patch a
Public bug reported:
1. root@z1:/etc/netplan# lsb_release -rd
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
2. root@z1:/etc/netplan# apt-cache policy nplan
nplan:
Installed: 0.18
Candidate: 0.18
Version table:
*** 0.18 500
500 http://archive.ubuntu.c
Public bug reported:
1. root@ubuntu:/run/systemd/network# lsb_release -rd
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
2. root@ubuntu:/run/systemd/network# apt-cache policy systemd
systemd:
Installed: 232-18ubuntu1
Candidate: 232-18ubuntu1
Version table:
**
'config' should be 'parameters'
** Changed in: nplan (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667765
Title:
bridge parameters are unknown
To manage not
Public bug reported:
Attempting to bring up a bridge with some config fails; all keys that
are listed in documentation are rejected. I removed 'ageing-time' and
it rejects the next item in the config dictionary.
root@ubuntu:/etc/netplan# netplan generate
Error in network definition //etc/netpla
On Fri, Feb 24, 2017 at 10:39 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> It doesn't look like that patch ever landed in mainline. Do you plan on
> responding to the upstream thread with your recommendation?
>
It's an untested change; I've not pushed anything upstream.
If tim
I think this is the relevant qemu patch that we might need:
Discussion:
https://www.spinics.net/linux/fedora/libvir/msg142550.html
Patch:
http://patchwork.ozlabs.org/patch/721974/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
On 4.10 kernel, when creating bcache devices, each device kname is now
incremented by 16
/dev/bcache0
/dev/bcache16
/dev/bcache32
etc.
This was to support partitioning of bcache devices[1], however, This
also will limit the number of bcache devices and doesn't match how oth
On Wed, Feb 22, 2017 at 9:15 AM, Eric Desrochers <
eric.desroch...@canonical.com> wrote:
> I can't attach a sosreport since it may reveal data that my contact
> doesn't want to be public on the bug, but I can check details you would
> inquire.
>
I think an lshw output would be useful; mostly CPU
On Wed, Feb 22, 2017 at 8:30 AM, ChristianEhrhardt <
1666...@bugs.launchpad.net> wrote:
> Discussed on IRC,
>
> TL;DR of that:
> The real customer case is different than we assumed so far:
> sda <- Host root
> sdb <- VG <- Guest Disk
>
>
What sort of disks and connections are we talking about on t
Public bug reported:
Running btrfs-debug-tree --uuid /dev/vdb returns only the program version,
nothing about the UUID.
I can correctly see the UUID in the --root output and others but --uuid does
not return that value.
1. root@z-oestrous-suellen:~# lsb_release -rd
Description:Ubuntu Zesty
I've verified the SRU test with the package in Xenial proposed. I've
also updated an UbuntuCore16 image with uses networkd and cloud-init to
validate that early networking which requires dns for resolving urls
works.
** Tags removed: verification-needed
** Tags added: verification-done
--
You
On Tue, Feb 21, 2017 at 12:07 PM, Eric Desrochers <
eric.desroch...@canonical.com> wrote:
> @Ryan,
>
> This situation has been brought to my attention by someone, and I was
> able to reproduce it myself.
>
> The main difference between my setup and his, is that my contact has
> "vg02-vg02--labmysq
This opens the underlying device (lvm) via O_DIRECT and submits Linux
AIO requests to the device. If the VMs are sharing the LVM pool it may
be overwhelming the underlying devices.
This feels like there are syncs after each write which is going to
serialize access to the LVM (and underlying dev
https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-inspect-internal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665701
Title:
Missing inspect-internal command
To manage notifications about th
Is there an example XML where this is reproducible?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665410
Title:
Mapping multiple disks to guests errors on ubuntu KVM
To manage notifications about
** 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 +
Public bug reported:
ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@ubuntu:~$ apt-cache pol
On Thu, Feb 9, 2017 at 9:23 PM, dann frazier
wrote:
> On Feb 9, 2017 16:11, "Ryan Harper" <1642...@bugs.launchpad.net> wrote:
>
> On Thu, Feb 9, 2017 at 4:31 PM, dann frazier
> wrote:
>
> > The grub2 changes are in zesty as of 2.02~beta3-4ubuntu1. Could I as
On Thu, Feb 9, 2017 at 4:31 PM, dann frazier
wrote:
> The grub2 changes are in zesty as of 2.02~beta3-4ubuntu1. Could I ask
> the curtin developers to take a look at implementing the necessary
> changes there? Specifically, using the new grub2/update_nvram preseed
> instead of manually passing --
On Tue, Feb 7, 2017 at 1:42 AM, ChristianEhrhardt <
1662...@bugs.launchpad.net> wrote:
> Hi Ryan,
> just to find if that is totally new or maybe bisect&backport - do you have
> any extra data on other "incarnation" of qemu?:
> - new Qemu in Yakkety or Zesty-Proposed
> - new Qemu in Debian
> - Upst
Public bug reported:
qemu-system-aarch64 supports -smbios parameters to export values into the DMI
tables.
These values are viewable via /sys/class/dmi/id/* or via dmidecode (V3 tables).
Passing in custom values for things like -smbios
type=1,manufacturer="Foobar" should result in that value bei
** Patch added: "xenial-dns-before-online-target-lp1649931-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4812597/+files/xenial-dns-before-online-target-lp1649931-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bug
If we can get the full installation log with the same error, please open
up a new bug against curtin. While the error mentioned in comment #30
is mdadm related, this bug addressed errors during mdadm scan of
previous disks and the issue in comment #30 is something else.
--
You received this bug
systemd-networkd-resolvconf-update.service uses default dependencies
which will only run after sysinit.target, however cloud-init.service
needs to run before sysinit.target; systemd apparently dropped running
the service due to the inconsistent order. Adding a
DefaultDependencies=no to systemd-net
Something isn't working here. I also typo'd the test-case, in
particular, the change to the cloud-init.service unit didn't specify
'systemd-networkd-wait-online.service', the sed command missed the 'd'
in networkd.
When I fix that, I find that systemd-networkd-resolvconf-update.service
does NOT r
ssh ubuntu@$HOST_IP sudo touch /run/block-curtin-poweroff
If you can, then after a failed curtin install, getting at
/var/log/curtin/install.log
will contain everything we need to investigate further.
> On Wed, Jan 18, 2017 at 3:00 PM Ryan Harper <1618...@bugs.launchpad.net>
> wrote:
>
Is it possible to include the entire installation.log?
Do repeat deploys to the same node and same configuration fail
consistently?
On Wed, Jan 18, 2017 at 6:50 AM, Ante Karamatić <
ante.karama...@canonical.com> wrote:
> ** Attachment added: "installation.log"
>https://bugs.launchpad.net/cur
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
1. % lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
2. % apt-cache policy os-prober
os-prober:
Installed: 1.70ubuntu3
Candidate: 1.70ubuntu3
Version table:
*** 1.70ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 P
I've uploaded a cloud-init test package to a ppa; you can test that
this update fixes the ntp issue on an existing node.
On an affected node:
1. sudo add-apt-repository -y ppa:raharper/bugfixes
2. sudo apt update && sudo apt install cloud-init (#installs
0.7.9-6-gf5fdb6c-1~bddeb)
3. cat >user
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645644
Title:
ntp not using expected servers
To manage notifications about
Not a MAAS issue.
** Changed in: maas (Ubuntu)
Status: New => Invalid
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
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
> correctly.
>
Ahh, interesting.
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, I'll follow up with MAAS.
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 subscri
If the cloud-init used in the build does not ship the Z99-cloud-local-
tests.sh, the hook script exits non-zero and fails the build.
https://launchpadlibrarian.net/301226697/buildlog_snap_ubuntu_xenial_amd64_core_BUILDING.txt.gz
Looking at the failed hook:
(foudres) hooks % cat 19-remove-cloud
** Bug watch added: Debian Bug tracker #847440
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649931
Title:
systemd-networkd needs to ensur
On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> How is this fixed in the development release?
>
For systemd portion, we carry the
systemd-networkd-resolvconf-update.service as a delta from Debian
Ryan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> How is this fixed in the development release?
>
There is an upstream resolvconf bug that addresses that package portion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
> Also the having a "Regression Potential" of low just bec
** Patch added: "xenial-dns-before-online-target-lp1649931.debdiff"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4792126/+files/xenial-dns-before-online-target-lp1649931.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** 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 +
This fix was needed for cloud-init in Ubuntu-Core 16 images which uses
Xenial archive. There is not a UC16 snappy image based on Yakkety
archive, so we do not have any users of this path in yakkety and no way
to test in a non-existent image. I'm marking verification-done.
** Tags removed: verifi
** Patch added: "xenial_resolvconf-lp1649931.diff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4792030/+files/xenial_resolvconf-lp1649931.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
16 at 8:17 PM, Ryan Harper
wrote:
> The other oddity, running the guest with 1 cpu always works for me in the
> cases where it failed before.
>
>
> On Wed, Dec 14, 2016 at 5:37 PM, Ryan Harper
> wrote:
>
>>
>>
>> On Wed, Dec 14, 2016 at 4:31 PM, Seth Forsh
The other oddity, running the guest with 1 cpu always works for me in the
cases where it failed before.
On Wed, Dec 14, 2016 at 5:37 PM, Ryan Harper
wrote:
>
>
> On Wed, Dec 14, 2016 at 4:31 PM, Seth Forshee <
> seth.forshee...@canonical.com> wrote:
>
>> Looking at
On Wed, Dec 14, 2016 at 4:31 PM, Seth Forshee wrote:
> Looking at kernel 4.9, the RTC_UIE_ON ioctl sets an alarm via the
> cmos_rtc driver. This does a couple of things.
>
> 1. Disables the CMOS RTC alarm interrupt, writes an alarm time to the
> CMOS RTC, then enables the alarm interrupt.
>
> 2.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636912
Title:
systemd-networkd runs too late for cloud-init.service (net)
To man
I've opened a new bug for the DNS networkd/resolvconf issue:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931
We'll track a new SRU for fixing that issue separately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
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 + DNS early in
901 - 1000 of 1382 matches
Mail list logo
