Activity log for bug #1572695

Date Who What changed Old value New value Message
2016-04-20 18:52:20 Seman bug added bug
2016-04-20 18:53:37 Seman bug added subscriber Andrew Wilkins
2016-04-20 18:54:35 Seman description When add-machine fails, automatic retry creates additional machines with identical IP address: machine 0 and 1 have same dns-name http://reports.vapour.ws/releases/3908/job/manual-deploy-precise-amd64/attempt/3419 2016-04-20 13:55:01 INFO juju --debug add-machine -m manual-deploy-precise-amd64 ssh:ec2-54-175-67-11.compute-1.amazonaws.com ... 2016-04-20 13:55:08 ERROR juju.environs.manual provisioner.go:114 cannot obtain provisioning script 2016-04-20 13:55:08 DEBUG juju.api apiclient.go:520 health ping failed: connection is shut down 2016-04-20 13:55:08 ERROR cmd supercommand.go:448 getting instance config: finding tools: EOF 2016-04-20 13:55:08 WARNING add-machine failed. Will retry. Sleeping for 30 seconds. 2016-04-20 13:55:38 INFO juju --debug add-machine -m manual-deploy-precise-amd64 ssh:ec2-54-175-67-11.compute-1.amazonaws.com ... 2016-04-20 13:57:00 INFO juju --debug add-machine -m manual-deploy-precise-amd64 ssh:ec2-54-86-247-44.compute-1.amazonaws.com http://reports.vapour.ws/releases/3908/job/manual-deploy-precise-amd64/attempt/3419model: manual-deploy-precise-amd64 machines: "0": juju-status: current: pending since: 20 Apr 2016 13:54:23Z dns-name: ec2-54-175-67-11.compute-1.amazonaws.com instance-id: manual:ec2-54-175-67-11.compute-1.amazonaws.com machine-status: current: pending since: 20 Apr 2016 13:54:23Z series: precise hardware: arch=amd64 cpu-cores=1 mem=7450M "1": juju-status: current: started since: 20 Apr 2016 13:56:16Z version: 2.0-beta5 dns-name: ec2-54-175-67-11.compute-1.amazonaws.com instance-id: manual:ec2-54-175-67-11.compute-1.amazonaws.com machine-status: current: pending since: 20 Apr 2016 13:55:00Z series: precise hardware: arch=amd64 cpu-cores=1 mem=7450M "2": juju-status: current: started since: 20 Apr 2016 13:57:30Z version: 2.0-beta5 dns-name: ec2-54-86-247-44.compute-1.amazonaws.com instance-id: manual:ec2-54-86-247-44.compute-1.amazonaws.com machine-status: current: pending since: 20 Apr 2016 13:56:23Z series: precise hardware: arch=amd64 cpu-cores=1 mem=7450M services: dummy-sink: charm: local:precise/dummy-sink-0 exposed: true service-status: current: unknown since: 20 Apr 2016 13:57:40Z relations: source: - dummy-source units: dummy-sink/0: workload-status: current: unknown since: 20 Apr 2016 13:57:40Z juju-status: current: idle since: 20 Apr 2016 14:07:40Z version: 2.0-beta5 machine: "1" public-address: ec2-54-175-67-11.compute-1.amazonaws.com dummy-source: charm: local:precise/dummy-source-0 exposed: false service-status: current: unknown message: Waiting for agent initialization to finish since: 20 Apr 2016 13:57:32Z relations: sink: - dummy-sink units: dummy-source/0: workload-status: current: unknown message: Waiting for agent initialization to finish since: 20 Apr 2016 13:57:32Z juju-status: current: allocating since: 20 Apr 2016 13:57:32Z machine: "0" public-address: ec2-54-175-67-11.compute-1.amazonaws.com When add-machine fails, automatic retry creates additional machines with identical IP address: machine 0 and 1 have same dns-name http://reports.vapour.ws/releases/3908/job/manual-deploy-precise-amd64/attempt/3419 2016-04-20 13:55:01 INFO juju --debug add-machine -m manual-deploy-precise-amd64 ssh:ec2-54-175-67-11.compute-1.amazonaws.com ... 2016-04-20 13:55:08 ERROR juju.environs.manual provisioner.go:114 cannot obtain provisioning script 2016-04-20 13:55:08 DEBUG juju.api apiclient.go:520 health ping failed: connection is shut down 2016-04-20 13:55:08 ERROR cmd supercommand.go:448 getting instance config: finding tools: EOF 2016-04-20 13:55:08 WARNING add-machine failed. Will retry. Sleeping for 30 seconds. 2016-04-20 13:55:38 INFO juju --debug add-machine -m manual-deploy-precise-amd64 ssh:ec2-54-175-67-11.compute-1.amazonaws.com ... 2016-04-20 13:57:00 INFO juju --debug add-machine -m manual-deploy-precise-amd64 ssh:ec2-54-86-247-44.compute-1.amazonaws.com manual-deploy-precise-amd64 machines:   "0":     juju-status:       current: pending       since: 20 Apr 2016 13:54:23Z     dns-name: ec2-54-175-67-11.compute-1.amazonaws.com     instance-id: manual:ec2-54-175-67-11.compute-1.amazonaws.com     machine-status:       current: pending       since: 20 Apr 2016 13:54:23Z     series: precise     hardware: arch=amd64 cpu-cores=1 mem=7450M   "1":     juju-status:       current: started       since: 20 Apr 2016 13:56:16Z       version: 2.0-beta5     dns-name: ec2-54-175-67-11.compute-1.amazonaws.com     instance-id: manual:ec2-54-175-67-11.compute-1.amazonaws.com     machine-status:       current: pending       since: 20 Apr 2016 13:55:00Z     series: precise     hardware: arch=amd64 cpu-cores=1 mem=7450M   "2":     juju-status:       current: started       since: 20 Apr 2016 13:57:30Z       version: 2.0-beta5     dns-name: ec2-54-86-247-44.compute-1.amazonaws.com     instance-id: manual:ec2-54-86-247-44.compute-1.amazonaws.com     machine-status:       current: pending       since: 20 Apr 2016 13:56:23Z     series: precise     hardware: arch=amd64 cpu-cores=1 mem=7450M services:   dummy-sink:     charm: local:precise/dummy-sink-0     exposed: true     service-status:       current: unknown       since: 20 Apr 2016 13:57:40Z     relations:       source:       - dummy-source     units:       dummy-sink/0:         workload-status:           current: unknown           since: 20 Apr 2016 13:57:40Z         juju-status:           current: idle           since: 20 Apr 2016 14:07:40Z           version: 2.0-beta5         machine: "1"         public-address: ec2-54-175-67-11.compute-1.amazonaws.com   dummy-source:     charm: local:precise/dummy-source-0     exposed: false     service-status:       current: unknown       message: Waiting for agent initialization to finish       since: 20 Apr 2016 13:57:32Z     relations:       sink:       - dummy-sink     units:       dummy-source/0:         workload-status:           current: unknown           message: Waiting for agent initialization to finish           since: 20 Apr 2016 13:57:32Z         juju-status:           current: allocating           since: 20 Apr 2016 13:57:32Z         machine: "0"         public-address: ec2-54-175-67-11.compute-1.amazonaws.com
2016-04-21 06:46:34 Seman summary Manual add-machine creates additional broken machine Manual-provider add-machine creates additional broken machine
2016-04-24 17:38:38 Curtis Hovey summary Manual-provider add-machine creates additional broken machine Manual-provider add-machine uses duplicate ip addresses
2016-04-25 23:28:50 Curtis Hovey juju-core: milestone 2.0-beta6 2.0-beta7
2016-05-13 16:22:38 Curtis Hovey juju-core: milestone 2.0-beta7 2.0-beta8
2016-05-18 18:13:07 Curtis Hovey tags ci intermittent-failure manual-provider precise ci intermittent-failure manual-provider manual-story precise
2016-05-26 12:19:40 Cheryl Jennings juju-core: milestone 2.0-beta8 2.0-rc1
2016-08-09 13:50:18 Anastasia juju-core: milestone 2.0-rc1 2.0.0
2016-08-23 00:12:09 Canonical Juju QA Bot affects juju-core juju
2016-08-23 00:12:09 Canonical Juju QA Bot juju: milestone 2.0.0
2016-08-23 00:12:13 Canonical Juju QA Bot juju: milestone 2.0.0
2016-09-09 22:39:46 Richard Harding juju: milestone 2.0.0 2.0.1
2016-10-28 13:27:37 Curtis Hovey juju: milestone 2.0.1
2017-02-14 01:14:12 Curtis Hovey juju: importance High Medium
2018-02-19 00:37:46 Tim Penhey tags ci intermittent-failure manual-provider manual-story precise ci manual-provider manual-story precise
2022-11-03 15:29:52 Canonical Juju QA Bot juju: importance Medium Low
2022-11-03 15:29:53 Canonical Juju QA Bot tags ci manual-provider manual-story precise ci expirebugs-bot manual-provider manual-story precise