1. check what use_peer_proxy
ubuntu@autopkgtest:~$ maas admin maas get-config name=use_peer_proxy
Success.
Machine-readable output follows:
false
2. set maas_proxy_port
ubuntu@autopkgtest:~$ maas admin maas set-config name=maas_proxy_port value=8081
Success.
Machine-readable output follows:
OK
Hello Andres, or anyone else affected,
Accepted maas into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/maas/2.3.5-6511
-gf466fdb-0ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.
MAAS 2.3.4 fixes various issues that were present on MAAS 2.3.0.
https://launchpad.net/maas/+milestone/2.3.1
https://launchpad.net/maas/+milestone/2.3.2
** Tags removed: verification-needed
** Tags added: verification-failed
--
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.4
To manage notifications about this bug go to:
I've reviewed the changes from 2.3.3 to 2.3.4 and I'm satisfied with all
of those.
On 2.3.0 to 2.3.3:
Xenial vs. Bionic for commissioning only changes new installs. Existing
installs are unaffected, so this is OK now that we have that detail
documented.
"LACP rate fast by default" does change
Please note that this is blocked from being published to xenial-updates
until the features being added in this SRU land in bionic-updates. To
avoid mistakes, please do not tag verification-xenial-done or
verification-done until that SRU is also ready to release.
--
You received this bug
Hi Andres,
Thank you for the bug description updates. I like the headings you have
now, assuming "Bug fixes that introduce" is supposed to be "Bug fixes
that introduce behaviour changes". These are useful and is exactly the
information I needed in the SRU information to be able to review this.
> ...but it looks like this landed in 2.4 in July yet xenial-proposed is
based on an upstream tarball first uploaded in June.
I meant _bionic-proposed_ is based on an upstream tarball first uploaded
in June.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.
MAAS 2.3.4 fixes various issues that were present on MAAS 2.3.0.
https://launchpad.net/maas/+milestone/2.3.1
https://launchpad.net/maas/+milestone/2.3.2
** Summary changed:
- [SRU] MAAS 2.3.3
+ [SRU] MAAS 2.3.4
** Description changed:
[Impact]
This is a new upstream release that addresses various issues present in 2.3.0.
- MAAS 2.3.3 fixes various issues that were present on MAAS 2.3.0.
+ MAAS 2.3.4 fixes various issues that were present
10 matches
Mail list logo
