** Also affects: cloud-initramfs-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
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:
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
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: In Progress => Fix Released
--
You received this bug notification because you are a member of
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
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
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
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
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
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
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
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
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
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
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
I've taked this qemu-file-locking just so we can group/easily find other bugs
that have this tag.
link to search for all bugs with that tag is: https://goo.gl/W2aT2T
or the longer form:
** Tags added: qemu-file-locking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716028
Title:
qemu 2.10 locks images with no feature flag
To manage notifications about this bug go to:
** Tags added: qemu-file-locking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734990
Title:
[SRU] pike stable releases
To manage notifications about this bug go to:
> Sounds like some religious b#@*S%^t or a f#%@* vendor lock. We use
> Ubuntu for development, testing and production. It's great, but not
> unique. We could use let's say Debian instead as well. I didn't even
> know/care about the ubuntu user until faced this issue.
???
Its vendor lock to have
** 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
Bugs, which is subscribed to
** Also affects: maas-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737592
Title:
no zfs module in initramfs
To manage notifications about this
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736556
Title:
mount can exit 0 (success) when
I have a fix
http://paste.ubuntu.com/26170810/
when launchpad git returns I will push and get uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737704
Title:
Cloud-init fails if iso9660
** Summary changed:
- Cloud-init seems not run on today's bionic images (20171211)
+ Cloud-init fails if iso9660 filesystem on non-cdrom path in 20171211 image.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> High
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are
,index=1 \
-device virtio-blk,drive=disk01,serial=my-seed.img \
-m 768 -nographic
It would work fine if you attached the iso filesystem as a cdrom.
(-cdrom my-seed.img)
** Affects: cloud-init
Importance: High
Assignee: Scott Moser (smoser)
Status: In Progress
** Affects: cloud
Quote:
| The xenial box is substantially less useful to Vagrant users with the
| "ubuntu" user as the default, and there is limited benefit to having the
| "ubuntu" user.
This is entirely untrue. There is *substantial* benefit in Ubuntu
consistency across platforms. Users who are familiar
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
Bugs, which is subscribed to
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
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
** Changed in: cloud-init
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731868
Title:
cloud-id: enable ESXi 6.5.0
To manage notifications about this
** 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
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
** Description changed:
I had reported this once before in bug 1666573.
I thought it was fixed there, but apparently not.
The failure shows itself as (controls removed):
- [ 80.089654] systemd[1]: media-root\x2dro.mount: Found ordering cycle on
media-root\x2dro.mount/start
- [
$ for r in artful zesty xenial; do lxc-proposed-snapshot --proposed $r
$r-aliyun; done
Creating artful-aliyun
--proposed --
Get:1 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB]
Hit:2 http://archive.ubuntu.com/ubuntu artful InRelease
Get:3 http://security.ubuntu.com/ubuntu
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722564
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/334880
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731868
Title:
cloud-id: enable ESXi 6.5.0
To
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 --";
>
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722564
Title:
apport
As suggested to Patrick in IRC, this can be worked around by
partitioning with gpt rather than MBR.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Importance: High =>
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
Bugs, which is
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
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Artful)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided =>
** Changed in: cloud-init
Status: In Progress => Fix Committed
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
work around is to clean empty dirs with something like:
find /archive/mirrors/ -type d -empty -delete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444632
Title:
sstream-mirror does not clean
** 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
** 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
** Description changed:
Cloud-init can fail to download a url in '#include' for reasons such
as bug 1734167 but not represent that failure anywhere.
$ curl --silent https://hastebin.com/raw/coladicuva
#!/bin/sh
cat /proc/uptime | tee /run/user-script-uptime
$ lxc launch
** 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-
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
$
Public bug reported:
Cloud-init can fail to download a url in '#include' for reasons such
as bug 1734167 but not represent that failure anywhere.
$ curl --silent https://hastebin.com/raw/coladicuva
#!/bin/sh
cat /proc/uptime | tee /run/user-script-uptime
$ lxc launch ubuntu-daily:bionic b4
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
Bugs, which is subscribed to
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734167
Title:
DNS doesn't work in no-cloud as launched by
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
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:
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
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
$ 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 }
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]:
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
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732964
Title:
dhclient process started by cloud-init-local.service still running
Public bug reported:
Running git-ubuntu on a remote system I hit the traceback below.
Note that this was when ssh'd into a system, and then I copied and
pasted the url into my local browser.
The authorization page:
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:
[
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
Bugs, which is subscribed to Ubuntu.
* bug 1723183: transient systemd ordering issue when using overlayroot
* bug 1732028: [systemd] transient boot fail with overlayroot
Hi, there is also this commit [1] that fixed bug 1723183. We just kind
of gave up and commented out the root entry.
I've opened up a bug against systemd in bug
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
** Description changed:
In the open-iscsi test we boot a read-only root iscsi target, using
overlayroot.
Transiently this operation fails, ultimately leading to emergency shell.
Since this occurs in automated test, there is no access to that console
(it is being logged to a file).
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** No longer affects: cloud-init
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init
James,
I do not think that manage_etc_hosts has any implication on cloud-init after an
'update'.
Unless your hostname were to change during that update.
I think the best thing for you to do is
a.) stop doing that
b.) figure out why you needed to do it and file a bug.
Basically we do not expect
James,
We believe we have a fix for this now in trunk and will be uploading eventually
to Ubuntu 16.04.
Your use case of running 'cloud-init init' after upgrade (without first running
'cloud-init init --local') is something we're confused by.
Is there a reason that you're doing that? Normally
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
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
** Changed in: open-iscsi (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731907
Title:
skip dep8 test if image is not available
To manage notifications
James,
Chad and I have been unsuccessful in reproducing this issue.
Could you provide some info?
Running 'cloud-init collect' should get most of the info we want.
Were you actually running this on Amazon AWS (as opposed to another
cloud that immitates the EC2 Metadata service) ?
Thanks,
Scott
Seems like this should work:
http://paste.ubuntu.com/25982684/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732964
Title:
dhclient process started by cloud-init-local.service still running
Public bug reported:
I launched an ec2 isntance, ssh'd in and ran 'systemctl status'.
The result is below.
The issue is that the cloud-init spawned temporary dhclient is still around.
It should not be terribly harmful as its script is /bin/true so it wont
ever take down the link itself.
$
** Changed in: cloud-images
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726818
Title:
vagrant artful64 box filesystem too small
To manage notifications about
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
James,
Thanks for taking the time to report this.
We'll look at this asap.
could you post the full /var/log/cloud-init.log ?
Thanks.
Scott
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732917
** Branch linked: lp:~raharper/curtin/trunk.lvmroot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652822
Title:
grub efi doesn't install fs module needed to access root
To manage notifications
Yasuo,
It is not exposed in any way through vagrant.
It is a kernel command line option.
You'd have to edit /etc/default/grub and add it to GRUB_CMDLINE_LINUX_DEFAULT
and then run 'update-grub'.
I had done a quick test and didn't seem to think that it fixed the
issue, but I'd be interested in
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[
I am confused by Stephane's orginal opening statement that
| Prior to the switch to nplan, systems (in my case containers) would
| DHCP for IPv4 and let the kernel do IPv6 auto-configuration whenever a
| router advertisement comes in.
I opened bug 1732002 with information to the contrary.
On my
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
I ended up kill -9'ing the process. and eventually it went on (not even
recording an error).
Then the subsequent 'apt-get autoremove' hung again.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
linux-headers-4.4.0-96
** Description changed:
I've run a dist-upgrade on a system with mdadm installed:
It hangs like this:
+ Setting up iproute2 (4.3.0-1ubuntu3.16.04.2) ...
+ Setting up resolvconf (1.78ubuntu5) ...
+ Setting up lshw (02.17-1.1ubuntu3.4) ...
+ Setting up golang-1.6-src
Public bug reported:
I've run a dist-upgrade on a system with mdadm installed:
It hangs like this:
Setting up python3-update-manager (1:16.04.10) ...
Setting up ubuntu-release-upgrader-core (1:16.04.23) ...
Setting up update-manager-core (1:16.04.10) ...
Processing triggers for resolvconf
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
Bugs, which is subscribed to Ubuntu.
As an 'fyi', newer versions of curtin now have dropped the specific hack for
dirmngr and gpg.
Instead they now use a pid namespace for all processes in the chroot.
This allows us to let the kernel kill off the delinquent processes when their
parent exits.
--
You received this bug notification
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)
--
** Also affects: simplestreams (Ubuntu)
Importance: Undecided
Status: New
** Changed in: simplestreams (Ubuntu)
Importance: Undecided => Medium
** Changed in: simplestreams (Ubuntu)
Status: New => Confirmed
** Changed in: simplestreams (Ubuntu)
Status: Confirmed =>
** Also affects: simplestreams (Ubuntu)
Importance: Undecided
Status: New
** Changed in: simplestreams (Ubuntu)
Status: New => Fix Released
** Changed in: simplestreams (Ubuntu)
Importance: Undecided => High
** Also affects: simplestreams (Ubuntu Artful)
Importance:
** 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
** 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
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
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 configuration
To manage notifications
901 - 1000 of 11836 matches
Mail list logo
