| 2014-08-21 19:08:52 |
Aaron Bentley |
bug |
|
|
added bug |
| 2014-08-21 19:09:21 |
Aaron Bentley |
description |
When there's no environment and I run juju destroy-environment charm-testing-hp --force --debug, it tries to delete an unknown container and fails:
2014-08-21 17:13:04 ERROR juju.cmd supercommand.go:323 failed to delete container:
caused by: Unauthorised URL https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/
caused by: request (https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/) returned unexpected status: 403; error info: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html>
If I manually specify a control bucket in environments.yaml , or if there's a .jenv, this does not happen.
It always tries to delete the same container. I wonder whether it's generating a control-bucket with an un-initialized psuedo-random number generator.
Note also that there's no debug message about deleting a container, just instances.
We see this frequently in CI, but it seems benign, so far.
$ juju destroy-environment charm-testing-hp --force --debug
2014-08-21 17:12:51 INFO juju.cmd supercommand.go:37 running juju [1.20.5-trusty-amd64 gc]
2014-08-21 17:12:51 INFO juju.provider.openstack provider.go:204 opening environment "charm-testing-hp"
WARNING! this command will destroy the "charm-testing-hp" environment (type: openstack)
This includes all machines, services, data and other resources.
Continue [y/N]? y
2014-08-21 17:12:54 INFO juju.provider.common destroy.go:15 destroying environment "charm-testing-hp"
2014-08-21 17:12:55 DEBUG juju.provider.openstack provider.go:1040 terminating instances []
2014-08-21 17:13:04 ERROR juju.cmd supercommand.go:323 failed to delete container:
caused by: Unauthorised URL https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/
caused by: request (https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/) returned unexpected status: 403; error info: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html> |
When there's no environment and I run juju destroy-environment charm-testing-hp --force --debug, it tries to delete an unknown container and fails:
2014-08-21 17:13:04 ERROR juju.cmd supercommand.go:323 failed to delete container:
caused by: Unauthorised URL https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/
caused by: request (https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/) returned unexpected status: 403; error info: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html>
If I manually specify a control bucket in environments.yaml, or if there's a .jenv, this does not happen.
It always tries to delete the same container. I wonder whether it's generating a control-bucket with an un-initialized psuedo-random number generator.
Note also that there's no debug message about deleting a container, just instances.
We see this frequently in CI, but it seems benign, so far.
$ juju destroy-environment charm-testing-hp --force --debug
2014-08-21 17:12:51 INFO juju.cmd supercommand.go:37 running juju [1.20.5-trusty-amd64 gc]
2014-08-21 17:12:51 INFO juju.provider.openstack provider.go:204 opening environment "charm-testing-hp"
WARNING! this command will destroy the "charm-testing-hp" environment (type: openstack)
This includes all machines, services, data and other resources.
Continue [y/N]? y
2014-08-21 17:12:54 INFO juju.provider.common destroy.go:15 destroying environment "charm-testing-hp"
2014-08-21 17:12:55 DEBUG juju.provider.openstack provider.go:1040 terminating instances []
2014-08-21 17:13:04 ERROR juju.cmd supercommand.go:323 failed to delete container:
caused by: Unauthorised URL https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/
caused by: request (https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/) returned unexpected status: 403; error info: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html> |
|
| 2014-08-21 19:10:31 |
Curtis Hovey |
tags |
ci destroy-environment |
ci destroy-environment openstack-provider |
|
| 2014-08-21 19:11:22 |
Curtis Hovey |
description |
When there's no environment and I run juju destroy-environment charm-testing-hp --force --debug, it tries to delete an unknown container and fails:
2014-08-21 17:13:04 ERROR juju.cmd supercommand.go:323 failed to delete container:
caused by: Unauthorised URL https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/
caused by: request (https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/) returned unexpected status: 403; error info: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html>
If I manually specify a control bucket in environments.yaml, or if there's a .jenv, this does not happen.
It always tries to delete the same container. I wonder whether it's generating a control-bucket with an un-initialized psuedo-random number generator.
Note also that there's no debug message about deleting a container, just instances.
We see this frequently in CI, but it seems benign, so far.
$ juju destroy-environment charm-testing-hp --force --debug
2014-08-21 17:12:51 INFO juju.cmd supercommand.go:37 running juju [1.20.5-trusty-amd64 gc]
2014-08-21 17:12:51 INFO juju.provider.openstack provider.go:204 opening environment "charm-testing-hp"
WARNING! this command will destroy the "charm-testing-hp" environment (type: openstack)
This includes all machines, services, data and other resources.
Continue [y/N]? y
2014-08-21 17:12:54 INFO juju.provider.common destroy.go:15 destroying environment "charm-testing-hp"
2014-08-21 17:12:55 DEBUG juju.provider.openstack provider.go:1040 terminating instances []
2014-08-21 17:13:04 ERROR juju.cmd supercommand.go:323 failed to delete container:
caused by: Unauthorised URL https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/
caused by: request (https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/) returned unexpected status: 403; error info: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html> |
When there's no environment and I run juju destroy-environment charm-testing-hp --force --debug, it tries to delete an unknown container and fails:
2014-08-21 17:13:04 ERROR juju.cmd supercommand.go:323 failed to delete container:
caused by: Unauthorised URL https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/
caused by: request (https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/) returned unexpected status: 403; error info: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html>
If I manually specify a control bucket in environments.yaml, or if there's a .jenv, this does not happen.
It always tries to delete the same container. I wonder whether it's generating a control-bucket with an un-initialized psuedo-random number generator.
Note also that there's no debug message about deleting a container, just instances.
We see this frequently in CI, but it seems benign, so far.
$ juju destroy-environment charm-testing-hp --force --debug
2014-08-21 17:12:51 INFO juju.cmd supercommand.go:37 running juju [1.20.5-trusty-amd64 gc]
2014-08-21 17:12:51 INFO juju.provider.openstack provider.go:204 opening environment "charm-testing-hp"
WARNING! this command will destroy the "charm-testing-hp" environment (type: openstack)
This includes all machines, services, data and other resources.
Continue [y/N]? y
2014-08-21 17:12:54 INFO juju.provider.common destroy.go:15 destroying environment "charm-testing-hp"
2014-08-21 17:12:55 DEBUG juju.provider.openstack provider.go:1040 terminating instances []
2014-08-21 17:13:04 ERROR juju.cmd supercommand.go:323 failed to delete container:
caused by: Unauthorised URL https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/
caused by: request (https://region-a.geo-1.objects.hpcloudsvc.com/v1/17031369947864/) returned unexpected status: 403; error info: <html><h1>Forbidden</h1><p>Access was denied to this resource.</p></html>
This happens in HP Cloud US East. It does not happen in US West or in canonistack. |
|
| 2014-08-21 19:11:28 |
Curtis Hovey |
tags |
ci destroy-environment openstack-provider |
ci destroy-environment hp-cloud openstack-provider |
|
| 2016-04-12 20:33:18 |
Curtis Hovey |
tags |
ci destroy-environment hp-cloud openstack-provider |
ci destroy-environment openstack-provider |
|
| 2016-10-17 13:36:54 |
Anastasia |
juju-core: status |
Triaged |
Won't Fix |
|
