Activity log for bug #1645478

Date Who What changed Old value New value Message
2016-11-28 21:24:46 Curtis Hovey bug added bug
2016-11-28 21:25:08 Curtis Hovey juju: assignee Alexis Bruemmer (alexis-bruemmer)
2016-11-28 21:25:47 Curtis Hovey juju: milestone 2.1-beta2
2016-11-28 22:44:55 Curtis Hovey tags ci model-config regression upgrade-juju ci model-config openstack-provider regression upgrade-juju
2016-11-28 22:45:57 Curtis Hovey description As seen at http://reports.vapour.ws/releases/issue/563c3bae749a5650a6256ca4 get_juju_output raises when calling out to the juju client after an upgrade, retries succeed. This might be a timing case where the controller hiccuped after the upgrade. The call to status reports that all machines and units upgraded. As seen at     http://reports.vapour.ws/releases/issue/563c3bae749a5650a6256ca4 get_juju_output raises when calling out to the juju client after an upgrade, retries succeed. This might be a timing case where the controller hiccuped after the upgrade. The call to status reports that all machines and units upgraded. This is only seen in openstack upgrades. maas, lxc, aws did not fail.
2016-11-29 23:38:53 Alexis Bruemmer juju: assignee Alexis Bruemmer (alexis-bruemmer) Ian Booth (wallyworld)
2016-11-30 04:53:54 Ian Booth bug task added juju-ci-tools
2016-11-30 04:54:38 Ian Booth juju: status Triaged Incomplete
2016-12-01 01:21:20 Anastasia juju: milestone 2.1-beta2
2016-12-01 15:18:01 Aaron Bentley juju: status Incomplete Triaged
2016-12-01 15:18:11 Aaron Bentley juju-ci-tools: status New Incomplete
2016-12-01 16:28:51 Aaron Bentley branch linked lp:~sinzui/juju-ci-tools/wait-for-upgrade
2016-12-01 18:09:37 Curtis Hovey summary juju model-config errors after upgrade Juju does not state it is upgrading
2016-12-01 18:28:08 Curtis Hovey description As seen at     http://reports.vapour.ws/releases/issue/563c3bae749a5650a6256ca4 get_juju_output raises when calling out to the juju client after an upgrade, retries succeed. This might be a timing case where the controller hiccuped after the upgrade. The call to status reports that all machines and units upgraded. This is only seen in openstack upgrades. maas, lxc, aws did not fail. As seen at     http://reports.vapour.ws/releases/issue/563c3bae749a5650a6256ca4 get_juju_output raises when calling out to the juju client after an upgrade, retries succeed. This might be a timing case where the controller hiccuped after the upgrade. The call to status reports that all machines and units upgraded. This is only seen in lxd, manual, and openstack upgrades. maas, aws did not fail. The root issue is that there is no way to see an upgrade is in progress until you get an error.
2016-12-01 23:00:30 Curtis Hovey tags ci model-config openstack-provider regression upgrade-juju ci model-config openstack-provider regression ui upgrade-juju
2017-01-03 23:55:55 Horacio Durán juju: assignee Ian Booth (wallyworld) Horacio Durán (hduran-8)
2017-01-03 23:56:03 Horacio Durán juju: status Triaged In Progress
2017-01-10 03:27:59 Anastasia juju: milestone 2.2.0-alpha1
2017-02-12 15:06:51 Nobuto Murata bug added subscriber Nobuto Murata
2017-03-16 04:23:27 Anastasia juju: milestone 2.2-alpha1 2.2-beta1
2017-03-22 09:01:26 Anastasia juju: assignee Horacio Durán (hduran-8) John A Meinel (jameinel)
2017-03-23 07:55:24 Anastasia juju: status In Progress Fix Committed
2017-05-15 13:58:06 Curtis Hovey removed subscriber Curtis Hovey
2017-06-28 23:17:06 Canonical Juju QA Bot juju: status Fix Committed Fix Released