Currently maas sends v1 config to cloud-init. cloud-init converts
that to netplan. MAAS could certainly change change to either
a.) improve the v1 config that it sends to put dns as per-interface
b.) send v2 config with dns per-interface.
I don't think there is reason to justify either of those a
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
--
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/1751797
Title:
dns resolution only works for domains in
Hi.
Just to re-iterate what Robie said.
If you are seeing hashsum mismatch errors on 16.04 or later, something is wrong.
That could be:
a.) you have a proxy in your way, and the proxy cached a bad download.
Apt is recognizing this and not installing it.
That is working as designed.
Note, that http
I'm pretty sure that if you you rm /etc/resolv.conf
and then just write what ever you want in there, it wont get overritten.
mv /etc/resolv.conf /etc/resolv.conf.dist
echo "nameserver 8.8.8.8" > /etc/resolv.conf
On Thu, Mar 8, 2018 at 4:36 PM, Mike Pontillo
wrote:
> We discussed this today and
** No longer affects: maas
** No longer affects: nplan (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Assignee: (unassigned) => Ryan Harper (ra
** Merge proposal linked:
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203
--
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.launchp
** Merge proposal unlinked:
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203
--
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.launc
** Merge proposal linked:
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203
--
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.ne
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
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/1751797
Title:
dns resolution only wor
$ systemd-resolve --status enp0s25
Link 2 (enp0s25)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 10.7.0.1
fdfd::::1
DNS Domain: ~mydomain.com
$ cat
/var/
connection.id: System Ethernet
connection.uuid:72c7fac3-c017-4b76-9954-b4fb08262376
connection.stable-id: --
connection.type:802-3-ethernet
connection.interface-name: --
connection.autoconnect:
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1751797
Title:
NetworkManager incorrect
See my attached log for verification of artful.
--
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 launched by ubuntu
Status in
** Attachment added: "verification log on artful"
https://bugs.launchpad.net/cloud-init/+bug/1734167/+attachment/5081507/+files/lp-1734167-verify-artful.txt
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful
--
You receiv
Public bug reported:
open-iscsi test utilizes overlayroot to boot a cloud-image with root
filesystem on a read-only iscsi server.
The /etc/fstab file in the image looks like this:
LABEL=cloudimg-rootfs /ext4 defaults0 0
#LABEL=UEFI /boot/efi vfatdefaults
I pushed a branch up to
https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/bug/1788188-debug
that Christian and I are trying to get some additional debug information out of
a failure.
--
You received this bug notification because you are a member of Ubuntu
Touch
here is a pastebin of boot with systemd debugging.
http://paste.ubuntu.com/p/vGTRh6WB3B/
--
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/1788188
Title:
transient systemd o
I've hit that 'retrigger' button 2 more times and have not seen failures.
I just did again. Don't know what to do. :-(
--
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/1788188
I uploaded open-iscsi_2.0.874-5ubuntu8 which has the debug code
that we were toying with included. It also includes a fix for
FTBFS bug 1791154.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
Public bug reported:
I haven't verified this, but I believe that ifupdown works through udevadm
hooks.
So udevadm hotplug event -> ifup eth0.
Any subprocesses of a udevadm hook will be restricted by the
systemd-udevd.service
restrictions, which currently are
RestrictAddressFamilies=AF_UNIX AF
This is invalid.
It actually all still works because:
udev hook /lib/udev/rules.d/80-ifupdown.rules calls /lib/udev/ifupdown-hotplug
which calls
systemctl --no-block start $(systemd-escape --template ifup@.service
$INTERFACE)
Then the ifup@.service is what actually brings up the device.
Tha
@xnox,
Are you suggesting the /media/root-ro entry in /etc/fstab line for
/media/root-ro should have x-systemd.DefaultDependencies=no ?
--
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.
** Changed in: maas (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1134036
Title:
Failure when using ssh with a locale tha
Hm...
Our tests show that this is not fixed in cosmic or bionic.
https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/533/console
shows curtin's vmtest failing. Partial output shows:
==
ERROR: test_ipv6_mtu_smaller_t
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Bionic)
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.laun
Public bug reported:
I'm accustomed to hitting 'alt-space' to 'Activate the window menu'
where there are options like 'Always on Top' or 'Always on visible
workspace'.
After an upgrade today I can no longer bring up that menu.
Alt-space simply does nothing. Configuring the keyboard shortcut in
g
i attached as reference
https://hackmd.io/E0ydu7Y7QEe-kroPb6-OOA
at some point we can improve the doc in the debian/tests directory with that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.la
** Description changed:
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
+ 1 minute 30 seconds for the disk to appear,
cloud-init can collect relevant logs with 'cloud-init collect-logs'
that is what we tell people to run (and what gets done with 'ubuntu-bug
cloud-init').
I know that is not exactly what you're after.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Changed in: software-properties (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Medium
--
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/1667725
Title:
[feature request]
decided => Medium
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
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
@mwhudson,
your suggested change seems reasonable to me.
I don't love the use of 'eval', but it seems reasonably safe here.
Instead of quoting you could just reject argv[1] input if it
had characters other than [a-zA-z_.-] . Perhaps that makes
this more difficult.
Also, maybe you should try to '
@Adam,
> See the comment on the linked debian-cd MP from Marc Deslauriers. Note
> that the goal of removing the cloud-image seed is still entirely
> reasonable and doable, openssh-server should just move to livecd-rootfs
> as something always added to cloud images. Done and done. There's no
Your
** 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
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(
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
@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
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
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:
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
** 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-
** Summary changed:
- apport-collect requires python2 or suggests installing already-installed
python3-apport
+ apport-collect requires python2
** Changed in: apport (Ubuntu)
Status: New => Fix Released
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
** Also affects: a
** 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
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 -
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
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
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
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
** 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=
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
> 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
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
** 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
** 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
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
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/
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
** 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
** 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: 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:
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
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
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
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
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
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
** 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
** 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
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
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
** 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
** 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: "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 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
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
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
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
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*[
** Description changed:
[Problem]
The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
10.0
** Summary changed:
- lxc postinst script checks available interfaces, can choose
+ pre-installed lxc in cloud image produces broken lxc (and later lxd)
containers
** Description changed:
[Problem]
The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst pac
can you post user-data that you use to create/populate the template?
--
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/1509747
Title:
Intermittent lxc failures on wily
Statu
** Description changed:
[Problem]
The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
10.0
Public bug reported:
Bug 1509414 describes fallout of inclusion of lxc in cloud images. The initial
inclusion caused 2 issues:
a.) containers created by 'lxc -t ubuntu-cloud' and 'lxd import-images ubuntu
wily' had completely broken networking
b.) all cloud images would have lost access to 10
For reference, bug 1509414 refers to this issue as 'stage 2'.
Serge Hallyn suggested a fix for it in comment 24
(https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/comments/24).
There is other discussion there also as to the viability of that fix.
--
You received this bug notification
I'm marking this verification-done based on comments:
25 : https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/comments/25
23 : https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/comments/23
21 : https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/comments/21
20 :
I've opened bug 1510108 to address 'Stage 2' of this fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
pre-installed lxc in cloud image produces broken lxc (a
** Changed in: lxc (Ubuntu Wily)
Status: New => Confirmed
** Changed in: lxc (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: lxc (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug
** Summary changed:
- [FFE] add mdadm and lvm2 to cloud image
+ add mdadm and lvm2 to cloud image
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1491102
Title:
add mdadm and
Just to be clear, the subject of this bug says 'add multiverse and
-backports', but only multiverse was added.
--
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/9973
** Changed in: lvm2 (Ubuntu)
Status: New => Fix Committed
** Changed in: mdadm (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bug
** Description changed:
maas images utilize cloud-initramfs-dyn-netconf . The way this works is
basically:
* /etc/network/interfaces in image is a link to
../../run/network/dynamic-interfaces
* kernel command line 'ip=' convince the initramfs to bring up networking
using 'ipconfig'
Public bug reported:
In testing use of squashfs images, I found that my initramfs could not mount
the squashfs filesystem.
Paired with overlayroot, squashfs is very nice for testing.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: initramfs-tools 0.120ubuntu5
ProcVersionSignature: Ubuntu 4
** Description changed:
In testing use of squashfs images, I found that my initramfs could not mount
the squashfs filesystem.
Paired with overlayroot, squashfs is very nice for testing.
+
+ We're investigating use of squashfs as a image type for cloud images.
+ Heres example of the changes t
** Description changed:
In testing use of squashfs images, I found that my initramfs could not mount
the squashfs filesystem.
Paired with overlayroot, squashfs is very nice for testing.
We're investigating use of squashfs as a image type for cloud images.
Heres example of the changes t
better link to upstream https://bugs.gnupg.org/gnupg/issue1675
** Bug watch added: bugs.gnupg.org/gnupg/ #1675
http://bugs.gnupg.org/gnupg/issue1675
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://
Public bug reported:
if the initramfs has 'ip=' on the cmdline, it is arguable that we should
bring the respective interface up as indicated.
Currently, initramfs only does this if something thinks it should.
Ie, open-iscsi might do it, or some other things might call
'configure_networking'.
Bu
Marked this as affecting initramfs-tools and cloud-initramfs-tools. only
one of them is needed.
--
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/1463846
Title:
if ip
** Description changed:
if the initramfs has 'ip=' on the cmdline, it is arguable that we should
bring the respective interface up as indicated.
Currently, initramfs only does this if something thinks it should.
Ie, open-iscsi might do it, or some other things might call
'configure_
marked software-properties as 'fix-released, as wily image has:
$ dpkg-query --show software-properties-common
software-properties-common 0.96.10
that depends on python3:any
** Changed in: software-properties (Ubuntu)
Status: New => Fix Released
** Also affects: vim (Debian) via
h
101 - 200 of 562 matches
Mail list logo
