Merge lp:~andreserl/maas/packaging_rc3 into lp:~maas-maintainers/maas/packaging

Proposed by Andres Rodriguez on 2016-07-27
Status: Merged
Approved by: Andres Rodriguez on 2016-07-28
Approved revision: 512
Merged at revision: 509
Proposed branch: lp:~andreserl/maas/packaging_rc3
Merge into: lp:~maas-maintainers/maas/packaging
Diff against target: 90 lines (+54/-6)
2 files modified
debian/changelog (+44/-0)
debian/maas-region-controller.postinst (+10/-6)
To merge this branch: bzr merge lp:~andreserl/maas/packaging_rc3
Reviewer Review Type Date Requested Status
Andres Rodriguez Approve on 2016-07-28
Review via email: mp+301342@code.launchpad.net

Commit message

* 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.

To post a comment you must log in.
Nobuto Murata (nobuto) :
MAAS Lander (maas-lander) wrote :

Voting does not meet specified criteria. Required: Approve >= 1, Disapprove == 0. Got: 1 Pending.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'debian/changelog'
2--- debian/changelog 2016-07-19 13:40:51 +0000
3+++ debian/changelog 2016-07-28 02:27:27 +0000
4@@ -1,3 +1,47 @@
5+maas (2.0.0~rc4+bzr5180-0ubuntu1) UNRELEASED; urgency=medium
6+
7+ * UNRELEASED
8+
9+ -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 27 Jul 2016 22:26:55 -0400
10+
11+maas (2.0.0~rc3+bzr5180-0ubuntu2) yakkety; urgency=medium
12+
13+ * Really fix by the determination of the default gateway, otherwise
14+ automatically chose localhost. (LP: #1607112)
15+
16+ -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 27 Jul 2016 22:20:09 -0400
17+
18+maas (2.0.0~rc3+bzr5180-0ubuntu1) yakkety; urgency=medium
19+
20+ * New upstream release, 2.0.0 RC3 bzr5180:
21+ - CLI version command doesn't work (2.0) (LP: #1557434)
22+ - [2.0rc1] MAAS does not respect default subnet's DNS server when
23+ choosing default DNS (LP: #1576116)
24+ - [2.0RC1] MAAS displays every power query on the summarized view of
25+ node event log (LP: #1594991)
26+ - [2.0] Loading latest machine events can make web browser
27+ unresponsive (LP: #1598028)
28+ - [2.0rc1] MAAS doesn't honor DNS settings for a subnet for
29+ DHCP (LP: #1600720)
30+ - [2.0rc1] drop arm64/efi grub module workaround (LP: #1600285)
31+ - maas login yields "ImportError: No module named
32+ 'maasserver'" (LP: #1604169)
33+ - [doc] events API limit,before, after options not
34+ documented (LP: #1604901)
35+ - RackController.get_image_sync_status causes huge load
36+ on regiond process (LP: #1604465)
37+ - [2.0b8] MAAS is automatically monitoring timeouts. (LP: #1598149)
38+ - [2.0] Error messaging about monitor expiry has been
39+ dropped (LP: #1605252)
40+ - [2.0rc2] Can't get node-results via cli/api (LP: #1602721)
41+ - node set to "failed deployment" for no visible reason (LP: #1604962)
42+ - Event log should always include a reason why a node was
43+ marked Failed Deployment (LP: #1604987)
44+ * If no default route is present in the system, configure maas_url on
45+ regiond.conf to localhost to allow the user to tell MAAS what IP to use.
46+
47+ -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 22 Jul 2016 18:05:45 -0400
48+
49 maas (2.0.0~rc2+bzr5156-0ubuntu1) yakkety; urgency=medium
50
51 * New upstream release, 2.0.0 RC2 bzr5156:
52
53=== modified file 'debian/maas-region-controller.postinst'
54--- debian/maas-region-controller.postinst 2016-06-17 17:46:00 +0000
55+++ debian/maas-region-controller.postinst 2016-07-28 02:27:27 +0000
56@@ -30,16 +30,20 @@
57 --maas-url "http://${ipaddr}/MAAS"
58 }
59
60-get_default_route_ip() {
61+get_default_route_ip_or_localhost() {
62 while read Iface Destination Gateway Flags RefCnt Use Metric Mask MTU Window IRTT
63 do
64 [ "$Mask" = "00000000" ] && break
65 done < /proc/net/route
66 interface="$Iface"
67- ipaddr=$(LC_ALL=C /sbin/ip -4 addr list dev "$interface" scope global)
68- ipaddr=${ipaddr#* inet }
69- ipaddr=${ipaddr%%/*}
70- echo $ipaddr
71+ if [ -z "$interface" ]; then
72+ echo "localhost"
73+ else
74+ ipaddr=$(LC_ALL=C /sbin/ip -4 addr list dev "$interface" scope global)
75+ ipaddr=${ipaddr#* inet }
76+ ipaddr=${ipaddr%%/*}
77+ echo $ipaddr
78+ fi
79 }
80
81 extract_default_maas_url() {
82@@ -67,7 +71,7 @@
83 db_get maas/default-maas-url
84 ipaddr="$RET"
85 if [ -z "$RET" ]; then
86- ipaddr=$(get_default_route_ip)
87+ ipaddr=$(get_default_route_ip_or_localhost)
88 fi
89 # Set the IP address of the interface with default route
90 if [ -n "$ipaddr" ]; then

Subscribers

People subscribed via source and target branches

to all changes: