Merge lp:~julian-edwards/maas/releasenotes-rc1 into lp:~maas-committers/maas/trunk
- releasenotes-rc1
- Merge into trunk
Proposed by
Julian Edwards
Status: | Merged |
---|---|
Approved by: | Julian Edwards |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3326 |
Proposed branch: | lp:~julian-edwards/maas/releasenotes-rc1 |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
576 lines (+231/-164) 1 file modified
docs/changelog.rst (+231/-164) |
To merge this branch: | bzr merge lp:~julian-edwards/maas/releasenotes-rc1 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Julian Edwards (community) | Approve | ||
Review via email:
|
Commit message
More release note changes for 1.7.0: Known problems section, and generally reformatted for clarity. Also removed bugs in the list that were only introduced in this cycle.
Description of the change
More release notes.
To post a comment you must log in.
Revision history for this message
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Julian Edwards (julian-edwards) : | # |
review:
Approve
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1 | === modified file 'docs/changelog.rst' |
2 | --- docs/changelog.rst 2014-10-30 05:53:02 +0000 |
3 | +++ docs/changelog.rst 2014-10-31 01:34:18 +0000 |
4 | @@ -8,14 +8,12 @@ |
5 | Important announcements |
6 | ----------------------- |
7 | |
8 | -Re-import your boot images |
9 | -^^^^^^^^^^^^^^^^^^^^^^^^^^ |
10 | -You must re-import your boot images, see below for details. |
11 | +**Re-import your boot images** |
12 | + You must re-import your boot images, see below for details. |
13 | |
14 | -Update Curtin preseed files |
15 | -^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
16 | -Two changes were made to Curtin preseed files that need your attention |
17 | -if you made any customisations: |
18 | +**Update Curtin preseed files** |
19 | + Two changes were made to Curtin preseed files that need your attention |
20 | + if you made any customisations: |
21 | |
22 | * The OS name must now appear in the filename. The new schema is shown |
23 | here, each file pattern is tried in turn until a match is found:: |
24 | @@ -46,7 +44,7 @@ |
25 | Major new features |
26 | ------------------ |
27 | |
28 | -Improved image downloading and reporting. |
29 | +**Improved image downloading and reporting.** |
30 | MAAS boot images are now downloaded centrally by the region controller |
31 | and disseminated to all registered cluster controllers. This change includes |
32 | a new web UI under the `Images` tab that allows the admin to select |
33 | @@ -57,7 +55,7 @@ |
34 | |
35 | This process is also completely controllable using the API. |
36 | |
37 | -Note: |
38 | +.. Note:: |
39 | Unfortunately due to a format change in the way images are stored, it |
40 | was not possible to migrate previously downloaded images to the new region |
41 | storage. The cluster(s) will still be able to use the existing images, |
42 | @@ -68,7 +66,7 @@ |
43 | This means that the first thing to do after upgrading to 1.7 is go to the |
44 | `Images` tab and re-import the images. |
45 | |
46 | -Increased robustness. |
47 | +**Increased robustness.** |
48 | A large amount of effort has been given to ensuring that MAAS remains |
49 | robust in the face of adversity. An updated node state model has been |
50 | implemented that takes into account more of the situations in which a |
51 | @@ -83,7 +81,7 @@ |
52 | handles retries when changing the power state of hardware, removing the |
53 | requirement that each power template handle it individually. |
54 | |
55 | -RPC security. |
56 | +**RPC security.** |
57 | As a step towards mutually verified TLS connections between MAAS's |
58 | components, 1.7 introduces a simple shared-secret mechanism to |
59 | authenticate the region with the clusters and vice-versa. For those |
60 | @@ -105,7 +103,7 @@ |
61 | That's it; the upgraded cluster controller will find the secret |
62 | without needing to be told. |
63 | |
64 | -RPC connections. |
65 | +**RPC connections.** |
66 | Each cluster maintains a persistent connection to each region |
67 | controller process that's running. The ports on which the region is |
68 | listening are all high-numbered, and they are allocated randomly by |
69 | @@ -113,15 +111,15 @@ |
70 | each cluster controller needs unfiltered access to each machine in the |
71 | region on all high-numbered TCP ports. |
72 | |
73 | -Node event log. |
74 | +**Node event log.** |
75 | For every major event on nodes, it is now logged in a node-specific log. |
76 | This includes events such as power changes, deployments and any failures. |
77 | |
78 | -IPv6. |
79 | +**IPv6.** |
80 | It is now possible to deploy Ubuntu nodes that have IPv6 enabled. |
81 | See :doc:`ipv6` for more details. |
82 | |
83 | -Removal of Celery and RabbitMQ. |
84 | +**Removal of Celery and RabbitMQ.** |
85 | While Celery was found to be very reliable it ultimately did not suit |
86 | the project's requirements as it is a largely fire-and-forget mechanism. |
87 | Additionally it was another moving part that caused some headaches for |
88 | @@ -134,18 +132,18 @@ |
89 | Since a constant connection is maintained, as a side effect the web UI now |
90 | shows whether each cluster is connected or not. |
91 | |
92 | -Support for other OSes. |
93 | +**Support for other OSes.** |
94 | Non-Ubuntu OSes are fully supported now. This includes: |
95 | - Windows |
96 | - Centos |
97 | - SuSE |
98 | |
99 | -Custom Images. |
100 | +**Custom Images.** |
101 | MAAS now supports the deployment of Custom Images. Custom images can be |
102 | uploaded via the API. The usage of custom images allows the deployment of |
103 | other Ubuntu Flavors, such as Ubuntu Desktop. |
104 | |
105 | -maas-proxy. |
106 | +**maas-proxy.** |
107 | MAAS now uses maas-proxy as the default proxy solution instead of |
108 | squid-deb-proxy. On a fresh install, MAAS will use maas-proxy by default. |
109 | On upgrades from previous releases, MAAS will install maas-proxy instead of |
110 | @@ -154,12 +152,23 @@ |
111 | Minor notable changes |
112 | --------------------- |
113 | |
114 | -Better handling of networks. |
115 | +**Better handling of networks.** |
116 | All networks referred to by cluster interfaces are now automatically |
117 | registered on the Network page. Any node network interfaces are |
118 | automatically linked to the relevant Network. |
119 | |
120 | -Improved logging. |
121 | +.. Note:: |
122 | + Commissioning currently requires an IP address to be available for each |
123 | + network interface on a network that MAAS manages; this allows MAAS to |
124 | + auto-populate its networks database. In general you should use a |
125 | + well-sized network (/16 recommended if you will be using containers and |
126 | + VMs) and dynamic pool. If this feature risks causing IP exhaustion for |
127 | + your deployment and you do not need the auto-populate functionality, you |
128 | + can disable it by running the following command on your region controller:: |
129 | + |
130 | + sudo maas <profile> maas set-config name=enable_dhcp_discovery_on_unconfigured_interfaces value=False |
131 | + |
132 | +**Improved logging.** |
133 | A total overhaul of where logging is produced was undertaken, and now |
134 | all the main events in MAAS are selectively reported to syslog with the |
135 | "maas" prefix from both the region and cluster controllers alike. If MAAS |
136 | @@ -170,238 +179,296 @@ |
137 | On the region controller appservers, maas-django.log contains only appserver |
138 | errors. |
139 | |
140 | -Static IP selection. |
141 | +**Static IP selection.** |
142 | The API was extended so that specific IPs can be pre-allocated for network |
143 | interfaces on nodes and for user-allocated IPs. |
144 | |
145 | -Pronounceable random hostnames. |
146 | +**Pronounceable random hostnames.** |
147 | The old auto-generated 5-letter names were replaced with a pseudo-random |
148 | name that is produced from a dictionary giving names of the form |
149 | 'adjective-noun'. |
150 | |
151 | -Bugs fixed in this release |
152 | --------------------------- |
153 | + |
154 | +Known Problems & Workarounds |
155 | +---------------------------- |
156 | + |
157 | +**Upgrade issues** |
158 | + There may be upgrade issues for users currently on MAAS 1.5 and 1.6; while we |
159 | + have attempted to reproduce and address all the issues reported, some bugs |
160 | + remain inconclusive. We recommend a full, tested backup of the MAAS servers |
161 | + before attempting the upgrade to 1.7. If you do encounter issues, please file |
162 | + these and flag them to the attention of the MAAS team and we will address them |
163 | + in point-releases. See bugs `1381058`_, `1382266`_, `1379890`_, `1379532`_, |
164 | + and `1379144`_. |
165 | + |
166 | +.. _1381058: |
167 | + https://launchpad.net/bugs/1381058 |
168 | +.. _1382266: |
169 | + https://launchpad.net/bugs/1382266 |
170 | +.. _1379890: |
171 | + https://launchpad.net/bugs/1379890 |
172 | +.. _1379532: |
173 | + https://launchpad.net/bugs/1379532 |
174 | +.. _1379144: |
175 | + https://launchpad.net/bugs/1379144 |
176 | + |
177 | +**Split Region/Cluster set-ups** |
178 | + If you site your cluster on a separate host to the region, it needs a |
179 | + security key to be manually installed by running |
180 | + ``maas-provision install-shared-secret`` on the cluster host. |
181 | + |
182 | +**Private boot streams** |
183 | + If you had private boot image stream information configured in MAAS 1.5 or |
184 | + 1.6, upgrading to 1.7 will not take that into account and it will need to be |
185 | + manually entered on the settings page in the MAAS UI (bug `1379890`_) |
186 | + |
187 | +.. _1379890: |
188 | + https://launchpad.net/bugs/1379890 |
189 | + |
190 | +**Concurrency issues** |
191 | + Concurrency issues expose us to races when simultaneous operations are |
192 | + triggered. This is the source of many hard to reproduce issues which will |
193 | + require us to change the default database isolation level. We intend to address |
194 | + this in the first point release of 1.7. |
195 | + |
196 | +**Destroying a Juju environment** |
197 | + When attempting to "juju destroy" an environment, nodes must be in the DEPLOYED |
198 | + state; otherwise, the destroy will fail. You should wait for all in-progress |
199 | + actions on the MAAS cluster to conclude before issuing the command. (bug |
200 | + `1381619`_) |
201 | + |
202 | +.. _1381619: |
203 | + https://launchpad.net/bugs/_1381619 |
204 | + |
205 | +**AMT power control** |
206 | + A few AMT-related issues remain, with workarounds: |
207 | + |
208 | + * Commissioning NUC reboots instead of shutting down (bug `1368685`_). There |
209 | + is `a workaround in the power template`_ |
210 | + |
211 | + * MAAS (amttool) cannot control AMT version > 8. See `workaround described in |
212 | + bug 1331214`_ |
213 | + |
214 | + * AMT NUC stuck at boot prompt instead of powering down (no ACPI support in |
215 | + syslinux poweroff) (bug `1376716`_). See the `ACPI-only workaround`_ |
216 | + |
217 | +.. _1368685: |
218 | + https://bugs.launchpad.net/maas/+bug/1368685 |
219 | +.. _a workaround in the power template: |
220 | + https://bugs.launchpad.net/maas/+bug/1368685/comments/8 |
221 | +.. _workaround described in bug 1331214: |
222 | + https://bugs.launchpad.net/maas/+bug/1331214/comments/18 |
223 | +.. _1376716: |
224 | + https://bugs.launchpad.net/maas/+bug/1376716 |
225 | +.. _ACPI-only workaround: |
226 | + https://bugs.launchpad.net/maas/+bug/1376716/comments/12 |
227 | + |
228 | + |
229 | +**Disk wiping** |
230 | + If you enable disk wiping, juju destroy-environment may fail for you. The |
231 | + current workaround is to wait and re-issue the command. This will be fixed in |
232 | + future versions of MAAS & Juju. (bug `1386327`_) |
233 | + |
234 | +.. _1386327: |
235 | + https://bugs.launchpad.net/maas/+bug/1386327 |
236 | + |
237 | +**BIND with DNSSEC** |
238 | + If you are using BIND with a forwarder that uses DNSSEC and have not |
239 | + configured certificates, you will need to explicitly disable that feature in |
240 | + your BIND configuration (1384334) |
241 | + |
242 | +.. _1384334: |
243 | + https://bugs.launchpad.net/maas/+bug/1384334 |
244 | + |
245 | +**Boot source selections on the API** |
246 | + Use of API to change image selections can leave DB in a bad state |
247 | + (bug `1376812`_). It can be fixed by issuing direct database updates. |
248 | + |
249 | +.. _1376812: |
250 | + https://bugs.launchpad.net/maas/+bug/1376812 |
251 | + |
252 | +**Disabling DNS** |
253 | + Disabling DNS may not work (bug `1383768`_) |
254 | + |
255 | +.. _1383768: |
256 | + https://bugs.launchpad.net/maas/+bug/1383768 |
257 | + |
258 | +**Stale DNS zone files** |
259 | + Stale DNS zone files may be left behind if the MAAS domainname is changed |
260 | + (bug `1383329`_) |
261 | + |
262 | +.. _1383329: |
263 | + https://bugs.launchpad.net/maas/+bug/1383329 |
264 | + |
265 | + |
266 | + |
267 | +Major bugs fixed in this release |
268 | +-------------------------------- |
269 | + |
270 | +See https://launchpad.net/maas/+milestone/1.7.0 for full details. |
271 | + |
272 | #1081660 If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached" |
273 | + |
274 | #1087183 MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost' |
275 | + |
276 | #1328351 ConstipationError: When the cluster runs the "import boot images" task it blocks other tasks |
277 | -#1340208 DoesNotExist: NodeGroupInterface has no nodegroup |
278 | -#1340896 MAAS upgrade from 1.5.2+bzr2282-0ubuntu0.2 to experiment failed |
279 | + |
280 | #1342117 CLI command to set up node-group-interface fails with /usr/lib/python2.7/dist-packages/maascli/__main__.py: error: u'name' |
281 | -#1342395 power_on: ipmi failed: name 'power_off_mode' is not defined at line 12 column 18 in file /etc/maas/templates/power/ipmi.template |
282 | -#1347579 Schema migration 0091 is broken (node boot type) |
283 | + |
284 | #1349254 Duplicate FQDN can be configured on MAAS via CLI or API |
285 | + |
286 | #1352575 BMC password showing in the apache2 logs |
287 | -#1353598 maas-import-pxe-files logger import error for logger |
288 | -#1355014 Can't run tests without a net connection |
289 | + |
290 | #1355534 UnknownPowerType traceback in appserver log |
291 | -#1356788 Test failure: “One or more services are registered” etc. |
292 | -#1359029 Power status monitoring does not scale |
293 | -#1359517 Periodic DHCP probe breaks: "Don't log exceptions to maaslog" |
294 | -#1359551 create_Network_from_NodeGroupInterface is missing a catch for IntegrityError |
295 | -#1360004 UI becomes unresponsive (unaccessible) if RPC to cluster fails |
296 | -#1360008 Data migration fails with django.db.utils.InternalError: current transaction is aborted, commands ignored until end of transaction block |
297 | -#1360676 KeyError raised importing boot images |
298 | -#1361799 absolute_reverse returns incorrect url if base_url is missing ending / |
299 | -#1362397 django.core.exceptions.ValidationError: {'power_state': [u'Ensure this value has at most 10 characters (it has 18).']} |
300 | -#1363105 Change in absolute_reverse breaks netbooting on installed MAAS |
301 | -#1363116 DHCP Probe timer service fails |
302 | -#1363138 DHCP Probe TimerService fails with 'NoneType' object has no attribute 'encode' |
303 | -#1363474 exceptions.KeyError: u'subarches' when syncing uploaded image from region to cluster |
304 | -#1363525 preseed path for generated tgz doesn't match actual path |
305 | -#1363722 Boot resource upload failed: error: length too large |
306 | + |
307 | #1363850 Auto-enlistment not reporting power parameters |
308 | + |
309 | #1363900 Dev server errors while trying to write to '/var/lib/maas' |
310 | + |
311 | #1363999 Not assigning static IP addresses |
312 | -#1364062 New download boot resources method doesn't use the configured proxy |
313 | + |
314 | #1364481 http 500 error doesn't contain a stack trace |
315 | + |
316 | #1364993 500 error when trying to acquire a commissioned node (AddrFormatError: failed to detect a valid IP address from None) |
317 | + |
318 | #1365130 django-admin prints spurious messages to stdout, breaking scripts |
319 | -#1365175 bootloader import code goes directly to archive.ubuntu.com rather than the configured archive |
320 | + |
321 | #1365850 DHCP scan using cluster interface name as network interface? |
322 | -#1366104 [FFe] OperationError when large object greater than 2gb |
323 | + |
324 | #1366172 NUC does not boot after power off/power on |
325 | + |
326 | #1366212 Large dhcp leases file leads to tftp timeouts |
327 | + |
328 | #1366652 Leaking temporary directories |
329 | -#1366726 CI breakage: Deployed nodes don't get a static IP address |
330 | + |
331 | #1368269 internal server error when deleting a node |
332 | + |
333 | #1368590 Power actions are not serialized. |
334 | + |
335 | #1370534 Recurrent update of the power state of nodes crashes if the connection to the BMC fails. |
336 | + |
337 | #1370958 excessive pserv logging |
338 | -#1371033 A node can get stuck in the 'RELEASING' state if the power change command fails to power down the node. |
339 | -#1371064 Spurious test failure: maasserver.rpc.tests.test_nodes.TestCreateNode.test_creates_node |
340 | -#1371236 power parameters for probe-and-enlist mscm no longer saved for enlisted nodes |
341 | -#1372408 PowerQuery RPC method crashes with exceptions.TypeError: get_power_state() got an unexpected keyword argument 'power_change' |
342 | -#1372732 ImportError running src/metadataserver/tests/test_fields.py |
343 | -#1372735 Deprecation warning breaks Node model tests |
344 | + |
345 | #1372767 Twisted web client does not support IPv6 address |
346 | + |
347 | #1372944 Twisted web client fails looking up IPv6 address hostname |
348 | + |
349 | #1373031 Cannot register cluster |
350 | + |
351 | #1373103 compose_curtin_network_preseed breaks installation of all other operating systems |
352 | -#1373207 Can't build package |
353 | -#1373237 maas-cluster-controller installation breaks: __main__.py: error: unrecognized arguments: -u maas -g maas |
354 | -#1373265 Where did the “Import boot images” button go? |
355 | -#1373357 register_event_type fails: already exists |
356 | + |
357 | #1373368 Conflicting power actions being dropped on the floor can result in leaving a node in an inconsistent state |
358 | -#1373477 Circular import between preseed.py and models/node.py |
359 | -#1373658 request_node_info_by_mac_address errors during enlistment: MACAddress matching query does not exist |
360 | + |
361 | #1373699 Cluster Listing Page lacks feedback about the images each cluster has |
362 | -#1373710 Machines fail to PXE Boot |
363 | + |
364 | #1374102 No retries for AMT power? |
365 | -#1374388 UI checkbox for Node.disable_ipv4 never unchecks |
366 | -#1374793 Cluster page no longer shows whether the cluster is connected or not. |
367 | -#1375594 After a fresh install, cluster can't connect to region |
368 | -#1375664 Node powering on but not deploying |
369 | -#1375835 Can't create node in the UI with 1.7 beta 4 |
370 | -#1375970 Timeout leads to inconsistency between maas and real world state, can't commission or start nodes |
371 | + |
372 | #1375980 Nodes failed to transition out of "New" state on bulk commission |
373 | -#1376000 oops: 'NoneType' object has no attribute 'encode' |
374 | + |
375 | #1376023 After performing bulk action on maas nodes, Internal Server Error |
376 | -#1376028 maasserver Unable to identify boot image for (ubuntu/amd64/generic/trusty/poweroff): cluster 'maas' does not have matching boot image. |
377 | -#1376031 WebUI became unresponsive after disconnecting Remote Cluster Controller (powered node off) |
378 | -#1376303 Can't commission a node: xceptions.AttributeError: 'NoneType' object has no attribute 'addCallback' |
379 | -#1376304 Timeout errors in RPC commands cause 500 errors |
380 | -#1376782 Node stuck with: "another action is already in progress for that node." |
381 | + |
382 | #1376888 Nodes can't be deleted if DHCP management is off. |
383 | + |
384 | #1377099 Bulk operation leaves nodes in inconsistent state |
385 | -#1377860 Nodes not configured with IPv6 DNS server address |
386 | -#1379154 "boot-images" link in the "Visit the boot images page to start the import." is a 404 |
387 | + |
388 | #1379209 When a node has multiple interfaces on a network MAAS manages, MAAS assigns static IP addresses to all of them |
389 | -#1379568 maas-cluster fails to register if the host has an IPv6 address |
390 | -#1379591 nodes with two interfaces fail to deploy in maas 1.7 beta5 |
391 | -#1379641 IPv6 netmasks aren't *always* 64 bits, but we only configure 64-bit ones |
392 | -#1379649 Invalid transition - 'Releasing Failed' to 'Disk Erasing' |
393 | + |
394 | #1379744 Cluster registration is fragile and insecure |
395 | -#1379924 maas 1.7 flooded with OOPSs |
396 | -#1380927 Default Cluster does not autoconnect after a fresh install |
397 | + |
398 | #1380932 MAAS does not cope with changes of the dhcp daemons |
399 | + |
400 | #1381605 Not all the DNS records are being added when deploying multiple nodes |
401 | -#1381714 Nodes release API bypasses disk erase |
402 | + |
403 | #1012954 If a power script fails, there is no UI feedback |
404 | -#1057250 TestGetLongpollContext.test_get_longpoll_context is causing test failures in metadataserver |
405 | + |
406 | #1186196 "Starting a node" has different meanings in the UI and in the API. |
407 | + |
408 | #1237215 maas and curtin do not indicate failure reasonably |
409 | + |
410 | #1273222 MAAS doesn't check return values of power actions |
411 | + |
412 | #1288502 archive and proxy settings not honoured for commissioning |
413 | -#1300554 If the rabbit password changes, clusters are not informed |
414 | -#1315161 cannot deploy Windows |
415 | + |
416 | #1316919 Checks don't exist to confirm a node will actually boot |
417 | + |
418 | #1321885 IPMI detection and automatic setting fail in ubuntu 14.04 maas |
419 | + |
420 | #1325610 node marked "Ready" before poweroff complete |
421 | + |
422 | #1325638 Add hardware enablement for Universal Management Gateway |
423 | -#1333954 global registry of license keys |
424 | -#1334963 Nodegroupinterface.clean_ip_ranges() is very slow with large networks |
425 | -#1337437 [SRU] maas needs utopic support |
426 | -#1338169 Non-Ubuntu preseed templates are not tested |
427 | -#1339868 No way to list supported operating systems via RPC |
428 | -#1339903 No way to validate an OS license key via RPC |
429 | + |
430 | #1340188 unallocated node started manually, causes AssertionError for purpose poweroff |
431 | -#1340305 No way to get the title for a release from OperatingSystem |
432 | + |
433 | #1341118 No feedback when IPMI credentials fail |
434 | + |
435 | #1341121 No feedback to user when cluster is not running |
436 | + |
437 | #1341581 power state is not represented in api and ui |
438 | -#1341619 NodeGroupInterface is not linked to Network |
439 | -#1341772 No way to get extra preseed data from OperatingSystem via RPC |
440 | + |
441 | #1341800 MAAS doesn't support soft power off through the API |
442 | -#1343425 deprecate use-fastpath-installer tag and use a property on node instead |
443 | + |
444 | #1344177 hostnames can't be changed while a node is acquired |
445 | + |
446 | #1347518 Confusing error message when API key is wrong |
447 | + |
448 | #1349496 Unable to request a specific static IP on the API |
449 | + |
450 | #1349736 MAAS logging is too verbose and not very useful |
451 | + |
452 | #1349917 guess_server_address() can return IPAddress or hostname |
453 | + |
454 | #1350103 No support for armhf/keystone architecture |
455 | + |
456 | #1350856 Can't constrain acquisition of nodes by not having a tag |
457 | -#1350948 IPMI power template treats soft as an option rather than a command |
458 | -#1354014 clusters should sync boot images from the region |
459 | -#1356490 Metadataserver api needs tests for _store_installing_results |
460 | -#1356780 maaslog items are logged twice |
461 | + |
462 | #1356880 MAAS shouldn't allow changing the hostname of a deployed node |
463 | -#1357071 When a power template fails, the content of the event from the node event log is not readable (it contains the whole template) |
464 | -#1357685 docs/bootsources.rst:: WARNING: document isn't included in any toctree |
465 | + |
466 | #1357714 Virsh power driver does not seem to work at all |
467 | -#1358177 maas-region-admin requires root privileges [docs] |
468 | -#1358337 [docs] MAAS documentation suggests to execute 'juju --sync-tools' |
469 | -#1358829 IPMI power query fails when trying to commit config changes |
470 | + |
471 | #1358859 Commissioning output xml is hard to understand, would be nice to have yaml as an output option. |
472 | + |
473 | #1359169 MAAS should handle invalid consumers gracefully |
474 | + |
475 | #1359822 Gateway is missing in network definition |
476 | -#1361897 exceptions in PeriodicImageDownloadService will cause it to stop running |
477 | -#1361941 erlang upgrade makes maas angry |
478 | -#1361967 NodePowerMonitorService has no tests |
479 | + |
480 | #1363913 Impossible to remove last MAC from network in UI |
481 | + |
482 | #1364228 Help text for node hostname is wrong |
483 | + |
484 | #1364591 MAAS Archive Mirror does not respect non-default port |
485 | -#1364617 ipmipower returns a zero exit status when password invalid |
486 | -#1364713 selenium test will not pass with new Firefox |
487 | + |
488 | #1365616 Non-admin access to cluster controller config |
489 | + |
490 | #1365619 DNS should be an optional field in the network definition |
491 | -#1365722 NodeStateViolation when commissioning |
492 | -#1365742 Logged OOPS ... NoSuchEventType: Event type with name=NODE_POWER_ON_FAILED could not be found. |
493 | + |
494 | #1365776 commissioning results view for a node also shows installation results |
495 | + |
496 | #1366812 Old boot resources are not being removed on clusters |
497 | + |
498 | #1367455 MAC address for node's IPMI is reversed looked up to yield IP address using case sensitive comparison |
499 | -#1368398 Can't mark systems that 'Failed commissioning' as 'Broken' |
500 | -#1368916 No resources found in Simplestreams repository |
501 | -#1370860 Node power monitor doesn't cope with power template answers other than "on" or "off" |
502 | -#1370887 No event is registered on a node for when the power monitor sees a problem |
503 | -#1371663 Node page Javascript crashes when there is no lshw output to display yet |
504 | -#1371763 Need to use RPC for validating license key. |
505 | -#1372974 No "installation complete" event |
506 | -#1373272 "No boot images are available.…" message doesn't disappear when images are imported |
507 | + |
508 | #1373580 [SRU] Glen m700 cartridge list as ARM64/generic after enlist |
509 | + |
510 | #1373723 Releasing a node without power parameters ends up in not being able to release a node |
511 | -#1373727 PXE node event logs provide too much info |
512 | -#1373900 New install of MAAS can't download boot images |
513 | -#1374153 Stuck in "power controller problem" |
514 | -#1374321 Internal server error when attempting to perform an action when the cluster is down |
515 | -#1375360 Automatic population of managed networks for eth1 and beyond |
516 | -#1375427 Need to remove references to older import images button |
517 | -#1375647 'static-ipaddresses' capability in 1.6 not documented. |
518 | -#1375681 "Importing images . . ." message on the image page never disappears |
519 | -#1375953 bootsourcecache is not refreshed when sources change |
520 | -#1376016 MAAS lacks a setting for the Simple Streams Image repository location |
521 | -#1376481 Wrong error messages in UI |
522 | -#1376620 maas-url config question doesn't make clear that localhost won't do |
523 | -#1376990 Elusive JavaScript lint |
524 | -#1378366 When there are no images, clusters should show that there |
525 | -#1378527 Images UI doesn't handle HWE images |
526 | -#1378643 Periodic test failure for compose_curtin_network_preseed_for |
527 | -#1378837 "Abort operation" action name is vague and misleading |
528 | -#1378910 Call the install log 'install log' rather than 'curtin log' |
529 | -#1379401 Race in EventManager.register_event_and_event_type |
530 | -#1379816 disable_ipv4 has a default setting on the cluster, but it's not visible |
531 | -#1380470 Event log says node was allocated but doesn't say to *whom* |
532 | -#1380805 uprade from 1.5.4 to 1.7 overwrote my cluster name |
533 | -#1381007 "Acquire and start node" button appears on node page for admins who don't own an allocated but unstarted node |
534 | -#1381213 mark_fixed should clear the osystem and distro_series fields |
535 | -#1381747 APIRPCErrorsMiddleware isn't installed |
536 | -#1381796 license_key is not given in the curtin_userdata preseed for Windows |
537 | -#1172773 Web UI has no indication of image download status. |
538 | + |
539 | #1233158 no way to get power parameters in api |
540 | + |
541 | #1319854 `maas login` tells you you're logged in successfully when you're not |
542 | -#1351451 Impossible to release a BROKEN node via the API. |
543 | -#1361040 Weird log message: "Power state has changed from unknown to connection timeout." |
544 | -#1366170 Node Event log doesn't currently display anything apart from power on/off |
545 | + |
546 | #1368480 Need API to gather image metadata across all of MAAS |
547 | -#1370306 commissioning output XML and YAML tabs are not vertical |
548 | -#1371122 WindowsBootMethod request pxeconfig from API for every file |
549 | -#1376030 Unable to get RPC connection for cluster 'maas' <-- 'maas' is the DNS zone name |
550 | -#1378358 Missing images warning should contain a link to images page |
551 | + |
552 | #1281406 Disk/memory space on Node edit page have no units |
553 | + |
554 | #1299231 MAAS DHCP/DNS can't manage more than a /16 network |
555 | + |
556 | #1357381 maas-region-admin createadmin shows error if not params given |
557 | -#1357686 Caching in get_worker_user() looks like premature optimisation |
558 | -#1358852 Tons of Linking <mac address> to <cluster interface> spam in log |
559 | -#1359178 Docs - U1 still listed for uploading data |
560 | -#1359947 Spelling Errors/Inconsistencies with MAAS Documentation |
561 | -#1365396 UI: top link to “<name> MAAS” only appears on some pages |
562 | -#1365591 "Start node" UI button does not allocate node before starting in 1.7 |
563 | -#1365603 No "stop node" button on the page of a node with status "failed deployment" |
564 | -#1371658 Wasted space in the "Discovery data" section of the node page |
565 | + |
566 | #1376393 powerkvm boot loader installs even when not needed |
567 | -#1376956 commissioning results page with YAML/XML output tabs are not centered on page. |
568 | + |
569 | #1287224 MAAS random generated hostnames are not pronounceable |
570 | + |
571 | #1348364 non-maas managed subnets cannot query maas DNS |
572 | -#1381543 Disabling Disk Erasing with node in 'Failed Erasing' state leads to Invalid transition: Failed disk erasing -> Ready. |
573 | + |
574 | |
575 | 1.6.1 |
576 | ===== |