Created by Andres Rodriguez and last modified
Get this branch:
bzr branch lp:~maas-maintainers/maas/packaging-2.0
Members of MAAS Maintainers can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

MAAS Maintainers

Recent revisions

510. By Andres Rodriguez

[r=andreserl][bug=][author=andreserl] Release MAAS 2.0

509. By Andres Rodriguez

[r=andreserl][bug=1557434,1576116,1594991,1598028,1598149,1600285,1600720,1602721,1604169,1604465,1604901,1604962,1604987,1605252,1607112][author=andreserl] * 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.

508. By Andres Rodriguez

Release RC2

507. By Andres Rodriguez

* 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

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

505. By Andres Rodriguez

Update changelog

504. By Andres Rodriguez

[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

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

502. By Andres Rodriguez

[r=andreserl][bug=][author=andreserl] debian/control: maas-region-api depends on maas-cli.

501. By Gavin Panella

[r=andreserl][bug=1590081][author=allenap] Switch to OpenSSH for SSH public key validation.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.