Public bug reported:
I'm downloading an image, and booting it in kvm via
lp:~ubuntu-foundations-team/create-ubuntu-core-image .
The result is a image that requires graphics to log into. Ie, I'd much rather
use either '-nographic' or '-curses' flags to kvm.
This is much easier to work with
Public bug reported:
When booting the system image, nothing generates ssh host keys.
Normally I think these are created on installation, but for good reason they're
not included in the image.
In cloud imags, cloud-init does this. In other systemd boot scenarios, they're
generated by another
Forwarded upstream https://bugs.g10code.com/gnupg/issue1675 .
** Bug watch added: GnuPG Bugs #1675
https://bugs.g10code.com/gnupg/issue1675
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Public bug reported:
Recent upgrade and reboot/re-login left me with a generally unusable
compiz/unity.
On login, the desktop icons move back and forth several times, I believe this
correlates with ~/.xesssion-errors 'unity main process ended' messages like:
upstart: gnome-keyring main process
For what its worth, this is an older thinkpad (T400). It has older
intel graphics chipset. I'm attaching xorg.0.log for more information.
** Attachment added: xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4174472/+files/Xorg.0.log
--
You received
$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset
OpenGL version string: 2.1 Mesa 10.2.5
Not software rendered:yes
Not blacklisted: yes
GLX fbconfig: yes
** Attachment added: /var/log/kern.log messages from guest login
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176601/+files/guest-kern.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity
** Attachment added: guest's home dir during failed login (log files in
.cache)
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176600/+files/guest-home.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: /var/log/Xorg.0.log from guest login
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1355196/+attachment/4176602/+files/guest-Xorg.0.log
** Changed in: unity (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1355196
Title:
unity crashes on login, compiz cpu
ok. so some updates.
Ben fixed this in the cloud image build process via [1] (commit [2]), and
limited the change to utopic+.
The fix was done by adding a file /etc/sysctl.d/99-cloudimg-ipv6.conf
The problem with this change is described in bug 1352255 and bug
994931. If ipv6 addresses are
** Also affects: ifupdown (Ubuntu Utopic)
Importance: Medium
Status: Confirmed
** Also affects: ifupdown (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: ifupdown (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: ifupdown (Ubuntu Trusty)
I've verified fix-released on utopic. In 2 ways:
a.) set /etc/network/interfaces with:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet6 static
netmask 64
address 2001:db8::1:3
And set a local 'NoCloud' datasource, and then booted
the system to see 'ip -6 addr' shows
** Changed in: curtin (Ubuntu Saucy)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1313550
Title:
ping does not work as a normal
** Description changed:
With trusty, /bin/ping relies on having extended attributes and kernel
capabilities to gain the cap_net_raw+p capability. This allows removing
the suid bit.
However, the tarball cloud images do not preserve the extended
attributes, and thus /bin/ping does not
heres output of a run of 'tmp-acl-bavior':
** Attachment added: example output of running
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1386237/+attachment/4246269/+files/out
** Description changed:
as discovered in bug 1382632 (http://launchpad.net/bugs/1382632), tar's --acl
has
Just to demonstrate a particularly odd behavior:
#!/bin/bash
set -e; set -o pipefail
tmpd=$(mktemp -d)
trap rm -Rf $tmpd EXIT
cd $tmpd; mkdir defaults ex
setfacl --default --modify u::rwx --modify g::r-x --modify other::r-x defaults
setfacl --remove-default ex
xattr_args=--xattrs
** Description changed:
With trusty, /bin/ping relies on having extended attributes and kernel
capabilities to gain the cap_net_raw+p capability. This allows removing
the suid bit.
However, the tarball cloud images do not preserve the extended
attributes, and thus /bin/ping does not
The simple fix, then is:
rm /etc/sysctl.d/10-ipv6-privacy.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1352255
Title:
Impossible to configure network interface
I did a fair amount of debug information including recreation with a
cloud image at lp:~smoser/+junk/lp-1377005 . I'll copy the final comment
here.
ok. so, i now know what happens, and why adding anything before the ipv6
address fixes the problem.
boot happens like this:
* system boot
*
Public bug reported:
I came across this when debugging bug 1352255.
as implemented right now (trusty and utopic) the 'static-network-up' event is
emitted when each 'auto' interface has had *an* address configured, as opposed
to *all* addresses configured.
Heres why:
ifupdown calls runparts on
interestingly enough, modifying the privacy settings via sysctl has some
negative affects if addresses are already up. see diagnosis in bug
1377005 .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
i opened bug 1379427 for the incorrect static-networking bug that i
found when investigating.
setting the use_tempaddr setting ends up wiping existing ipv6 addresses.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown
just for the record changing
sysctl -e net.ipv6.conf.all.use_tempaddr
is what causes the problem. changing 'sysctl -e
net.ipv6.conf.default.use_tempaddr' does not.
changing 0 - 2 or 2 - 0 deletes all existing addresses for an interface.
** Changed in: ifupdown (Ubuntu)
Importance:
I've verified this change fixes the issue with initramfs mounting iscsi targets
. I did this inside of maas.
* basically set up functional maas with some nodes, and daily images of utopic
imported.
from there
### repro
# get some tools
$ apt-get install cloud-image-utils
** Changed in: cloud-init
Status: New = Confirmed
** Changed in: cloud-init
Importance: Undecided = Medium
** Changed in: util-linux (Ubuntu)
Status: New = Confirmed
** Changed in: util-linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification
** Changed in: gnupg (Ubuntu)
Status: New = Confirmed
** Changed in: gnupg (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
** No longer affects: cloud-init (Ubuntu)
--
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/1347020
Title:
trusty host - utopic lxc container cloudimage boot with systemd does
marked this 'triaged' in cloud-init while still not really relevant.
Ben Howard has disabled the privacy extensions in cloud images in 14.10, and
the plan is to just do the same for 14.04.
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Public bug reported:
There is a race condition with gnupg --verify when multiple processes
act at the same time.
strace helps cause the race condition (probably by slowing thing down)
gpgv does not seem to have the issue.
The result is you will see transient verify failures with output like
** Attachment added: script that shows the issue
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1342807/+attachment/4154140/+files/race-verify
** Description changed:
There is a race condition with gnupg --verify when multiple processes
act at the same time.
strace helps cause
updated race-verify a bit. no functional change.
** Attachment added: script that shows the issue
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1342807/+attachment/4154169/+files/race-verify
** Attachment removed: script that shows the issue
*** This bug is a duplicate of bug 1379427 ***
https://bugs.launchpad.net/bugs/1379427
** This bug has been marked a duplicate of bug 1379427
/etc/network/if-up.d/upstart emits static-network-up to early
--
You received this bug notification because you are a member of Ubuntu
Touch
To rule out kernel involvement, I took the same 'root-image' and ran
this on utopic:
# these downloaded trusty versions
[https://launchpad.net/ubuntu/+source/e2fsprogs]
$ sudo dpkg -i e2fslibs_1.42.9-3ubuntu1_amd64.deb
$ sudo dpkg -i e2fsprogs_1.42.9-3ubuntu1_amd64.deb
$ resize2fs -P
Public bug reported:
I have a disk image created as part of lp:maas-images.
This process takes a cloud image (http://cloud-images.ubuntu.com) such as
http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64.tar.gz
.
Inside that .tar.gz is a .img file. The .img file is operated
Ted, thanks for your response, and sorry for the spam.
Can you just verify that this specific bit seems correct:
| On that derived image, I see 'resize2fs -P' numbers like:
| trusty: 274500
| utopic: 358400
| vivid: 358400
| The 83900 blocks out of a 358400 seems significant (23% of the
Public bug reported:
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'
example:
** Patch added: suggested fix.
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432821/+attachment/4348329/+files/bug-1432821.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Tomorrow I'll look into adding code in systemd package that would
basically do what the open-iscsi job did previously.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
** Changed in: ubuntu
Status: New = Confirmed
** Changed in: ubuntu
Importance: Undecided = High
** Package changed: ubuntu = systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thomas,
Yeah, you're right about 'manual devname'. Seems unnecessary.
wrt you not reproducing it, I'm seeing the issue
a.) when using systemd as init
b.) when configuring networking from the initramfs
the interface being used is already up, and in this case cant be bounced
when init runs from
possibly related...
likely related, I find that on this system
$ ls /run/network/ifstate
ls: cannot access /run/network/ifstate: No such file or directory
$ ifquery --state --all
Segmentation fault (core dumped)
$ sudo ifquery --state --all
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr
** Patch added: proposed fix
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432829/+attachment/4349395/+files/lp-1432829.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I've made this affect systemd as that is where I have the fix for it.
I could fix in open-iscsi as it was in upstart, but I think adding general
infrastructure that considers open-iscsi is more sane than open-iscsi playing
around with tricking ifupdown.
** Package changed: resolvconf (Ubuntu)
Public bug reported:
As seen in the failed systemd adt test at [1], installing 'upstart-bin'
and then booting a system with 'init=/sbin/upstart' does not result in a
fully functional system. The problem is that there are many upstart
jobs provided by 'upstart' package that are essential to
Hi,
I dont actually know why 219-4ubuntu7 would fix the problem.
I think it probably just change timing of a very small race window.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Summary changed:
- something deleting /run/network after during boot
+ something deleting /run/network after initramfs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
So, thanks to xnox.
/lib/systemd/system/ifup@.service
has 'RuntimeDirectory=network'
So that is what is killing /run/network .
He suggested we should remove this from ifup@.service and ship a file in
/usr/lib/tmpfiles.d that does:
d /run/network 0755 root root -
--
You received this bug
Per mvo, there is apparently by-hash support in debian experimental with some
references seen at
https://github.com/Debian/apt/blob/debian/experimental/apt-pkg/acquire-item.cc#L1222
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
relevant changelog in debian:
* Implement simple by-hash for apt update to improve reliability of
the update. Apt will try to fetch the Packages file via
/by-hash/$hash_type/$hash_value if the repo supports that.
- add APT::Acquire::$(host)::By-Hash=1 knob
- add
I opened bug 1430011 as a request for launchpad to gain the ability to
create /populate by-hash mirrors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/972077
Title:
apt
** Also affects: schroot (Ubuntu)
Importance: Undecided
Status: New
** Changed in: schroot (Ubuntu)
Importance: Undecided = High
** Changed in: schroot (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Just realized, that ideally 'apt-get update' would respect headers that were
put in place by the source.
$ wget -S -q http://azure.archive.ubuntu.com/ubuntu/dists/vivid/Release -O
/dev/null
HTTP/1.1 200 OK
Date: Tue, 31 Mar 2015 13:32:55 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified:
this particular system (in azure) has io that rivals that of floppy disks, so
the times are more dramatic.
you're correct in that the information is cached, and that is in general a good
thing, but if I ssh to a system only once a day, then every time i do it, i hit
this penalty.
thats in
Public bug reported:
If i launch a new cloud instance, and then ssh to it, my ssh login
blocks, stopping me from doing useful work while '/usr/lib/update-
notifier/apt-check' runs.
By far, the biggest offender of this slow login is
/usr/lib/update-notifier/apt-check.
To demonstrate, a fresh
just copying description from my duplicate bug as i think its probably /
possibly useful
As seen in the failed systemd adt test at [1], installing 'upstart-bin'
and then booting a system with 'init=/sbin/upstart' does not result in a
fully functional system. The problem is that there are many
-- adt --
Note, my adt runs so far have failed each time (and after 30+ minutes)
The last last failure due to guest running out of space, so changed to 20G
(default 4)
# per http://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test
sudo addgroup kvm
sudo adduser $(id
Public bug reported:
In many cases (juju, lxc containers .. ) we find ourselves in the
position of not knowing if the apt-cache has been udpated recently. So,
you either risk not doing it, or do it and it takes some time and
generates load.
so long story short, you always run 'apt-get update'
I've recreated this in a cloud image.
See the steps to do so here in this attachment.
** Attachment added: description of how to recreate in cloud image
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264/+attachment/4353785/+files/notes.txt
--
You received this bug notification
$ echo now: $(TZ=GMT date); wget -S -q
http://azure.archive.ubuntu.com/ubuntu/dists/vivid/Release -O /dev/null
now: Fri Apr 3 14:37:31 GMT 2015
HTTP/1.1 200 OK
Date: Fri, 03 Apr 2015 14:37:31 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified: Fri, 03 Apr 2015 14:28:00 GMT
ETag:
** Patch added: fix applied to vivid
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380759/+files/lp-1446767-vivid.diff
** Attachment removed: nic-go-crazy: randomly rename nics for dhclient noise
** Attachment added: ifup-loop: loop over ifdown / ifup for a nic to cause
dhclient failure
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380761/+files/ifup-loop
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Attachment added: nic-go-crazy: randomly rename nics for dhclient noise
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380760/+files/nic-go-crazy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
given 3 nics eth0, eth1, eth2
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
while that in its early phases, if eth1 is renamed a race condition can
cause dhclient to exit failure.
example, while running attached 'nic-go-crazy' on
** Attachment added: nic-go-crazy: randomly rename nics for dhclient noise
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380696/+files/nic-go-crazy
** Changed in: isc-dhcp (Ubuntu)
Status: New = Confirmed
** Changed in: isc-dhcp (Ubuntu)
Importance:
** Description changed:
given 3 nics eth0, eth1, eth2
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
while that in its early phases, if eth1 is renamed a race condition can
cause dhclient to exit failure.
+
+ This can happen in real life
** Patch added: patch for trusty
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380752/+files/lp-1446767-trusty.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
I've also put these attached recreate programs and the original kvm boot
recreate at lp:~smoser/+junk/lp128/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1446767
The solution here was pulled from
https://bugzilla.redhat.com/show_bug.cgi?id=449946
The patch really just makes linux use getifaddrs rather than reading
/proc/net/dev for information.
The change has been in place in fedora for ~ 3 years, so that should
stand as some testimony.
** Bug watch
** Changed in: cloud-utils (Ubuntu Vivid)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1427275
Title:
clean cloud images of python2
landscape-client removed from wily cloud-image seed.
** Changed in: landscape-client (Ubuntu)
Status: Confirmed = Fix Committed
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
host $ rel=vivid serial=20150422
host $
url=http://cloud-images.ubuntu.com/releases/$rel/release-$serial/ubuntu-14.04-server-cloudimg-amd64-disk1.img
host $ img_dist=$rel-$serial-amd64.img.dist
host $ img=${img_dist%.dist}
## host
host $ pkgs=qemu-utils qemu-system-x86 cloud-image-utils
host $
## host system is vivid, trusty would also do
host $ rel=trusty ; serial=20150417
host $
url=http://cloud-images.ubuntu.com/releases/$rel/release-$serial/ubuntu-14.04-server-cloudimg-amd64-disk1.img
host $ img_dist=$rel-$serial-amd64.img.dist
host $ img=${img_dist%.dist}
host $ pkgs=qemu-utils
For anyone else hit by this, the fix still requires you to turn it on.
echo Set probe_interfaces false | sudo tee -a /etc/sudo.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
With some other work that I was doing, I found bug 1272414
it seems that getifaddrs() is somewhat slow when lots of interfaces are used.
so this could have a bit of a performance impact in some places. that said,
dhclient is not likely a heavy use path.
--
You received this bug notification
took an initial stab at vim, and then was pointed at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729924
which is debian bug to get python3 support.
just linking here.
** Bug watch added: Debian Bug tracker #729924
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729924
--
You received
point of reference:
$ sudo apt-get remove python
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
landscape-client landscape-common python python-apt python-characteristic
python-chardet python-configobj
** Also affects: vim (Ubuntu)
Importance: Undecided
Status: New
** Changed in: vim (Ubuntu Vivid)
Status: New = Confirmed
** Changed in: vim (Ubuntu Vivid)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I ran this on a fresh cloud instance.
$ cat /etc/cloud/build.info
build_name: server
serial: 20150403.2
$ py2pkgs=$(dpkg -l | grep python | grep -v python3 | awk '{print $2}')
$ for p in $py2pkgs; do
out=$(sudo apt-get remove --dry-run $p 21); pkgs=$(echo $out | awk '$1 ==
Remv $2 != p {
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
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'.
Public bug reported:
provided is user-data that should write:
[stdout] Tue, 23 Jun 2015 20:17:52 + == successfull boot 1 ===
to the console on the first boot.
currently in wily, rc.local's output is not being written to the
console, so you wont see this.
Related bugs:
* bug
** Description changed:
provided is user-data that should write:
[stdout] Tue, 23 Jun 2015 20:17:52 + == successfull boot 1 ===
to the console on the first boot.
currently in wily, rc.local's output is not being written to the
console, so you wont see this.
-
Public bug reported:
per https://www.debian.org/doc/manuals/debian-faq/ch-customizing.en.html
| The rc.local script is executed at the end of each multiuser runlevel.
Generally speaking people expect rc.local to be run as the last thing
in boot.
currently it is being run by systemd much
you can test easily enough on a local vm.
previously output of things run in rc.local went to wherever /dev/console went.
that meant if you ran 'echo hello world' from rc.local when
'console=ttyS0' on the kernel command line, you'd dsee 'hello world' on
the serial console.
this is important to
** Changed in: curtin
Status: Confirmed = Fix Committed
** Changed in: curtin (Ubuntu)
Status: Confirmed = Fix Released
** No longer affects: curtin (Ubuntu Saucy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
A discussion that has come up before, but I figured I'd file a bug.
When you 'apt-get install some-packages' often times:
a.) update-initramfs is called more than once for the same kernel
b.) update-initramfs might not even be called (such as in bug 1466960).
some
** 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
** Changed in: maas-images
Status: Confirmed = Fix Released
--
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/1391354
Title:
Failure to boot ephemeral image for
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.
*** This bug is a duplicate of bug 525674 ***
https://bugs.launchpad.net/bugs/525674
** This bug has been marked a duplicate of bug 525674
apt-check hangs, preventing login via SSH
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Just for clarity, this can be marked fix-released in util-linux when we
get any upstream release 2.26.2.
--
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/1474090
Title:
util-linux trunk is now fixed for both of the issues above.
I've fixed this in cloud-utils by using gdisk unless sfdisk = 2.26.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
** Summary changed:
- ppc64 cloud images boot only once
+ growpart breaks ppc64 images / sfdisk changes partition type
** Description changed:
rebooting a wily cloud image under ppc64 qemu fails to come back up.
also power off then start causes this issue.
It ends in a SLOF prompt
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu)
Status: New = Confirmed
** Changed in: util-linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch
** 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
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
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
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
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 :
1 - 100 of 557 matches
Mail list logo
