*** This bug is a duplicate of bug 1842320 ***
https://bugs.launchpad.net/bugs/1842320
In case it helps: I just want to add that I had similar issues due to
debug symbols present in my kernel modules (15x initrd size).
--
You received this bug notification because you are a member of Ubuntu
** Changed in: maas
Status: Incomplete => Invalid
--
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/1573982
Title:
LVM boot problem - volumes not activated after upgrade
In MAAS we have provided a work around in LP: #1773698
** Changed in: maas
Milestone: 2.5.0beta1 => 2.5.0beta2
** No longer affects: maas
** No longer affects: maas/2.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: maas
Milestone: 2.5.0 => 2.5.0beta1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in Avahi:
** Changed in: maas/2.4
Milestone: 2.4.2 => 2.4.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in Avahi:
** Changed in: maas/2.4
Milestone: 2.4.1 => 2.4.2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in Avahi:
** Also affects: maas/2.4
Importance: Undecided
Status: New
** Changed in: maas
Milestone: 2.4.x => 2.5.0
** Changed in: maas/2.4
Milestone: None => 2.4.1
** Changed in: maas/2.4
Status: New => Triaged
** Changed in: maas/2.4
Importance: Undecided => High
**
** Changed in: maas
Milestone: 2.4.0beta4 => 2.4.x
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in Avahi:
** Changed in: maas
Milestone: 2.4.0beta3 => 2.4.0beta4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in
no
> Launchpad-Bug-Commenters: andreserl janitor manjo vorlon
> Launchpad-Bug-Reporter: Andres Rodriguez (andreserl)
> Launchpad-Bug-Modifier: Steve Langasek (vorlon)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
U
Public bug reported:
When executing ifconfig, it outputs the whole 10 characters of the
interface name. However, when using ifconfig -s (or ifconfig -a -s) it
doesn't include all the name of the interface (or 10+ characters).
Instead, it outputs only 8 characters of the interface.
** Changed in: maas
Milestone: 2.4.0beta2 => 2.4.0beta3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in
*** This bug is a duplicate of bug 1756846 ***
https://bugs.launchpad.net/bugs/1756846
Thanks to the investigation from Steve, it seems that during the dist-
upgrade process ifupdown was removed due a transient conflict during the
devel cycle. This caused it to be removed. It being removed
https://pastebin.ubuntu.com/p/YPRxSrjHZ9/
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => New
--
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/1761294
cloud-init-output.log after manually rebooting the machine.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
** Attachment added: "cloud-init-output.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+attachment/5101804/+files/cloud-init-output.log
**
** Changed in: maas
Milestone: 2.4.0beta1 => 2.4.0beta2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in
** Changed in: maas
Milestone: None => 2.4.0beta1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737
Title:
[2.3.0-6434] mDNS observer problems
Status in Avahi:
Dear user,
This is an automated message.
We believe this bug report is no longer an issue in the latest version
of MAAS. For such reason, we are making this issue as Won't Fix. If you
believe this issue is still present in the latest version of MAAS,
please re-open this bug report.
** Changed
** Changed in: maas
Importance: High => Medium
** Changed in: maas
Status: Won't Fix => Triaged
** Changed in: maas
Importance: Medium => Low
** Changed in: maas
Milestone: None => 2.4.x
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
n;
> status=New; importance=Critical; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=systemd; component=main;
> status=New; importance=Critical; assignee=None;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerabilit
** Changed in: maas
Importance: Low => High
** Changed in: maas
Assignee: (unassigned) => Mike Pontillo (mpontillo)
** Changed in: maas
Milestone: None => 2.4.0alpha2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: maas
Importance: Undecided => Low
** Changed in: maas
Status: Invalid => Triaged
--
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/1750884
Title:
@Scott,
Sure, we can all improve but I just want to note one thing. The "Silly"
config that MAAS sends to curtin is valid config. That yields valid
configuration in Xenial. Since Curtin is now passing the /same/
configuration to cloud-init, cloud-init is not generating valid
configuration in
@Matthieu,
ubuntu@node01:~$ systemd-resolve google.com
google.com: resolve call failed: No appropriate name servers or networks for
name found
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@Mathieu,
Good catch.
@Scott:
Network config MAAS sent is correect, it is the same config sent to
xenial: https://pastebin.canonical.com/p/rjBgzKjdxR/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This is pretty critical to MAAS as this yield Bionic deployments without
DNS resolution.
** Description changed:
When deploying Bionic, /etc/resolv.conf is not configured correctly,
which leads to no DNS resolution. In the output below, you will see that
netplan config is correctly to the
Public bug reported:
When deploying Bionic, /etc/resolv.conf is not configured correctly,
which leads to no DNS resolution. In the output below, you will see that
netplan config is correctly to the 10.90.90.1 nameserver, but in
resolv.conf that's a local address.
Resolv.conf should really be
ubuntu@node03:~$ systemd-resolve --status --no-pager
Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
Added a team subscriber
** Changed in: python-nacl (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1747460
Title:
[MIR]
FWIW, i have filed:
https://github.com/go-macaroon-bakery/py-macaroon-bakery/issues/47
https://github.com/ecordell/pymacaroons/issues/44
but doubt this would be resolved before Bionic.
** Also affects: python-nacl (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
09:27 < roaksoax> doko: TBH, no idea as i've not looked at what the differences
are, but will take a look
09:38 < doko> roaksoax: maybe you could ask cjwatson about the differences in
python-nacl and python-libnacl, he is one of the Debian uploaders
09:39 < roaksoax> doko: that's what I waas
** Changed in: protobuf (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1626692
Title:
python3 support
Status in
** Summary changed:
- [MIR] py-macaroon-bakery,
+ [MIR] py-macaroon-bakery, protobuf, pyrfc3339
** Description changed:
py-macaroon-bakery
==
1. Availability: all
2. Rationale:
Macaroons is a new form of authorization mechanism. The macaroon bakery
builds on
@I've uploaded the new package. I've tested an upgrade to Xenial to
ensure there are no issues and confirm it is good to go.
** Changed in: maas/1.9
Assignee: Andres Rodriguez (andreserl) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch see
On Wed, Dec 13, 2017 at 6:00 PM Robie Basak <1732...@bugs.launchpad.net>
wrote:
> On Wed, Dec 13, 2017 at 10:34:25PM -0000, Andres Rodriguez wrote:
> > FWIW, this is currently affecting customers who are running MAAS and
> > require livepatch.
>
> It's been af
FWIW, this is currently affecting customers who are running MAAS and
require livepatch.
Comments #11 and #12 above confirm that the patch is enough for the MAAS
needs. Whichever way MAAS decides to check for systemd is up to MAAS and
that is not a reason to block an SRU provided that it does not
** Changed in: maas
Status: Fix Committed => 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/1732522
Title:
[2.3] Ephemeral boot environment does not
** Changed in: maas
Status: Fix Committed => Fix Released
--
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
Title:
[2.3] resolv.conf is not set (during
@Chris,
Can you attach the output of:
maas machine get-curtin-config
And attach the follow curtin log (you can grab that from the UI under
the Installation tab).
Also, this seems an issue widely with Ubuntu.
Curtin is the one that writes this configuration, so marking this as
Incomplete for
I've verified these two manually! Thanks for all the work!
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Also, I've tested this in GMAAS and confirm the fix works!
--
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
Title:
[2.3] resolv.conf is not set (during
Bumping this to critical provided that at this point, this completely
breaks MAAS.
** Changed in: resolvconf (Ubuntu Xenial)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in
@Mark,
I do have access (just tested). I'll give it a try tomorrow! Thanks!
--
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
Title:
[2.3] resolv.conf is not set
** Changed in: maas
Status: Fix Committed => Fix Released
--
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
Title:
[2.3] resolv.conf is not set (during
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
** Changed in: maas
Milestone: 2.3.0 => 2.3.0beta2
--
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
Title:
[2.3] resolv.conf is not set (during commissioning
Public bug reported:
Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set with
the DNS server.
That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network,
FWIW, this issue is still present in older releases. Effectively, if NTP
is installed and configured to access X ntp server and timesyncd would
still try to fallback to ntp.ubuntu.com.
In proxied environments, this will result in ntp.ubuntu.com being
unavailable.
** Also affects: ntp (Ubuntu
@Tyler,
The reason why this wasn't seen before is that previously in Xenial,
cloud-init did not restart 'ntp' with a new config file. Since cloud-
init recently SRU'd a fixed cloud-init that does restart 'ntp' on
overlay, the issue started to show up.
In other words, after a cloud-init bugfix ,
@Frode,
Users running 2.2 *already* have the apparmor=0 work around for
*ephemeral* environments only.
For users running previous versions, we recommend you upgrade
immediately, provided that 2.0 and 2.1 are out of support. If you decide
not to upgrade, your options are:
1. Use a HWE kernel
When using the following kernel (the default Xenial kernel, aka ga-16.04
in MAAS), we see this issue:
4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
When using the HWE kernel (aka hwe-16.04 in MAAS), we do NOT see this
issue:
4.8.0-58-generic
@Tyler,
That's is correct, MAAS 2.2.0+ sends the apparmor=0 for the ephemeral
environments.
That said, however, this affects else who is not using 2.2 (which in
fact, affects customers who are still in 2.1). Also, based on my
testing, it seems that when using hwe-16.04 kernel this doesn't
It seems that this only happens when using ga-16.04 and doesn't when
using hwe-16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1701297
Title:
NTP reload failure
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Critical
--
** Changed in: maas
Status: Fix Committed => Fix Released
--
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/1621507
Title:
initramfs-tools configure_networking()
** Changed in: maas
Status: Fix Committed => Fix Released
--
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/1640147
Title:
[2.1] rsyslog is flooded with "no
** Changed in: maas/2.1
Status: Fix Committed => Fix Released
--
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/1640147
Title:
[2.1] rsyslog is flooded with "no
>From the ML
lease {
interface "enp0s25";
fixed-address 10.1.8.227;
option subnet-mask 255.255.255.0;
option dhcp-lease-time 2592000;
option routers 10.1.8.1;
option dhcp-message-type 5;
option dhcp-server-identifier 10.1.8.1;
option domain-name-servers 8.8.8.8,8.8.4.4;
option
cat $(ps auxw | grep dhclient | grep -o '\-lf.*' | awk '{ print $2 }')
--
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/1664748
Title:
wifi connection drops,
@ Dustin,
Can you attach your dhcpd.conf or at least the relevant sections to see
how this hostmap was configured ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Changed in: maas
Status: Triaged => Fix Released
** Changed in: maas
Milestone: next => None
--
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/1355813
Title:
** Changed in: maas
Milestone: 2.1.2 => 2.1.3
--
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/1629972
Title:
networking stop incorrectly disconnects from (network)
** Changed in: maas
Milestone: 2.1.0 => 2.1.1
--
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/1629972
Title:
networking stop incorrectly disconnects from (network)
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Milestone: None => 2.1.0
--
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/1629972
Title:
** Changed in: maas
Status: Triaged => Fix Released
--
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/1621507
Title:
initramfs-tools configure_networking() fails to
** Changed in: maas
Status: New => Confirmed
** Changed in: maas
Importance: Undecided => Critical
** Tags added: maas-ipv6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1621507
Title:
ipconfig lacks ipv6 support
Status in MAAS:
** No longer affects: maas/1.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1251257
Title:
[SRU] avahi fails in containers
Status in MAAS:
Fix Released
Status in avahi
** Changed in: maas
Status: Fix Committed => Fix Released
--
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/1521618
Title:
[1.9] wrong subnet in DHCP answer when
** Changed in: maas/1.9
Status: Fix Committed => Fix Released
--
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/1521618
Title:
[1.9] wrong subnet in DHCP answer when
** Summary changed:
- wrong subnet in DHCP answer when multiple networks are present
+ [1.9] wrong subnet in DHCP answer when multiple networks are present
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
ok, so I think what the issue is. I found a different rule that would
do:
& ~
However, that means " stop logging anything that matches the last rule",
however, instead of stopping just that rule, it was stopping everything.
The reason why this was stopping everything is because it didn't really
Ok, so MAAS install's an rsyslog config to forward messages from syslog
to /var/log/maas/maas.log. Today we noticed that maas.log was completely
empty, and on further checking, we noticed that syslog was completely
empty as well. The fun fact, however, is that MAAS has not changed its
syslog
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: maas
** Description changed:
- MAAS ships a custom rsyslog.d config which follows:
-
- /etc/rsyslog.d/20-maas ships:
-
- # Log MAAS messages to their own file.
- :syslogtag,contains,"maas"
** Changed in: maas
Milestone: 1.9.2 => None
--
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/1540522
Title:
vfat support broken in initramfs
Status in MAAS:
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Critical
--
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/1567744
Title:
RTNETLINK answers: Numerical result
** Description changed:
- I have a USB NIC that is connected to my xenial system:
+ I have a USB NIC that is connected to my denial system. I tried to
+ create an alias, and after reboot, it wasn't created. When I manually
+ try to bring it up I have the error.
/e/n/i:
auto
Public bug reported:
I have a USB NIC that is connected to my xenial system:
/e/n/i:
auto enx000ec688b79f
iface enx000ec688b79f inet static
address 10.90.90.1
netmask 255.255.255.0
auto enx000ec688b79f:1
iface enx000ec688b79f:1 inet static
address 192.168.100.1
** Changed in: maas
Milestone: 1.9.1 => 1.9.2
--
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/1540522
Title:
vfat support broken in initramfs
Status in MAAS:
policycoreutils (in universe) is installed by default by isc-dhcp-
> server as it is a Recommends
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1546358/+subscriptions
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Serve
** Description changed:
- Policycoreutils is being installed by default, and this dependency is in
- Universe. This should not be a recommends but rather, it should be a
- Suggests, because this is pulling selinux dependencies.
+ Policycoreutils is being installed by default because the package
Public bug reported:
Policycoreutils is being installed by default, and this dependency is in
Universe. This should not be a recommends but rather, it should be a
Suggests, because this is pulling selinux dependencies.
However, it seems that the postinst requires a binary being shipped in
** Changed in: maas
Status: Fix Committed => Fix Released
--
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 user on
** No longer affects: maas
--
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 repository disk format has race conditions
Status in apt package in Ubuntu:
** Changed in: maas
Importance: Undecided = Wishlist
** Changed in: maas
Status: New = Triaged
** Changed in: maas
Milestone: None = 1.8.0
** Changed in: maas
Milestone: 1.8.0 = next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: maas
Milestone: 1.7.1 = 1.7.2
--
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 Utopic Fast Installer
86 matches
Mail list logo
