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
t; Launchpad-Bug: product=maas; productseries=2.3; milestone=2.3.1; status=In
> Progress; importance=High; assignee=andres...@ubuntu-pe.org;
> Launchpad-Bug: product=maas-images; status=Fix Released;
> importance=Critical; assignee=lee.tra...@canonical.com;
> Launchpad-Bug: distributi
FWIW, I did a bit of extra testing. I killed maas' rackd (which provides
PXE). Rebooted the machine and I saw:
1. It attempted to PXE boot multiple times (like a lot)
2. It eventually gave up and booted from disk
So it successfully booted into the deployed OS.
I noticed that the curtin
5a28802797729aedf99dcd37
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl bladernr cyphermox jwezel ltrager
> narindergupta raharper rodsmith vorlon
> Launchpad-Bug-Reporter: Rod S
** 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
Bugs, which is subscribed to Ubuntu.
** Changed in: maas
Status: Triaged => In Progress
** Changed in: maas/2.3
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments
.
I'm making this change in MAAS as a working work around.
** Changed in: maas
Status: Invalid => Triaged
** Changed in: maas
Importance: Critical => High
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification be
nassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Boot enabled
To manage notifications about this bug
So I've enabled secure boot on my Intel NUC's and have *not* used to
workaround in #36, and the machines deployed just fine (that is, they
pxe boot off MAAS and they are told to load the shim). The same scenario
is when using workaround in #36.
That said, the interesting bit is I remember testing
** Changed in: maas
Importance: Undecided => Low
** Changed in: maas
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750884
Title:
[2.4, bionic]
@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
** Also affects: django-piston3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: django-piston3 (Ubuntu)
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: django-piston3 (Ubuntu)
Status: New => Triaged
--
You received this bug notifi
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
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750884
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
@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
Bugs, which is subscribed to Ubuntu.
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
MAAS sends a debconf selection to curtin, so that curtin tells grub to
not update the nvram. The information that's required is:
1. The curtin config sent to curtin (maas machine get-curtin-config
)
2. The installation log (you can grab both the UI/API)
3. The *actual* debconf selection set on
** Changed in: maas/2.2
Status: Triaged => Won't Fix
** Changed in: maas/2.2
Milestone: 2.2.3 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
Grub package upgrades
Added a team subscriber
** Changed in: python-nacl (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747460
Title:
[MIR] py-macaroon-bakery, protobuf,
** Changed in: maas
Milestone: None => 2.4.0alpha2
** Also affects: maas/2.3
Importance: Undecided
Status: New
** Changed in: maas/2.3
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas/2.3
Milestone: None => 2.4.0alpha2
** Changed in:
** Changed in: maas
Milestone: 2.4.0alpha1 => 2.4.0alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655447
Title:
IEEE indexes in netaddr package may not match data in ieee-data
package
Undecided => High
** Changed in: maas/2.3
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Importance: Undecided => High
** No longer affects: maas/2.3
** Changed in: maa
roaksoax@rivals:/var/lib/maas/boot-resources/current/ubuntu/amd64$ md5sum
hwe-16.04-edge/xenial/daily/boot-kernel
e82babf4ccdef259c29e932a099416b2 hwe-16.04-edge/xenial/daily/boot-kernel
roaksoax@rivals:/var/lib/maas/boot-resources/current/ubuntu/amd64$ md5sum
generic/xenial/daily/boot-kernel
Can you provide /var/log/maas/rackd.log when the machine is PXE booting
and the MAC address of the PXE interface?
** Changed in: maas (Ubuntu)
Status: New => Incomplete
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Incomplete
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
Also, MAAS maintainers is now a bug subscriber.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746772
Title:
[MIR] pymacaroons, python-libnacl
To manage notifications about this bug go to:
As per comments from cjwatson, setting it as New:
09:42 < cjwatson> different upstream projects with incompatible APIs
09:43 < cjwatson> more or less similar functions
09:43 < cjwatson> but AIUI switching from one to the other is basically a
rewrite
** Changed in: pymacaroons (Ubuntu)
Hi Scott,
What was the state of the machine when it rebooted ?
When it rebooted, did it PXE boot again ?
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748875
Title:
Unable to deploy Bionic on bare-metals with MaaS 2.3.0
To manage
** Also affects: maas-images
Importance: Undecided
Status: New
** Branch linked: lp:~smoser/maas-images/trunk.lp1749019-re-add-cloud-
intramfs-dyn-netconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The image is: 20180210
** Changed in: maas (Ubuntu)
Status: Confirmed => Invalid
** Attachment added: "overlay.png"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1748875/+attachment/5053789/+files/overlay.png
--
You received this bug notification because you are a member of
** Summary changed:
- Failed Deployment after timeout trying to retrieve grub cfg
+ High IO on the system can cause MAAS to not provide PXE config in a timely
manner (less than 30 secs)
** Changed in: maas
Status: New => Triaged
** Tags added: performance
** Summary changed:
- High IO
and fwiw, I'm not saying this is *the* solution for a problem like this one
where there is IO starvation. But it is definitely a step forward.
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer
--
You received this bug notification because
> https://www.enodev.fr/posts/emulate-a-slow-block-device-
> with-dm-delay.html
> >
> > https://www.kernel.org/doc/Documentation/device-mapper/delay.txt
> >
> > On Tue, Feb 6, 2018 at 5:06 PM, Jason Hobbs <jason.ho...@canonical.com>
> wrote:
> >> On Tu
chpad-Bug-Commenters: andreserl blake-rouse cgregan janitor
> jason-hobbs mpontillo vorlon
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Jason Hobbs (jason-hobbs)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
@Jason,
I'm comparing pb in #79 vs pb in #90
#79 (non-patched): https://paste.ubuntu.com/26530737/
#90 (patched with lru_cache): https://paste.ubuntu.com/26531873/
Examples I see in #79:
14:02:ec:42:38:dc # makes 9 requests. on line 160+
14:02:ec:42:28:70 # 8 requests on line 72
/
>
> So it seems that changing the CPU limits for the VMs doesn't change
> the results drastically, which lines up with the data showing CPU
> utilization never gets over 50%.
>
> Jason
>
>
> On Mon, Feb 5, 2018 at 10:19 PM, Andres Rodriguez
> <andres...@ubuntu-pe.org
-hobbs
> mpontillo vorlon
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Jason Hobbs (jason-hobbs)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Teleco
t=maas; milestone=2.4.x; status=New;
> importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=grub2; component=main;
> status=In Progress; importance=Medium; assignee=mathieu...@gmail.com;
> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine patch
&g
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl blake-rouse cgregan jason-hobbs
> mpontillo vorlon
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Jason Hobbs (jason-hobbs)
> Launchpad-Message-Rationale: Subscriber
On Tue, Feb 6, 2018 at 11:24 AM, Jason Hobbs <jason.ho...@canonical.com>
wrote:
> On Mon, Feb 5, 2018 at 4:07 PM, Andres Rodriguez
> <andres...@ubuntu-pe.org> wrote:
> > I think there's a misunderstanding on how the network boot process
> happens:
> > Let's look a
** Changed in: protobuf (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626692
Title:
python3 support
To manage notifications about this bug go to:
** 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
sage in
the current conditions, and that's data worth gathering to be able to
better support you in the future).
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer
--
You received this bug notification because you are a member of Ubuntu
Bugs,
t 3:27 PM, Andres Rodriguez
> <andres...@ubuntu-pe.org> wrote:
> > @Steve,
> >
> > MAAS already has a mechanism to collapse retries into the initial
> request.
> > In this case, it is the rack that grabs the requests and makes a request
> to
> > the
Commenters: andreserl blake-rouse cgregan jason-hobbs vorlon
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Jason Hobbs (jason-hobbs)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
@Jason,
On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs <jason.ho...@canonical.com>
wrote:
> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
> <andres...@ubuntu-pe.org> wrote:
> > No new data was provided to mark this New in MAAS:
> >
> > 1. Changes to the
@Jason,
On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs <jason.ho...@canonical.com>
wrote:
> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
> <andres...@ubuntu-pe.org> wrote:
> > No new data was provided to mark this New in MAAS:
> >
> > 1. Changes to the
s)
> Launchpad-Bug-Modifier: Steve Langasek (vorlon)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer
--
You received this bug notification because
No new data was provided to mark this New in MAAS:
1. Changes to the storage seem to have improved things
2. No tests have been run with fixed grub that have caused boot failures.
3. AFAIK, the VM config has not changed to use less CPU to compare results and
whether this config change causes the
Public bug reported:
py-macaroon-bakery
==
1. Availability: all
2. Rationale:
Macaroons is a new form of authorization mechanism. The macaroon bakery builds
on pymacaroons, which allows it working at a higher level.
In order for MAAS (and other projects) to support macaroon
** Changed in: ubuntu
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/1747328
Title:
[needs-packaging] python-libmaas
To manage notifications about this
** Changed in: ubuntu
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: ubuntu
Status: New => In Progress
** Changed in: ubuntu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bu
Public bug reported:
Please package python-libmaas. This is a python3 asyncio python client
library for Canonical MAAS.
URL: https://github.com/maas/python-libmaas
License: AGPL-3.0+
Notes: Python client library for MAAS.
** Affects: ubuntu
Importance: Undecided
Status: New
**
I've tested and I can confirm it made just 1 request instead of 4. I
think now we need to test it in Jason's environment to see the
differences.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743249
** Attachment added: "tcpdump.pcap"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1743249/+attachment/5047711/+files/tcpdump.pcap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743249
@Steve,
On Thu, Feb 1, 2018 at 1:49 PM, Steve Langasek <steve.langa...@canonical.com
> wrote:
> On Thu, Feb 01, 2018 at 06:15:31PM -0000, Andres Rodriguez wrote:
> > @Jason,
>
> > Packet 90573 doesn't seem to me as an indication of what you are
> > describing. Wha
@Jason,
Did you expand the "production environment" section?
Memory (MB) CPU (GHz) Disk (GB)
Region controller (minus PostgreSQL)20482.0 5
PostgreSQL 20482.0 20
Rack controller 20482.0 20
Ubuntu Server (including logs) 512 0.5 20
--
You
Oh I see what you mean, yeah ignore the GHz section, that's wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743249
Title:
Failed Deployment after timeout trying to retrieve grub cfg
To
@Jason,
I would give MAAS at least 6 CPU's.
2 for Region
2 for Postgres
2 for Rack.
I would even recommend 4 for region instead of just 2, as MAAS runs 4
region processes. So that would be a total of 8.
[2]: https://docs.ubuntu.com/maas/2.3/en/#minimum-requirements
--
You received this bug
@Jason,
Packet 90573 doesn't seem to me as an indication of what you are
describing. What I see is this:
1. grub makes ~30 requests for PXE config on grub.cfg-, after which it
gives up because it didn't receive a response.
2. grub moves on and requests grub.cfg-default-amd64, and it receives a
** Description changed:
+ pymacaroons
+ =
+
1. Availability: all
2. Rationale:
macaroon is a new dependency that MAAS will use. This provides the library
for macaroon based authentication, which MAAS will use for the support
remote/centralized authentication.
3.
*** This bug is a duplicate of bug 1376483 ***
https://bugs.launchpad.net/bugs/1376483
** This bug has been marked a duplicate of bug 1376483
AttributeError: 'Port' object has no attribute 'socket'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: grub2 (Ubuntu)
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/1743249
Title:
Failed Deployment after timeout trying to retrieve grub cfg
** Changed in: freeipmi (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052056
Title:
[FFe] [MIR] freeipmi
To manage notifications about this bug go
Public bug reported:
1. Availability: any
2. Rationale:
uvloop is a new dependency that MAAS will use (in the next upload). This
provides asyncio event loop for MAAS to improve performance.
Note that this is required on MAAS 2.4+, which will be uploaded to the
archive soon, but doing this MIR
** Summary changed:
- Trusty deployments fail when custom archives are configured
+ Trusty deployments fail when custom archive keys are configured
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/336284
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743966
Title:
Trusty deployments fail when custom
For posterity, MAAS trusty configuration uses package_mirrors to change
the archive the machines should access. Such configuration does not
support specifying a key for a custom mirror.
That said, the deployed machine will end up with the correct
configuration, but the deployment ephemeral
** Changed in: maas
Status: In Progress => Triaged
** Merge proposal unlinked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/336284
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: maas
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743966
Title:
Trusty deployments fail when custom archives are configured
To manage
@Kiko,
I've tested a deployment of trusty and confirm that the deployed system
does end up with the configuration of the custom repository. This is
because the configuration happens by curtin.
However, the difference between trusty and xenial is that the custom
repository is not available in the
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743966
Please att h logs from apt both the term and the history.
** Changed in: maas (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679322
Title:
maas-dhcp
Can you provide a way to reproduce this, or show us the exact steps
followed ?
** Changed in: maas (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741179
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037964/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743595
Title:
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037963/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743595
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037965/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743595
Title:
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743595/+attachment/5037962/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743595
Title:
Public bug reported:
ubuntu@wrlsrvr321:~$ sudo -i
root@wrlsrvr321:~# lsmod
Module Size Used by
ipmi_devintf 20480 0
iscsi_tcp 20480 0
libiscsi_tcp 24576 1 iscsi_tcp
libiscsi 53248 2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi
Based on the comments above, this doesn't really seem to be an issue
with MAAS, but rather an issue with SSH and/or postgres. I've marked
this bug as incomplete for MAAS until we (or someone else) can confirm
this is an issue with MAAS.
** Changed in: maas
Status: Triaged => Incomplete
**
@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
Bugs, wh
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
@Rod,
Any chance you can test the work around of comment #36. You will need to
manually modify a file under:
/usr/lib/python3/dist-
packages/provisioningserver/templates/uefi/config.local.amd64.template
And then restart maas-regiond & maas-rackd.
Thanks!
--
You received this bug notification
Just to confirm that the verification as per the bug description has
been done!
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial verification-needed-zesty
** Tags added: verification-done verification-done-artful
verification-done-xenial
Hi Dimitrii,
This request seems like something we have never seen before. This
doesn't seem to be quite a complex thing to do. Right now, this is and
never has been in our plans to implement. This is also something that
has never come up before.
I'm going to mark this as a wishlist, and
** Description changed:
- Trusty uses upstart by default, and installing snapd (e.g. for livepatch
- purposes), pulls systemd too. In this setup, upstart is _not_ replaced
- by systemd, but MAAS "detects" systemd as init because of the existence
- of /run/systemd/system:
+ [impact]
+ Since Trusty
As per Rod's comments, I'm re-opening the grub task.
** Changed in: maas-images
Status: Fix Committed => Fix Released
** Changed in: grub2 (Ubuntu)
Status: Won't Fix => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=ipxe; component=main; status=Fix Released;
> importance=Undecided; assignee=None;
> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker cdo-release-blocker
> foundations-engine internal patch verification-done-xenial
> v
Seems someone needs to reject/remove the previous upload (from proposed)
so the new upload doesn't get rejected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
Title:
[SRU] iPXE doesn't
I've uploaded a new version of the package fixing the FTBFS using the
patch from the Debian bug referenced above from Steve.
Debian fixed this issue by getting a new upstream checkout of iPXE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm that ipxe is FTBFS in Zesty (without the patch).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
Title:
[SRU] iPXE doesn't handle NAK requests when multiple DHCP server's
So to clarify, MAAS pxe config searches & chainloads
/efi/ubuntu/shimx64.efi. It seems here the issue is with the shim. As
per Rod's comments:
"Changes to Shim/GRUB so that it works in this configuration. This used
to be the case, but the Shim/GRUB configuration has been tightening
security,
** Changed in: maas
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Boot enabled
To manage notifications about this
@Rod,
Can you retry this URL as a different images source:
http://162.213.35.187/proposed/streams/v1/index.json
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when
This is the part of the buildlog... looks like may be unrelated to the
change.
arch/x86/drivers/xen/hvm.c arch/x86/drivers/hyperv/hyperv.c
arch/i386/drivers/net/undirom.c arch/i386/drivers/net/undinet.c
arch/i386/drivers/net/undionly.c arch/i386/drivers/net/undi.c
** No longer affects: maas (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To manage notifications about
301 - 400 of 4346 matches
Mail list logo
