lp://staging/~andreserl/maas/packaging_rc3

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/~maas-maintainers/maas/packaging at revision 509

Andres Rodriguez (community): Approve on 2016-07-28

Diff: 90 lines (+54/-6)

2 files modified

debian/changelog (+44/-0)
debian/maas-region-controller.postinst (+10/-6)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1557434: [2.0rc1] CLI version command doesn't work	High	Fix Released
Bug #1576116: [2.0rc1] MAAS does not respect default subnet's DNS server when choosing default DNS	High	Fix Released
Bug #1594991: [2.0RC1] MAAS displays every power query on the summarized view of node event log	High	Fix Released
Bug #1598028: [2.0] Loading latest machine events can make web browser unresponsive	High	Fix Released
Bug #1598149: [2.0rc2] MAAS is not automatically monitoring timeouts for commissioning.	Critical	Fix Released
Bug #1600285: [2.0rc1] please drop arm64/efi grub module workaround	Medium	Fix Released
Bug #1600720: [2.0rc1] MAAS doesn't honor DNS settings for a subnet for DHCP	Critical	Fix Released
Bug #1602721: [2.0rc2] Can't get node-results via cli/api	Critical	Fix Released
Bug #1604169: [2.0] maas login yields "ImportError: No module named 'maasserver'"	Critical	Fix Released
Bug #1604465: [2.0rc2] RackController.get_image_sync_status causes huge load on regiond process	Critical	Fix Released
Bug #1604901: [doc] events API limit,before, after options not documented	Wishlist	Fix Released
Bug #1604962: node set to "failed deployment" for no visible reason	Critical	Fix Released
Bug #1604987: Event log should always include a reason why a node was marked Failed Deployment	Medium	Fix Released
Bug #1605252: [2.0] Log messaging about timeout monitor has been dropped	Critical	Fix Released
Bug #1607112: [2.0rc2] package installation fails when default gateway is not set	Medium	Fix Released

Link a bug report

Related blueprints

512. By Andres Rodriguez on 2016-07-28

Open RC4

511. By Andres Rodriguez on 2016-07-28

Really fix by the determination of the default gateway, otherwise
automatically chose localhost. (LP: #1607112)

510. By Andres Rodriguez on 2016-07-27

* New upstream release, 2.0.0 RC3 bzr5180:
  - CLI version command doesn't work (2.0) (LP: #1557434)
  - [2.0rc1] MAAS does not respect default subnet's DNS server when
    choosing default DNS (LP: #1576116)
  - [2.0RC1] MAAS displays every power query on the summarized view of
    node event log (LP: #1594991)
  - [2.0] Loading latest machine events can make web browser
    unresponsive (LP: #1598028)
  - [2.0rc1] MAAS doesn't honor DNS settings for a subnet for
    DHCP (LP: #1600720)
  - [2.0rc1] drop arm64/efi grub module workaround (LP: #1600285)
  - maas login yields "ImportError: No module named
    'maasserver'" (LP: #1604169)
  - [doc] events API limit,before, after options not
    documented (LP: #1604901)
  - RackController.get_image_sync_status causes huge load
    on regiond process (LP: #1604465)
  - [2.0b8] MAAS is automatically monitoring timeouts. (LP: #1598149)
  - [2.0] Error messaging about monitor expiry has been
    dropped (LP: #1605252)
  - [2.0rc2] Can't get node-results via cli/api (LP: #1602721)
  - node set to "failed deployment" for no visible reason (LP: #1604962)
  - Event log should always include a reason why a node was
    marked Failed Deployment (LP: #1604987)
* If no default route is present in the system, configure maas_url on
  regiond.conf to localhost to allow the user to tell MAAS what IP to use.

509. By Andres Rodriguez on 2016-07-27

If no default route is set, configure maas_url on regiond.conf as localhost, so the user can tell MAAS what IP to use.

508. By Andres Rodriguez on 2016-07-19

Release RC2

507. By Andres Rodriguez on 2016-07-06

* UNRELEASED
* New upstream release, 2.0.0 RC1 bzr5143:
  - Determine a method for how to reconnect a deleted rack controller (LP: #1576357)
  - [2.0b7, regression] maas-rack register makes up a new hostname (LP: #1592246)
  - [2.0b8] HMC power driver regression -- Not able to connect via SSH. (LP: #1595753)
  - [2.0b7] Date and time format should be consistent accross logs (LP: #1592885)
  - [2.0b8] Unable to set default gateway interface (LP: #1597324)
  - [1.9] VMware power management fails when VMs are organized in nested subfolders (LP: #1515188)
  - [2.0] maas 2.0 pxeboot fails on PowerNV (LP: #1596046)
* New upstream release, 2.0.0 beta8 bzr5134:

506. By LaMont Jones on 2016-06-18

[r=blake-rouse][bug=1592954][author=lamont] Wait for squid to finish starting in systemctl start maas-proxy

505. By Andres Rodriguez on 2016-06-17

Update changelog

504. By Andres Rodriguez on 2016-06-17

[r=andreserl,allenap][bug=][author=andreserl] * debian/maas-region-controller.config: Ensure dbc_go is not run when dbconfig common is not yet installed.
* debian/maas-region-api.postinst: Ensure rsyslog is restarted.
* debian/maas-region-controller.postinst: Ensure maas_url ends with 5240.

503. By LaMont Jones on 2016-06-16

[r=blake-rouse][bug=][author=lamont] Versioned dependency on squid >> 3.5 to better reflect xenial, and built-in acl changes that have occurred.