This bug was fixed in the package maas - 2.3.5-6511-gf466fdb-0ubuntu1
---
maas (2.3.5-6511-gf466fdb-0ubuntu1) xenial-proposed; urgency=medium
* Stable Release Update. New upstream release, MAAS 2.3.5 (LP: #1772010):
- MAAS 2.3.5 is a new upstream release that fixes a
** Changed in: maas (Ubuntu)
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/1772010
Title:
[SRU] MAAS 2.3.5
To manage notifications about this bug go to:
tested from -proposed this package both on CI and manually and +1.
Marked 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/1772010
Title:
[SRU] MAAS 2.3.5
To manage notifications
After this operation, 228 MB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 authbind amd64
2.1.1+nmu1 [17.6 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64
libavahi-common-data amd64 0.6.32~rc+dfsg-1ubuntu2.2 [21.5 kB]
Get:3
maas-integration.TestMAASIntegration.test_create_admin ... ok
maas-integration.TestMAASIntegration.test_restart_dbus_avahi ... SKIP:
Avahi/DBUS are not used anymore
maas-integration.TestMAASIntegration.test_update_maas_url ... ok
maas-integration.TestMAASIntegration.test_update_maas_url_rack ...
For MAAS 2.3.4 I've marked this as verification failed. I'm uploading
MAAS 2.3.5 which fixes a regression that was encountered by some users
during testing and we were able to reproduce. I'm using this same bug
report for MAAS 2.3.5.
** Description changed:
[Impact]
This is a new upstream
