Activity log for bug #1604962

Date Who What changed Old value New value Message
2016-07-20 20:58:56 Jason Hobbs bug added bug
2016-07-20 20:58:56 Jason Hobbs attachment added hayward-11-logs.tgz https://bugs.launchpad.net/bugs/1604962/+attachment/4704263/+files/hayward-11-logs.tgz
2016-07-20 21:52:26 Andres Rodriguez nominated for series maas/2.0
2016-07-20 21:52:26 Andres Rodriguez bug task added maas/2.0
2016-07-20 21:52:26 Andres Rodriguez nominated for series maas/trunk
2016-07-20 21:52:26 Andres Rodriguez bug task added maas/trunk
2016-07-22 13:36:23 Adam Stokes tags oil conjure oil
2016-07-22 15:30:34 Andres Rodriguez bug task added curtin
2016-07-22 18:45:13 Scott Moser curtin: importance Undecided Medium
2016-07-22 18:45:13 Scott Moser curtin: status New Confirmed
2016-07-23 13:41:30 Launchpad Janitor branch linked lp:~andreserl/maas/lp1604962_lp1604987
2016-07-25 23:15:27 MAAS Lander maas/trunk: status New Fix Committed
2016-07-25 23:26:36 Launchpad Janitor branch linked lp:~andreserl/maas/lp1604962_lp1604987_2.0
2016-07-26 00:12:45 MAAS Lander maas/2.0: status New Fix Committed
2016-07-26 00:36:03 Andres Rodriguez maas/2.0: importance Undecided Critical
2016-07-26 00:36:04 Andres Rodriguez maas/trunk: importance Undecided Critical
2016-07-26 00:36:08 Andres Rodriguez maas/2.0: milestone 2.0.0
2016-07-26 00:36:10 Andres Rodriguez maas/trunk: milestone 2.1.0
2016-07-27 17:24:03 Scott Moser description A node reached the end of installation and was marked Failed Deployment, but I can't discover the reason it was marked that. I've attached logs from the MAAS server, and the event log, and the install log. In the event log we see this: { "type": "Node changed status", "level": "INFO", "node": "4y3hdg", "hostname": "hayward-11", "id": 1436389, "description": "From 'Deploying' to 'Failed deployment'", "created": "Wed, 20 Jul. 2016 01:01:00" }, { "type": "Node installation", "level": "DEBUG", "node": "4y3hdg", "hostname": "hayward-11", "id": 1436388, "description": "'cloudinit' running modules for final", "created": "Wed, 20 Jul. 2016 01:01:00" }, In the install log we see this: Length: unspecified [text/plain] Saving to: '/dev/null' 0K 138K=0s 2016-07-20 01:00:50 (138 KB/s) - '/dev/null' saved [2] curtin: Installation finished. This is from this run: http://10.245.162.43:8080/job/pipeline_deploy/8151/console This is with juju 2.0 beta 12 and maas 2.0 RC2. A node reached the end of installation and was marked Failed Deployment, but I can't discover the reason it was marked that. I've attached logs from the MAAS server, and the event log, and the install log. In the event log we see this:         {             "type": "Node changed status",             "level": "INFO",             "node": "4y3hdg",             "hostname": "hayward-11",             "id": 1436389,             "description": "From 'Deploying' to 'Failed deployment'",             "created": "Wed, 20 Jul. 2016 01:01:00"         },         {             "type": "Node installation",             "level": "DEBUG",             "node": "4y3hdg",             "hostname": "hayward-11",             "id": 1436388,             "description": "'cloudinit' running modules for final",             "created": "Wed, 20 Jul. 2016 01:01:00"         }, In the install log we see this: Length: unspecified [text/plain] Saving to: '/dev/null'      0K 138K=0s 2016-07-20 01:00:50 (138 KB/s) - '/dev/null' saved [2] curtin: Installation finished. This is from this run: http://10.245.162.43:8080/job/pipeline_deploy/8151/console This is with juju 2.0 beta 12 and maas 2.0 RC2. Related Bugs: * bug 1606999: reporting messages can slow down operations greatly
2016-07-27 23:19:52 Launchpad Janitor branch linked lp:~andreserl/maas/packaging_rc3
2016-08-22 15:44:06 Andres Rodriguez maas/2.0: status Fix Committed Fix Released
2016-08-22 16:34:04 Andres Rodriguez maas: status Fix Committed Fix Released
2016-08-22 16:37:20 Andres Rodriguez maas/trunk: milestone 2.0.1
2016-09-22 18:16:15 Andreas Hasenack attachment added cloud-init-logs.txt https://bugs.launchpad.net/maas/+bug/1604962/+attachment/4746381/+files/cloud-init-logs.txt
2016-09-22 19:09:43 Jon Grimm bug added subscriber Jon Grimm
2016-09-22 20:53:02 Scott Moser branch linked lp:~smoser/curtin/trunk.lp1604962
2016-12-01 18:44:35 David Britton bug task added landscape
2016-12-01 18:44:43 David Britton landscape: milestone 16.11
2016-12-01 18:44:49 David Britton tags conjure oil conjure landscape oil
2016-12-01 18:50:19 David Britton landscape: status New Confirmed
2016-12-01 19:02:20 David Britton tags conjure landscape oil cdo-qa-blocker conjure landscape oil
2016-12-07 09:01:57 Blake Rouse maas/trunk: status Fix Released In Progress
2016-12-07 09:02:00 Blake Rouse maas/trunk: milestone 2.2.0
2016-12-07 09:02:04 Blake Rouse bug task deleted maas/2.0
2016-12-07 09:02:12 Blake Rouse nominated for series maas/2.1
2016-12-07 09:02:12 Blake Rouse bug task added maas/2.1
2016-12-07 09:02:22 Blake Rouse maas/2.1: status New In Progress
2016-12-07 09:02:25 Blake Rouse maas/2.1: importance Undecided Critical
2016-12-07 09:02:28 Blake Rouse maas/2.1: status In Progress Triaged
2016-12-07 09:02:31 Blake Rouse maas/2.1: milestone 2.1.3
2016-12-07 09:25:43 Launchpad Janitor branch linked lp:~blake-rouse/maas/deploy-cloudinit-reboot
2016-12-08 09:12:37 MAAS Lander maas/trunk: status In Progress Fix Committed
2016-12-08 13:10:31 Blake Rouse maas/trunk: assignee Blake Rouse (blake-rouse)
2016-12-08 13:10:33 Blake Rouse maas/2.1: assignee Blake Rouse (blake-rouse)
2016-12-08 13:10:40 Blake Rouse maas/2.1: status Triaged In Progress
2016-12-08 13:46:49 Launchpad Janitor branch linked lp:~blake-rouse/maas/deploy-cloudinit-reboot-2.1
2016-12-08 17:01:59 MAAS Lander maas/2.1: status In Progress Fix Committed
2017-01-03 17:53:11 Andreas Hasenack landscape: milestone 16.11 16.12
2017-01-18 11:52:12 Andreas Hasenack landscape: milestone 16.12 17.01
2017-01-25 12:56:37 Andreas Hasenack bug added subscriber Landscape
2017-01-25 13:52:29 Andres Rodriguez maas/2.1: status Fix Committed Fix Released
2017-01-25 14:02:57 Andres Rodriguez maas/trunk: status Fix Committed Fix Released
2017-02-10 20:55:08 Chad Smith landscape: milestone 17.01 17.02
2017-03-16 14:52:37 Chad Smith landscape: status Confirmed Incomplete
2017-03-16 15:20:32 Chad Smith landscape: milestone 17.02 17.03
2017-03-21 15:26:17 Scott Moser bug task deleted curtin
2017-03-21 15:41:35 Scott Moser description A node reached the end of installation and was marked Failed Deployment, but I can't discover the reason it was marked that. I've attached logs from the MAAS server, and the event log, and the install log. In the event log we see this:         {             "type": "Node changed status",             "level": "INFO",             "node": "4y3hdg",             "hostname": "hayward-11",             "id": 1436389,             "description": "From 'Deploying' to 'Failed deployment'",             "created": "Wed, 20 Jul. 2016 01:01:00"         },         {             "type": "Node installation",             "level": "DEBUG",             "node": "4y3hdg",             "hostname": "hayward-11",             "id": 1436388,             "description": "'cloudinit' running modules for final",             "created": "Wed, 20 Jul. 2016 01:01:00"         }, In the install log we see this: Length: unspecified [text/plain] Saving to: '/dev/null'      0K 138K=0s 2016-07-20 01:00:50 (138 KB/s) - '/dev/null' saved [2] curtin: Installation finished. This is from this run: http://10.245.162.43:8080/job/pipeline_deploy/8151/console This is with juju 2.0 beta 12 and maas 2.0 RC2. Related Bugs: * bug 1606999: reporting messages can slow down operations greatly A node reached the end of installation and was marked Failed Deployment, but I can't discover the reason it was marked that. I've attached logs from the MAAS server, and the event log, and the install log. In the event log we see this:         {             "type": "Node changed status",             "level": "INFO",             "node": "4y3hdg",             "hostname": "hayward-11",             "id": 1436389,             "description": "From 'Deploying' to 'Failed deployment'",             "created": "Wed, 20 Jul. 2016 01:01:00"         },         {             "type": "Node installation",             "level": "DEBUG",             "node": "4y3hdg",             "hostname": "hayward-11",             "id": 1436388,             "description": "'cloudinit' running modules for final",             "created": "Wed, 20 Jul. 2016 01:01:00"         }, In the install log we see this: Length: unspecified [text/plain] Saving to: '/dev/null'      0K 138K=0s 2016-07-20 01:00:50 (138 KB/s) - '/dev/null' saved [2] curtin: Installation finished. This is from this run: http://10.245.162.43:8080/job/pipeline_deploy/8151/console This is with juju 2.0 beta 12 and maas 2.0 RC2. Related Bugs:  * bug 1606999: reporting messages can slow down operations greatly * bug 1674734: [curtin] if invoked by init, should wait until cloud-init is finished for reboot
2017-03-28 18:09:03 David Britton bug task deleted landscape