** Changed in: orchestra (Ubuntu)
Status: Confirmed => 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/834185
Title:
Orchestra should request the localnet for squid
To manage notific
** Changed in: maas (Ubuntu)
Status: Fix Released => Confirmed
** Also affects: maas
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/1281758
Title:
Marking Verification-done. Upgrade path has been verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509147
Title:
[SRU] M
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: verification-failed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Changed in: maas
Status: Fix Committed => 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/1379567
Title:
maas-proxy is an open proxy with no ACLs; it should add networks
autom
** Changed in: maas
Status: Fix Committed => 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/1570606
Title:
[2.0] subnet.list: list index out of range error when using a /31
subn
** Changed in: maas
Status: Fix Committed => 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/1521618
Title:
[1.9] wrong subnet in DHCP answer when multiple networks are present
To
** Changed in: maas
Status: Fix Committed => 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/1356012
Title:
maas incorrectly overmanages DNS reverse zones
To manage notifications
** Changed in: maas
Status: Fix Committed => 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/1590081
Title:
twisted's conch does not support ed25519 and ecdsa ssh public keys
To m
** Changed in: maas
Status: Fix Committed => 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/1551730
Title:
error deleting node
To manage notifications about this bug go to:
https
** Changed in: maas
Status: Fix Committed => 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/1553176
Title:
BIND ignores nanoseconds field in timestamps, fails to load newer
vers
Hi Dan,
Can you please provide exact instructions on how you set debconf options
and how you proceed to run the install?
THanks.
** Changed in: maas (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
So after banging my head a while trying to find out why this wasn't
working for you, I realized that you were deploying Ubuntu 14.04.
The ability to disable_pockets was introduced in MAAS 2.1, and will only
work when deploying Xenial+. This is because MAAS depends on cloud-init
to do such configur
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: cloud-init (Ubuntu Trusty)
Importance: Undecided
@Tom,
All third party OS' are deployed with the latest LTS ephemeral image or
the one that is default for commissioning.
There are multiple reasons why we always deploy a Ubuntu based OS' with
the same ephemeral image. Examples:
1. If you deploy 'Trusty' with Xenial ephemeral on a hardware for w
For the second part of my last comment, I've filed:
https://bugs.launchpad.net/maas/+bug/1664384
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664248
Title:
Can't disable a backports pocket when d
Hi Dustin,
I have, /personally/ not seen this type of behavior myself. However, it
is kind of strange that the wifi connection would just drop when a lease
is renewed... that would seem like a bug in network manager to me
That said, I think it is worth investigating on our side.
--
You rece
** Changed in: maas (Ubuntu)
Status: Triaged => Fix Released
** Changed in: maas (Ubuntu Trusty)
Status: Triaged => 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/1310846
Ti
*** This bug is a duplicate of bug 1660188 ***
https://bugs.launchpad.net/bugs/1660188
Hi Dustin,
Have you tried adding a device via the 'Device' subtab under 'Nodes'?
Go to Nodes > 'Devices' > 'Add Device', Add your new device with a
'Static' IP assignment and that should do. That said, thi
*** This bug is a duplicate of bug 1660188 ***
https://bugs.launchpad.net/bugs/1660188
Also, I think what you want is captured in:
https://bugs.launchpad.net/maas/+bug/1661879
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
*** This bug is a duplicate of bug 1660188 ***
https://bugs.launchpad.net/bugs/1660188
Also, being able to have "details" for a device is captured under:
http://launchpad.net/bugs/1660188
** This bug has been marked a duplicate of bug 1660188
[2.2b1] Devices cannot be edited in the device
cat $(ps auxw | grep dhclient | grep -o '\-lf.*' | awk '{ print $2 }')
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664748
Title:
wifi connection drops, reconnects every 10 minutes
To manage noti
@ 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664748
Title:
wifi connection dro
>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 br
** Changed in: maas (Ubuntu)
Status: Incomplete => Triaged
** Also affects: maas
Importance: Undecided
Status: New
** No longer affects: maas (Ubuntu)
** Changed in: maas
Milestone: None => 2.2.0
** Changed in: maas
Importance: Undecided => Medium
** Changed in: maas
Tom,
1. Check that /etc/maas/rackd.conf does not point to 'localhost'.
Instead, make sure that it points to an IP address of the Region
Controller that the machines can access to (you'll need to restart maas-
rackd: sudo service maas-rackd restart).
2. Once you do that, attempt to deploy a machin
Actually, If you could:
1. Deploy trusty, attach log as above once 'Failed Deployment' or
'Deployed' (maas node-results read system_id=
result_type=1 | grep data | cut -d"\"" -f4 | base64 --decode)
2. Do the same when deploying Xenial.
--
You received this bug notification because you are a me
@Mateusz
What's the output of rackd.conf vs regiond.conf ?
If rackd.conf points to localhost and regiond.conf points to a different
IP address, then the metadata url will be the one of regiond.conf. To
properly configure this, you need to change rackd.conf to point to an IP
address.
That said, t
** Changed in: maas (Ubuntu)
Assignee: MAAS (maas) => (unassigned)
** Changed in: maas
Status: Triaged => Confirmed
** Changed in: maas
Milestone: None => next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: maas
Importance: Undecided => Wishlist
** Changed in: maas (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: maas
Milestone: None => next
** Changed in: maas
Status: New => Triaged
** Changed in: maas (Ubuntu)
Status: New => Triaged
--
You receiv
** Changed in: maas
Status: Fix Committed => 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/1665143
Title:
Commission scripts select the wrong nvme device link, then fails to
re
** Changed in: maas
Status: Fix Committed => 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/1655049
Title:
[2.1] netaddr raises IndexError when looking up some OUI registrations
** Changed in: maas
Status: Fix Committed => 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/1640147
Title:
[2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE"
** Changed in: maas
Status: Fix Committed => 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/1645912
Title:
freeipmi ipmi-config --checkout lacks support for ipv6 lan parameters
T
** Changed in: maas
Status: Fix Committed => 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/1637246
Title:
MaaS should use configured names for VLAN interfaces
To manage notifica
** Changed in: maas
Status: Fix Committed => 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/1621507
Title:
initramfs-tools configure_networking() fails to dhcp ipv6 addresses
To
** Changed in: maas
Status: Fix Committed => 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/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To ma
I can confirm that this has tested and works as expected. We have not
found any regressions.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Changed in: debian-installer (Ubuntu)
Importance: Undecided => Low
** Changed in: debian-installer (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625211
T
** Changed in: maas (Ubuntu)
Status: Confirmed => 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/1214172
Title:
juju/MAAS Tag constraints do not work in Precise
To manage notificati
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
Interface MTU management acro
Public bug reported:
Dependencies & Upgrade
=
MAAS users that are upgrading to Yakkety and 2.1, they will be able to
continue to use MAAS exactly the same way how they were using it before,
right after the upgrade without any user intervention. While MAAS 2.1
adds significant
** Changed in: maas
Milestone: None => 2.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639930
Title:
initramfs network configuration ignored if only ip6= on kernel command
line
To manage
** Changed in: maas (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639766
Title:
[SRU] MAAS 2.1.1
To manage notifications about this bug go to:
https:/
Right, so this is a bug in LSHW and NOT in MAAS.
** Also affects: lshw (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Won't Fix
** Summary changed:
- [2.1] Cavium ThunderX system with 128GigB of memory is reported as having
125.9GigB of memory in
** Changed in: maas
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/1632480
Title:
Latest Yakkety grub timesout when attempting to UEFI boot over IPv6
To manage notifica
@Scott,
Any ETA for SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
To manage notifications about this bug go to
Re-marking verification-done provided veritifaction had already been
made in Xenial, and was overwritten by yakkety one. It has also been
tested in yakkety.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubu
** Changed in: maas/2.1
Status: Fix Committed => 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/1582323
Title:
Commissioning fails when competing cloud metadata resides on disk
T
I have tested and confirm that passes all CI and manual tests.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644071
Title:
[SR
Public bug reported:
[Impact]
MAAS 2.1.4 is a new upstream bugfix release that includes various fixes
that Ubuntu version of MAAS would benefit of. See the CHANGELOG for a
complete list of bugs fixed.
[Test Case]
1. Install MAAS 2.0.0 or Ubuntu 2.1.0
2. Upgrade to MAAS 2.1.4
3. MAAS will continu
** Changed in: maas/2.1
Status: In Progress => 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/1665143
Title:
Commission scripts select the wrong nvme device link, then fails to
** Changed in: maas/2.1
Status: Fix Committed => 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/1655049
Title:
[2.1] netaddr raises IndexError when looking up some OUI registratio
** Changed in: maas/2.1
Status: Fix Committed => 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/1645912
Title:
freeipmi ipmi-config --checkout lacks support for ipv6 lan parameter
** Changed in: maas/2.1
Status: Fix Committed => 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/1640147
Title:
[2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE
Public bug reported:
[Impact]
MAAS 1.9.5 is a new upstream bugfix release that includes various fixes
that Ubuntu version of MAAS would benefit of. See the CHANGELOG for a
complete list of bugs fixed.
[Test Case]
1. Install MAAS 1.9.4
2. Upgrade to MAAS 1.9.5
3. MAAS will continue to function as
** Also affects: maas (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu Trusty)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
*** This bug is a duplicate of bug 1665808 ***
https://bugs.launchpad.net/bugs/1665808
Yes it is a dupe. Marking as such.
** This bug has been marked a duplicate of bug 1665808
Unable to install core snap in an ephemeral boot: cannot create namespace
group directory /run/snapd/ns: Bad fil
*** This bug is a duplicate of bug 1659151 ***
https://bugs.launchpad.net/bugs/1659151
** This bug has been marked a duplicate of bug 1659151
[UI, 2.1] Can't change fabric, subnet and IP Mode for NIC all at once from
webui
--
You received this bug notification because you are a member of
while there's a traceback, the reality of it is that MAAS itself
recovers, so it is not immediately a blocking issue.
** Changed in: maas
Milestone: None => 2.3.x
** Changed in: maas
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
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
Bugs, which is subscribed to Ubuntu.
https
Hi James,
Can you please provide the following:
1. MAAS version and logs (/var/log/maas/regiond.log,maas.log)'
2. The dump of machine that would satisfy constraints: e.g. maas admin machines
read hostname=
3. Can you provide the Juju debug lab where it is making a request to MAAS
sending the co
debug log*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729127
Title:
storage: No available machine matches constraints
To manage notifications about this bug go to:
https://bugs.launchpad.net/ju
** Changed in: maas (Ubuntu)
Status: New => Fix Released
** Changed in: maas/2.0
Status: Triaged => Won't Fix
** Changed in: maas/2.0
Milestone: 2.0.1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: maas
Milestone: 2.0.0 => next
** Changed in: maas
Status: Triaged => Won't Fix
** Changed in: maas (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Changed in: maas
Status: Triaged => 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/1307614
Title:
MAAS sometimes attempts to install to USB flash drive
To manage notifications
** Changed in: maas
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442112
Title:
booting ppc64el with hwe-u kernel hangs in initrd
To manage notifications about th
** Changed in: maas
Milestone: None => 2.3.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319600
Title:
maas-cli stack trace if .maascli.db unreadable
To manage notifications about this bug g
I believe that in the latest versions of MAAS, this has now been fixed.
If you believe this issue still exists, please re-open this bug report
or file a new one.
** No longer affects: python-tx-tftp
** Changed in: python-tx-tftp (Ubuntu)
Status: New => Invalid
** Changed in: maas
S
We believe this is no longer an issue in the latest releases of MAAS.
Please upgrade to the latest version of MAAS, and If you believe this
issue is still present, please re-open this bug report or file a new
one.
** Changed in: maas
Status: Triaged => Won't Fix
--
You received this bug n
@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
** Changed in: maas
Status: Fix Committed => 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/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
To manag
The versions in -proposed for all releases have been tested as per the
description of the bug.
2.2.0+bzr6054-0ubuntu2~17.04.1
2.2.0+bzr6054-0ubuntu2~16.10.1
2.2.0+bzr6054-0ubuntu2~16.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 2.3.0
** Changed in: maas
Importance: Undecided => High
** Changed in: maas
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bug
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testin
*** This bug is a duplicate of bug 1721808 ***
https://bugs.launchpad.net/bugs/1721808
You need a newer version of curtin, which is currently available on
xenial-proposed.
** Changed in: maas
Status: Confirmed => Invalid
** Changed in: maas (Ubuntu Xenial)
Status: Confirmed =>
** Changed in: ipxe (Ubuntu Bionic)
Status: New => 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/1707999
Title:
pod VM fails to PXE boot after receiving multiple DHCP offers, for
Also, I've tested this in GMAAS and confirm the fix works!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
To manage noti
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Milestone: None => 1.9.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713795
Title:
Hey guys.
Sorry for joining the party late. But let me see if I understand the
full extent of the problem here.
0. A machine PXE boots off MAAS, installs Ubuntu in it, grub gets
installed and configured without updating the NVRAM.
1. The machine reboots, PXE's, boots from local disk, and finishe
Hi Rod,
Judging by your message in #2, unless I'm missing something, you would have not
been able to re-deploy the machine because efibootmgr had set the boot order to
the disk first. When you re-deployed the machine, MAAS told that machine that
"on the next boot, PXE boot".
"
- The node was al
Public bug reported:
This is a follow up discussion from #1642298 and filing this bug to keep
a record.
On a fresh Ubuntu install, grub2 overwrites the NVRAM and updates to
boot order to have Ubuntu as the first boot device. This affects
situations in which PXE had been set the first boot device
So the concern we are primarily interested on is the upgrade scenario.
Effectively, if 'ubuntu' is already in the boot order (and it is not the
first one), on grub2 upgrade, it shouldn't be overwriting the current
BootOrder (e.g. because we specifically configured it to Boot from the
Network first
In ipmitool 1.18.17+
$ ipmitool -I lanplus -U xxx -P xxx -H X.X.X.X chassis bootdev pxe
options=persistent,efiboot
Set Boot Device to pxe
$ ipmitool -I lanplus -U xxx -P xxx -H X.X.X.X chassis bootparam get 5
Boot parameter version: 1
Boot parameter 5 is valid/unlocked
Boot parameter data: a0040
** Summary changed:
- UEFI Xenial install sets computer to boot from hard disk
+ Grub upgrades overwrites NVRAM cuasing MAAS/curtin boot order to be overwriten
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
The work around is to pass a debconf configuration option to grub2
package to not update the NVRAM on package upgrade.
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Status: New => Confirmed
** Changed in: maas
Importance: Und
Hi John,
There's a patch attached which you can apply to resolve this issue. We
are working to get this SRU'd.
Thanks!
** Changed in: maas
Status: Triaged => In Progress
** Changed in: maas (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you
** Changed in: maas (Ubuntu)
Status: In Progress => New
** Changed in: maas (Ubuntu)
Assignee: Andres Rodriguez (andreserl) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Description changed:
- After a recent update, it's no longer possible to install Ubuntu 14.04
- with MaaS 1.9.5 . This is on a new installation of MaaS on 14.04.
+ [Impact]
+ After a recent update, it's no longer possible to install Ubuntu 14.04 with
MaaS 1.9.5 . This is on a new installation
*** This bug is a duplicate of bug 1711700 ***
https://bugs.launchpad.net/bugs/1711700
Hi Jeff,
If MAAS is reloading DNS constantly, it is because you have machines
from the dynamic range obtaining new IP addresses. That said, the issue
is not MAAS reloading, but rather, it is bind failing to
>From our irc discussion:
18:27 < dpb> but it's booted just fine as recently as 2 days ago
A new grub version was published on 2017-07-28 in
2.02~beta2-36ubuntu3.12. This seems like it could be a regression in
grub that 2.02~beta2-36ubuntu3.13 (currently in proposed) could
probably fix.
** Cha
** Changed in: maas
Status: Confirmed => In Progress
** Also affects: maas/2.2
Importance: Undecided
Status: New
** Changed in: maas/2.2
Milestone: None => 2.2.3
** Changed in: maas/2.2
Importance: Undecided => High
** Changed in: maas/2.2
Status: New => Triaged
Yes, this will work only with the version in trusty-updates, provided
that all of our known customers/users are already using trusty-updates,
and as such, we do not need to be compatible with trusty-security.
** Changed in: maas (Ubuntu)
Status: Incomplete => New
--
You received this bug
Hi There,
Can you confirm that both your MAAS Region and Cluster controller are working
as expected?
Can you attach logs? /var/log/maas/*.log
Can you restart your services? sudo service maas-regiond restart && sudo
service maas-rackd restart
Can you attach the upstart job log?
** Changed in: m
** Changed in: maas (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667141
Title:
[FFe] Standing FFe for MAAS 2.2
To manage notifications about this bug g
** Changed in: maas (Ubuntu)
Importance: Undecided => High
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Importance: Undecided => High
** Changed in: maas
Milestone: None => 2.2.0rc2
--
You received this bug notification because you are a membe
Public bug reported:
The rack controller constantly showing the " rackd — 75% connected to
region controllers." message. However, this may just be a UI message
provided that there are no tracebacks on the logs.
2017-04-05 22:51:47 regiond: [info] 127.0.0.1 GET /MAAS/api/2.0/machines/
HTTP/1.1 -
Hi Brad,
MAAS DNS support was completely refactored in MAAS 2.0, and you should
find all your issues above fully operation on MAAS 2.x.
Given that we completely refactored this in 2.0, we have no plans of
backporting any of this to 1.9.
** Changed in: maas (Ubuntu)
Status: New => Won't Fi
** Changed in: maas
Milestone: 2.2.0rc2 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679222
Title:
ISCSI target validation fails when target name includes a ':'
To manage notification
701 - 800 of 2956 matches
Mail list logo
