** Description changed:
OS:Ubuntu Mate 18.04 daily
apport-collect won't work because it's say that i am missing "You need
to run 'sudo apt-get install python3-apport' for apport-collect to
work." But "python3-apport" its installed
work.
apolihron@apolihron-desktop:~$ sudo apport-
Public bug reported:
I'm booted into a 16.04 maas rescue environment.
$ apport-collect
You need to run 'sudo apt-get install python-apport' for apport-collect to work.
running the provided command will get me a python2 stack.
python3-apport is already installed.
python3 should be used.
I the
Public bug reported:
As ubuntu goes forward, net-tools is looking to be dropped.
Byobu currently depends on net-tools. That code should be replaced by
iproute2.
Related bugs:
* bug 925145: cloud-init Use ip instead of ifconfig and route
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package:
Marked as fix-released.
I tested today with 20180115.1 image from bionic.
wget http://cloud-images.ubuntu.com/bionic/20180115.1/bionic-server-
cloudimg-amd64.img -O bionic-server-cloudimg-amd64.img
url="https://smoser.brickies.net/ubuntu/nocloud/";
qemu-system-x86_64 -enable-kvm -m 768 \
-net
@Nate,
there is some suggestions about that in bug 1433761.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1089389
Title:
juju bootstrap fail behind a proxy wh
closer.
still need artful to be updated. but seems like next build would do that.
$ for f in *-initrd; do echo == $f ==; lsinitramfs $f | grep zfs; done
== artful-20180109-initrd ==
== bionic-20180115.1-initrd ==
lib/modules/4.13.0-25-generic/kernel/zfs
lib/modules/4.13.0-25-generic/kernel/zfs/spl
Hi,
I'm coming here from bug 1730744.
Is this bug expected to be fixed for 18.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Undecided => Medium
--
Y
Well, I went looking to verify this. We got builds out of artful and
xenial today (20180109).
$ usquery maas3-daily --max=1 ftype=boot-initrd arch=amd64 subarch~ga- \
kpackage~generic \
--output-format='%(release)s %(version_name)s %(path)s %(item_url)s' |
while read rel ver path url; do \
** Changed in: maas-images
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1737592
Title:
no zfs module in initramfs
Stat
** Tags removed: verification-donezesty
** Tags added: verification-done-zesty
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Dimitri,
What is the fix that you put in? I assume it was to systemd ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1734167
Title:
DNS doesn't work in no-cloud as laun
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touc
I've verified zesty with the script that is attached.
Output is shown here.
** Attachment added: "verification log of zesty"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5023065/+files/zesty.log
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verific
This bug is believed to be fixed in cloud-init in 1705804. If this is
still a problem for you, please make a comment and set the state back to
New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
** Changed in: maas-images
Status: New => Confirmed
** Changed in: maas-images
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Also affects: maas-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1737592
Title:
no zfs module in initramfs
** Summary changed:
- mount can exit (success) when it fails
+ mount can exit 0 (success) when it fails
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736556
Title:
m
Adding this to maas-images would look like this:
http://paste.ubuntu.com/26165463/
but we'd avoid that as if zfs is officially supported, then it might as
well be in the default initramfs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
As a work around you can specifically add the zfs module (if its in your
kernel) with:
$ cat /etc/initramfs-tools/hooks/zfs
#!/bin/sh
. /usr/share/initramfs-tools/hook-functions
manual_add_modules zfs
$ update-initramfs -u -k all
--
You received this bug notification because you are a member o
Public bug reported:
zfs support exists in Ubuntu kernels for 16.04 and later, but the
default initramfs build does not include this module.
Other common filesystems are included.
As a small piece of information:
$ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
3.2M/lib/modules/4.13.0-17-
** Also affects: resolvconf (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu Zesty)
Status: New => Triaged
** Changed in: resolvconf (Ubuntu Zesty)
Importance: Undecided => Medium
--
You received this bug notification because you are a membe
This is marked fix-released in cloud-initramfs-tools, but in reality that is
not a useful fix anymore.
The fix was added to cloud-initramfs-dyn-netconf which is not used in xenial
and later.
The fix really should go into mkinitramfs-tools proper.
--
You received this bug notification because y
** Changed in: apport (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: apport (Ubuntu Zesty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.l
Robie, Brian,
I went ahead and did the reproduce in the test and selected '2' in the
multi-select. Heres the full console log. My responses can be seen there alsol.
$ for release in xenial artful; do
> ref=$release-proposed;
> echo "$release START --";
> lxc-
Full disclosure, As you can see, I ran with artful and xenial (just
copied and pasted text from above). I didn't run with zesty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs
blkid output was above. and as I said in my first comment the entry in
/etc/fstab is wrong.
there is no LABEL=METADATA device. So 'mount' *should* fail, but I would have
expected it to exit non-zero.
I noticed just now that '/etc/fstab' has 'nofail' for that line. I
removed that, and it fails
I didn't notice initially but just did. The entry in /etc/fstab is
bogus, containing a LABEL=METADATA but the disk here is LABEL=config-v2.
That is clearly broken, but 'mount' should not exit success.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Public bug reported:
I'm on softlayer in an official Ubuntu image and 'mount' exits
success even when it fails.
$ cat /etc/cloud/build.info
build_name: server
serial: 20171116
$ cat /etc/fstab
LABEL=cloudimg-rootfs /ext4 defaults,relatime 0 0
# Added by Cloud Image build pr
** Description changed:
=== Begin SRU Template ===
[Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".
Thus dns resolution does not work. Of most interest was the MAAS use
case of the 'root=http://<>/sq
** Attachment added: "test script"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1735225/+attachment/5016294/+files/test-lp1714308.sh
** Also affects: resolvconf (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: resolvconf (Ubuntu Xenial)
Importance:
** Also affects: initramfs-tools (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: initramfs-tools (
Public bug reported:
=== Begin SRU Template ===
[Impact]
Booting a kernel/initramfs with 'rooturl=http://...' for trusty
or xenial requires also adding 'rc-initrd-dns' or 'cloud-config-url='
to the kernel command line in order to get the fix provided by bug
1711760.
If a user boots with 'rooturl=
** Description changed:
I use no-cloud to test the kernel in CI (I am maintainer of the bcache
subsystem), and have been running it successfully under 16.04 cloud
images from qemu, using a qemu command that includes:
-smbios "type=1,serial=ds=nocloud-
net;s=https://raw.githubuserconte
I've verified that this is reproducible within lxc, and then filed a bug i
saw (bug 1734939) as a result.
Heres a trivial reproduce:
## just showing content of the url.
$ curl --silent https://hastebin.com/raw/coladicuva
#!/bin/sh
cat /proc/uptime | tee /run/user-script-uptime
$ name=btest
$ lxc
To be clear, the suggestion that xnox made causes a ordering cycle.
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
zesty does not show this problem. neither does xenial. I reflected that
in the status.
** Changed in: cloud-init (Ubuntu Artful)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Artful)
Importance: M
zesty does not show this problem. neither does xenial. I reflected that
in the status.
$ sudo journalctl -b -o short-monotonic | pastebinit
http://paste.ubuntu.com/26035779/
$ sudo journalctl -o short-precise | pastebinit
http://paste.ubuntu.com/26035774/
Nov 24 17:49:25.193028 ubuntu systemd[1]:
that ordering cycle is if we add 'After=systemd-resolved.service' to
cloud-init.service.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1734167
Title:
DNS doesn't work in
I think the primary issue is that cloud-init.service is depending on using the
network fully.
cloud-init.service runs:
After=networking.service
After=systemd-networkd-wait-online.service
Before=network-online.target
But systemd-resolved.service runs
After=systemd-networkd.service network.t
Heres some more info that is from failed system using bionic.
$ sudo journalctl -o short-monotonic --no-pager | pastebinit
http://paste.ubuntu.com/26035621/
$ sudo base64
/run/log/journal/7ba07d79c32c4103aefee168e433d847/system@e9ae467d022046f0a034147c78254ae9-0001-00055ebdb4f0260b.jo
$ wget http://cloud-images.ubuntu.com/artful/20171122/artful-server-
cloudimg-amd64.img
## set up dns locally for 'qemu-host' to the default ip for user networking.
$ grep qemu-host /etc/hosts
10.0.2.2 qemu-host
$ cat data/user-data
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh
Bummer.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171122_204418_8ac74@/log.gz
shows
[ 43.793658] systemd[1]: media-root\x2dro.mount: Found ordering cycle on
-.mount/start
[ 43.801914] systemd[1]: me
Well, I tried updating /etc/fstab
https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/fix/get-journal-publish-artifacts
but that doesnt help. It still fails and goes on after 90 seconds. I
verified this by just changing the LABEL= to a different string that
would
Note that this failure could just be due to slowness at this point.
The open-iscsi tests that are running are running in nested qemu with kvm
disabled. So it is quite slow to boot.
We seem to be getting usually around 40 seconds for that to arrive. My
statement is based on
messages like:
[
It looks like:
x-systemd.device-timeout=
might be useful
https://www.freedesktop.org/software/systemd/man/systemd.mount.html
we'd have to update the /etc/fstab entry in 'patch-image' of the open-
iscsi test, but we could do that and just bump it to 6m or something.
As some evidence, that this mi
Is there a way to bump that 1m30s timeout from the kernel command line?
Even image modification would be ok, as we're already modifying the
image to insert the deb.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in U
This issue is discussed in a document at
https://docs.google.com/document/d/14xH2Q3VH_7ArXzRPhqogfACeOI0rmEinm_Q98imNWlc/
Its all about "transition" of networking information from the initramfs
environment which is configured by the kernel command line over to the
"real root".
The Ubuntu founda
Another fail log at
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171114_192057_17bf1@/log.gz
Basically if you look at bionic failures
http://autopkgtest.ubuntu.com/packages/o/open-iscsi/bionic/amd64
if i
Public bug reported:
This issue keeps cropping up. It shows itself in open-iscsi autopkg tests.
I think it might just be "really slow system". It seems the timeout is only
1 minute 30 seconds for the disk to appear, and in a happy run you
might see something very close:
[K[ [0;31m*[0;1;31m*[
Public bug reported:
I noticed that lxd (lxc list) reports that an lxc container has an ipv6
address in artful or bionic. It does not list this in xenial or zesty.
I suspect this change occurred in the switch over to netplan/networkd.
This may at first seem harmless or even desired, but note tha
Bill, just for some more information.
Also note "This options is deprecated".
The correct way to do it now is to configure dirmngr.conf (which is
backgrounded when you invoke gpg).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
In an update to my own comment #2 above, we have made some progress:
a.) FIXED: exited success (0) meaning its caller did not even log error (bug
1532855)
b.) NOT FIXED: left /etc/apt/sources.list.d/.list in place, meaning
subsequent 'apt-get update' was guaranteed to fail. (bug 1671566)
--
Y
** Attachment removed: "lp-1711760-test.sh: script to aid in testing default
to proposed"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/4966838/+files/lp-1711760-test.sh
** Attachment removed: "updated recreate script that supports running in
'control' mode
** Attachment added: "output of running script with comments showing fix."
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5006686/+files/verify-trusty-lp-1711760.txt
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-tru
** Attachment added: "final version of recreate script"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5006685/+files/lp-1711760-test.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https
** Attachment added: "one more try at reproduce script."
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/5006069/+files/lp-1711760-test.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resol
testing showed that I uploaded a bad version.
Fixed in a new upload
https://launchpadlibrarian.net/345007871/resolvconf_1.69ubuntu1.3_source.changes
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-failed verification-failed-trusty
--
You received this
Output of recreate script:
$ /tmp/lp-1730744-reproduce-lxc
=== launch container testme50 ===
Creating testme50
Starting testme50
=== wait for boot ===
.1 degraded 7.00
=== set hostname to bogus value: testme50-foo ===
=== show slow sudo ===
sudo: unable to resolve h
** Attachment added: "script with full reproduce."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1730744/+attachment/5005923/+files/lp-1730744-reproduce-lxc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
** Changed in: resolvconf (Ubuntu Trusty)
Status: Confirmed => In Progress
** Changed in: resolvconf (Ubuntu Trusty)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: resolvconf (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received
Somewhat interestingly, I'm not sure why I can't just reproduce this by:
$ sudo bash -c 'oname=$(hostname);
trap "hostname $oname" EXIT;
hostname my-bogus-hostname;
hostname;
time sudo /bin/true;' ; hostname
but it doesnt reproduce this way.
--
You received this bug notification beca
This is more easily recreated with lxc.
Given a host with systemd-resolv:
$ lxc launch ubuntu-daily:xenial x1
$ sleep 10 # let it boot
$ lxc exec x1 -- grep '^[^#]' /etc/resolv.conf
nameserver 10.75.205.1
search lxd
$ lxc exec x1 -- hostname bogus-host
$ lxc exec x1 -- bash -c 'time sudo /bin/tr
I've uploaded the same change that is in xenial but slightly adjusted for
trusty.
I'm attaching an updated recreate script that works for both xenial and trusty.
(trusty needs to install the cloud-initramfs-dyn-netconf package to mimic the
MAAS ephemeral environment).
** Attachment added: "lp-1
Here is some information collected when I tried to debug.
Using resolved on host =
## guest
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.0.2.3
sea
Public bug reported:
I'm seeing very slow 'sudo' times in a qemu guest when the host uses
systemd-resolved.
If I change /etc/resolv.conf on the host to point directly to a dns server
(8.8.8.8) then the problem goes away.
To recreate, you can download a cloud image and boot it under qemu with a
Public bug reported:
I have just used 'env -i' to avoid the gtk dialog.
The same occurs when using gtk.
I can't file a bug against systemd because it complains:
This is not an official Ubuntu package. Please remove any third party
package and try again.
Other packages work (i tried 'cloud-in
** Also affects: resolvconf (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: resolvconf (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: resolvconf (Ubuntu Trusty)
Importance:
** Description changed:
=== Begin SRU Template ===
[Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".
Thus dns resolution does not work. Of most interest was the MAAS use
case of the 'root=http://<>/sq
** Also affects: apport (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1722564
Title:
apport question will not a
Some comments by Adam Conrad in #ubuntu-devel:
https://irclogs.ubuntu.com/2017/10/30/%23ubuntu-devel.html
10:44 is there a fine manual that ii'm supposed to read for
10:44 jbicha: Bah. That's bound to be mythtv-specific. Lemme look.
10:44 https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1
Public bug reported:
Our /etc/apt/sources.list looks like this:
$ cat /etc/apt/sources.list
| deb http://archive.ubuntu.com//ubuntu devel main restricted universe
multiverse
| deb http://archive.ubuntu.com//ubuntu devel-updates main restricted universe
multiverse
| deb http://archive.ubuntu.com/
Essentially we are looking for this work flow to function, with or without
network devices attached to the system.
$ wget http://cloud-images.ubuntu.com/some-disk.img
$ qemu-img create -f qcow2 -b some-disk.img my-disk.img
$ sudo ~/bin/backdoor-image my-disk.img --user=user1 --password=passw0rd1
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1728181
Title:
systemd-networkd-wait-online waits when devic
** Attachment added: "updated recreate script that supports running in
'control' mode (to show no harm is done)"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4998244/+files/lp-1711760-test.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
the attached log shows this is working when expected and not when not
expected.
** Attachment added: "my.log: log of running lp-1711760-test.sh"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4998243/+files/my.log
--
You received this bug notification because you are a member of U
> I have reviewed this. +1 from ~ubuntu-sru.
Thanks for the thoughtful review.
> What happens when the DHCP lease acquired in the initramfs expires? What
> if the DNS server changes after a new lease? Really it's the entire DHCP
> lease that needs handing over from the initramfs rather than just
I updated some state on the tasks. As justification, this fix is in
resolvconf, so I dropped cloud-init. I had added it thinking it might
need integration, but it did not. Also marked the 'ubuntu' task as
"won't fix". The problem did not currently exist in Artful, and the
solution provided in r
** Description changed:
=== Begin SRU Template ===
- [Impact]
+ [Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".
Thus dns resolution does not work. Of most interest was the MAAS use
case of the 'root=
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1726818/+attachment/4992312/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1726818/+attachment/4992313/+files/ProcCpuinfoMinimal.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** No longer affects: e2fsprogs (Ubuntu)
--
You received this bug
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
DistroRelease: Ubuntu 17.10
Ec2AMI: ami-02da
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--l
So the/some interesting points of dmesg.log:
[0.00] random: get_random_bytes called from start_kernel+0x42/0x4e1
with crng_init=0
[0.00] Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version
7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubu
The attached /var/log/cloud-init.log has 2 boots in it.
One starts at 14:15:18 (line 1) and one starting at 14:21:17,808 (line 719).
The first boot successfully updated the partition table for /dev/sda
so that the first partition (/dev/sda1) took the whole ~ 10G disk.
2017-10-24 14:15:33,338 -
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/17225
** Attachment added: "lp-1711760-test.sh: script to aid in testing default to
proposed"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4966838/+files/lp-1711760-test.sh
** Attachment removed: "lp-1711760 script to aid in testing"
https://bugs.launchpad.net/maas/+bug/1711760/+at
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ Without this fix applied, dns settings provided to the dhcp response
+ in the initramfs are not reflected in the "real root".
+
+ Thus dns resolution does not work. Of most interest was the MAAS use
+ case of the 'root=http://<>/s
I've also asked the MAAS team to build a maas-images with an updated
squashfs.
I made a couple changes to lp:maas-images on Friday to make that easy to do
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/381
http://bazaar.launchpad.net/~maas-images-main
Public bug reported:
the newly added cloud-init apport support shows a list of cloud
providers and asks the user to select one. There are currently 18
options. For any option > 10, apport will just take the '1' that is
typed as the answer.
It should obviously wait for more than one character or
This script runs and demonstrates functional dns.
It launches a guest with a custom kernel command line
pointing to a nocloud datasource running on the host.
It uses user mode networking to seed a dns server and a
dns search.
The 'seedfrom' is done over dns which would not work if this
change wer
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6 MTU
S
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
** Attachment added: "lp-1711760 sc
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubu
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1707222
Title:
usage of /tmp during boot is not safe due
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bu
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.co
I opened bug 1718227. for packages that ship if-up.d or if-down.d
scripts.
On Tue, Sep 19, 2017 at 2:18 PM, Steve Langasek <
steve.langa...@canonical.com> wrote:
> On Tue, Sep 19, 2017 at 01:09:24PM -0000, Scott Moser wrote:
> > "I don't know I don't think..&
101 - 200 of 562 matches
Mail list logo
