Public bug reported:
I tried to create a new undercloud on the server team's serverstack test
environment; I realized shortly after starting the juju-deployer that I
had made a mistake and used ^C to interrupt the deploy, to save ten
minutes of time, and then juju destroy-environment hung when trying to
clean up my mess:
$ juju-deployer -v --bootstrap -c default.yaml -d trusty-icehouse
2015-03-24 22:25:08 [DEBUG] deployer.cli: Using runtime GoEnvironment on secteam
2015-03-24 22:25:08 [INFO] deployer.cli: Starting deployment of trusty-icehouse
2015-03-24 22:25:08 [DEBUG] deployer.import: Getting charms...
2015-03-24 22:25:33 [DEBUG] deployer.deploy: Resolving configuration
2015-03-24 22:25:33 [INFO] deployer.env: bootstraping, this might take a
while...
^CTraceback (most recent call last):
File "/usr/bin/juju-deployer", line 9, in <module>
load_entry_point('juju-deployer==0.4.3', 'console_scripts',
'juju-deployer')()
File "/usr/lib/python2.7/dist-packages/deployer/cli.py", line 130, in main
run()
File "/usr/lib/python2.7/dist-packages/deployer/cli.py", line 228, in run
importer.Importer(env, deployment, options).run()
File "/usr/lib/python2.7/dist-packages/deployer/action/importer.py", line
193, in run
self.env.bootstrap()
File "/usr/lib/python2.7/dist-packages/deployer/env/base.py", line 71, in
bootstrap
params, self.log, "Failed to bootstrap")
File "/usr/lib/python2.7/dist-packages/deployer/env/base.py", line 21, in
_check_call
return _check_call(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/deployer/utils.py", line 253, in
_check_call
params, cwd=cwd, stderr=stderr, env=os.environ)
File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
output, unused_err = process.communicate()
File "/usr/lib/python2.7/subprocess.py", line 791, in communicate
stdout = _eintr_retry_call(self.stdout.read)
File "/usr/lib/python2.7/subprocess.py", line 476, in _eintr_retry_call
return func(*args)
KeyboardInterrupt
ubuntu@secteam-bastion:~/openstack-charm-testing$ ^C
ubuntu@secteam-bastion:~/openstack-charm-testing$ ^C
ubuntu@secteam-bastion:~/openstack-charm-testing$ ^C
ubuntu@secteam-bastion:~/openstack-charm-testing$ ^C
ubuntu@secteam-bastion:~/openstack-charm-testing$ ^C
ubuntu@secteam-bastion:~/openstack-charm-testing$ juju destroy-environment
secteam
WARNING! this command will destroy the "secteam" environment (type: openstack)
This includes all machines, services, data and other resources.
Continue [y/N]? y
^C
$ dpkg -l '*juju*' | awk 'OFS="\t" {print $1, $2, $3, $4}'
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
+++-================================-====================================-============-===============================================================================
ii juju 1.22.0-0ubuntu1~14.04.2~juju1 all
ii juju-core 1.22.0-0ubuntu1~14.04.2~juju1 amd64
ii juju-deployer 0.4.3-0ubuntu1~ubuntu14.04.1~ppa1 all
ii python-jujuclient 0.50.1-2 amd64
un python2.7-jujuclient <none> <none>
Thanks
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1436096
Title:
interrupting juju-deployer prevents juju destroy-environment from
tearing it down cleanly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1436096/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
