group.of.nepali.translators team mailing list archive

[Andres Rodriguez <andreserl@xxxxxxxxxxxxx>]

** Changed in: maas (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1772010

Title:
  [SRU] MAAS 2.3.5

Status in maas package in Ubuntu:
  Fix Released
Status in maas source package in Xenial:
  Fix Committed

Bug description:
  [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
  https://launchpad.net/maas/+milestone/2.3.3
  https://launchpad.net/maas/+milestone/2.3.4
  https://launchpad.net/maas/+milestone/2.3.5

  This point release includes fixes/enhancements for hardware enablement
  and to address customer related issues that are worth noting:

  Enhancements/Hardware Enablement
  --------------------------------

  * Bug 1750622 "[feature] Add ability to select the BIOS boot method
  for IPMI - To address issues with newer firmware"

  This adds a new option to power manage machines, that are oriented at
  addressing changes in upstream hardware firmware's (that have broken
  compatibility with older versions). Causes no behavior changes for
  MAAS as it continues to do the same.

  Regression potential: None. MAAS will continue to behave the same way
  it did before in new installs and upgrades, and this change only takes
  effect by a user driven action.

  Bug 1758760 "[enhancement] Support Lenovo’s new password policy
  (Lenovo SR550)"

  Fixes the password generation process for IPMI discovery to consider
  new password policies that are being added to newer hardware or
  firmware versions.

  Regression potential: None. MAAS will continue to behave the same way
  it did before in new installs and upgrades, by testing the old
  password policy. If it doesn't work it will use the new password
  policy.

  LP: #1779712	[enhancement] maas-proxy port should be configurable
  Adds the ability to change the proxy port for the proxy that MAAS uses. If users upgrade, the configuration rendered will continue to use the default port. This will only take effect for users who change the port.

  Regression potential: None. MAAS will continue to behave the same way
  it did before in new installs and upgrades, by using the default port.
  This change only takes effect by a user driven action.

  LP: #1778710	[2.3] Allow telling MAAS image import to not use proxy.
  Allow's users to tell MAAS to import images without using the configured proxy, in cases that MAAS is directly connected to the internet but machines are not.

  Regression potential: None. MAAS will continue to behave the same way
  it did before in new installs and upgrades, this would only take
  effect by a user driven action.

  Bug fixes that change existing behaviour
  ------------------------

  Bug 1739761 [adds support to deploy Precise on MAAS 2.3]
  Re-adds the ability to deploy precise, which was dropped on MAAS 2.3 initially.

  Bug 1730751 "LACP rate fast by default"
  Changes the default LACP rate to fast, which addresses issues in that our IS department was facing. Note that this only changes how often the control packets are set and it is recommended/preferred to be set to fast, and the use of slow is discouraged.

  Bug 1767137 "Default install is now importing bionic by default instead of xenial"
  This is an issue that MAAS automatically started selection Bionic for commissioning instead of Xenial as it was intended. This ensure that Xenial is selected by default. Note that in case of upgrades, if Bionic is already selected, MAAS won't change this to Xenial. It will *only* affect to new installs.

  Other

  LP: #1787381 - WebUI overrides proxy values that have not changed

  The WebUI was overriding values that had not been changed in the
  WebUI. This bugs addresses this issue to ensure it only does it if
  something changes.

  
  [Test Case]

  MAAS Testing
  ------------
  MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include:

  1. Manual Fresh installation of MAAS
  2. Manual upgrade from the previous Ubuntu Release.
  3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI.
  4. Automated (CI) testing of MAAS install and operation against other Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the Canonical Solutions QA Team.
  5. Manual split region/rack test are performed. This is to ensure that if we upgrade a MAAS Region to a newer version, the MAAS rack of the older version remains connected and operational.

  All of this includes verifying normal operation, issues fixed, and
  ensuring that Canonical Cloud solutions can inter-operate.

  LP: #1787381 Testing
  --------------------
  This fix requires manual testing. To test:

  1. Install MAAS
  2. Update maas_proxy_port over the API (e.g. maas <user> maas set-config name=maas_proxy_port value=8080
  3. Go to the Web UI and change the proxy method from internal to 'Peer Proxy'
  4. Ensure that maas_proxy_port has not changed: (w.g. maas <user> maas get-config name=maas_proxy_port.

  Solutions QA
  ------------
  MAAS releases are also now vetted by the Solutions QA team. The test they run ensure there are no regression for their use cases. This release has been accepted / vetted by them.

  [Regression Potential]

  Minimal (For MAAS itself).
  MAAS is fully backwards compatible and handles upgrades from previous releases which result in the continuous operation of MAAS. Users will continue to use this new version of MAAS as they used it before.

  Minimal (for deployments).
  LP: #1730751 is fixed in this release, which changes the default LACP rate to fast. This doesn't provide any regression for MAAS itself, machines deployed with bonds will have the LACP rate to fast, which will yield discovery of errors much faster.

  Since this is a point release, this has been tested thoroughly to
  confirm that no regressions have been introduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1772010/+subscriptions