Activity log for bug #1658837

Date Who What changed Old value New value Message
2017-01-24 00:07:53 Curtis Hovey bug added bug
2017-01-25 18:52:50 Curtis Hovey juju-ci-tools: importance High Medium
2017-02-09 20:30:44 Curtis Hovey summary CI maas cleanup script selected network instead of hostname Race in maas setup/teardown
2017-02-09 20:31:01 Curtis Hovey description As seen at http://reports.vapour.ws/releases/issue/57c721c7749a5615669b72dc The mass cleanup script that resets networks in the bindings test failed to match the hostname (machine=) to look up the system id that needs reseting. the test failed to setup. ++ grep 10.0.40.0/24@ ++ cut -d @ -f2 + system_id= + maas env20 machine release ^ We expected the grep to be for name like juju-qa-maas-node-40 but machine=10.0.40.0/24 was selected previously As seen at    http://reports.vapour.ws/releases/issue/57c721c7749a5615669b72dc http://reports.vapour.ws/releases/issue/56f3c6ae749a5672accf4402 The mass cleanup script that resets networks in the bindings test failed to match the hostname (machine=) to look up the system id that needs reseting. the test failed to setup. ++ grep 10.0.40.0/24@ ++ cut -d @ -f2 + system_id= + maas env20 machine release ^ We expected the grep to be for name like juju-qa-maas-node-40 but machine=10.0.40.0/24 was selected previously
2017-02-09 20:32:52 Curtis Hovey description As seen at    http://reports.vapour.ws/releases/issue/57c721c7749a5615669b72dc http://reports.vapour.ws/releases/issue/56f3c6ae749a5672accf4402 The mass cleanup script that resets networks in the bindings test failed to match the hostname (machine=) to look up the system id that needs reseting. the test failed to setup. ++ grep 10.0.40.0/24@ ++ cut -d @ -f2 + system_id= + maas env20 machine release ^ We expected the grep to be for name like juju-qa-maas-node-40 but machine=10.0.40.0/24 was selected previously As seen at    http://reports.vapour.ws/releases/issue/57c721c7749a5615669b72dc    http://reports.vapour.ws/releases/issue/56f3c6ae749a5672accf4402 The endpoint-bindings test does not wait for machines and resources to enter the right state before adding/removing subnets and spaces. Clean up scripts were written to recover from the problem, but they too can fail because of race conditions. The mass cleanup script that resets networks in the bindings test failed to match the hostname (machine=) to look up the system id that needs reseting. the test failed to setup. ++ grep 10.0.40.0/24@ ++ cut -d @ -f2 + system_id= + maas env20 machine release ^ We expected the grep to be for name like juju-qa-maas-node-40 but machine=10.0.40.0/24 was selected previously
2017-02-23 23:28:45 Curtis Hovey juju-ci-tools: importance Medium Low
2017-05-15 13:58:25 Curtis Hovey removed subscriber Curtis Hovey