It sound like our change to set readable on the control-bucket is failing
on Canonistack.
Maybe this is an incompatibility with Icehouse? (Did canonistack get
upgraded?)
John
=:->
On Thu, Apr 24, 2014 at 6:44 PM, Curtis Hovey <email address hidden> wrote:
> Public bug reported:
>
> Canonistack swift access has spontaneously combusted. First juju-qa lost
> access. Now orangesquad has lost access. Juju cannot get permission to
> use swift. juju-qa and orangesquad can not use swift-client after juju's
> configs were changed to match the setup recommended by
>
> juju init
>
> Both accounts lost access when control-bucket and admin-secret were
> removed from the juju configs. In both cases, there were no jenv files
> left behind nor where there any running environments when the change
> was made. An example config looks like this:
>
> test-cloud-canonistack:
> # juju --show-log bootstrap -e test-release-canonistack
> type: openstack
> test-mode: true
> use-floating-ip: false
> auth-url: https://keystone.canonistack.canonical.com:443/v2.0/
> authorized-keys: |
> ssh-rsa <SECRET>
> username: juju-qa
> password: <SECRET>
> tenant-name: <SECRET>
> region: lcy02
> default-series: precise
> tools-metadata-url:
> https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60/juju-dist/tools
>
> The output of bootstrap showed this:
>
> juju --show-log bootstrap -e test-cloud-canonistack --constraints
> mem=2G
> 2014-04-23 14:45:35 INFO juju.cmd supercommand.go:297 running
> juju-1.18.0-precise-amd64 [gc]
> 2014-04-23 14:45:35 INFO juju.provider.openstack provider.go:202
> opening environment "test-cloud-canonistack"
> 2014-04-23 14:45:36 WARNING juju.environs open.go:289 failed to write
> bootstrap-verify file: cannot make Swift control container: failed to
> create container: 17338a9c21264d6b8e5b34b9e443c049
> caused by: Resource at
> https://swift.canonistack.canonical.com/v1/AUTH_bfbb283705034a7c8eeefb918b2e8df8/17338a9c21264d6b8e5b34b9e443c049not found
> caused by: request (
> https://swift.canonistack.canonical.com/v1/AUTH_bfbb283705034a7c8eeefb918b2e8df8/17338a9c21264d6b8e5b34b9e443c049)
> returned unexpected status: 404; error info: 404 Not Found
>
> The resource could not be found.
>
> After juju tried to create a container, swift shows this (after the lib
> was hacked to survive the report a a unicode error):
>
> swift list
> Account GET failed:
>
> https://swift.canonistack.canonical.com/v1/AUTH_bbda63d64a9e4dfda1072e7743704f1e
> ?
> format=json 403 Forbidden
> JMN+THII-IM b
>
> CI is not testing canonistack since juju and its accounts are crippled.
>
> ** Affects: juju-core
> Importance: High
> Status: Triaged
>
>
> ** Tags: openstack-provider
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1312217
>
> Title:
> open-stack provider breaks swift with standard config
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1312217/+subscriptions
>
It sound like our change to set readable on the control-bucket is failing
on Canonistack.
Maybe this is an incompatibility with Icehouse? (Did canonistack get
upgraded?)
John
=:->
On Thu, Apr 24, 2014 at 6:44 PM, Curtis Hovey <email address hidden> wrote:
> Public bug reported: canonistack: canonistack /keystone. canonistack. canonical. com:443/ v2.0/ /swift. canonistack. canonical. com/v1/ AUTH_526ad877f3 e3464589dc1145d feaac60/ juju-dist/ tools canonistack --constraints 18.0-precise- amd64 [gc] openstack provider.go:202 canonistack" b8e5b34b9e443c0 49 /swift. canonistack. canonical. com/v1/ AUTH_bfbb283705 034a7c8eeefb918 b2e8df8/ 17338a9c21264d6 b8e5b34b9e443c0 49not found /swift. canonistack. canonical. com/v1/ AUTH_bfbb283705 034a7c8eeefb918 b2e8df8/ 17338a9c21264d6 b8e5b34b9e443c0 49) /swift. canonistack. canonical. com/v1/ AUTH_bbda63d64a 9e4dfda1072e774 3704f1e /bugs.launchpad .net/bugs/ 1312217 /bugs.launchpad .net/juju- core/+bug/ 1312217/ +subscriptions
>
> Canonistack swift access has spontaneously combusted. First juju-qa lost
> access. Now orangesquad has lost access. Juju cannot get permission to
> use swift. juju-qa and orangesquad can not use swift-client after juju's
> configs were changed to match the setup recommended by
>
> juju init
>
> Both accounts lost access when control-bucket and admin-secret were
> removed from the juju configs. In both cases, there were no jenv files
> left behind nor where there any running environments when the change
> was made. An example config looks like this:
>
> test-cloud-
> # juju --show-log bootstrap -e test-release-
> type: openstack
> test-mode: true
> use-floating-ip: false
> auth-url: https:/
> authorized-keys: |
> ssh-rsa <SECRET>
> username: juju-qa
> password: <SECRET>
> tenant-name: <SECRET>
> region: lcy02
> default-series: precise
> tools-metadata-url:
> https:/
>
> The output of bootstrap showed this:
>
> juju --show-log bootstrap -e test-cloud-
> mem=2G
> 2014-04-23 14:45:35 INFO juju.cmd supercommand.go:297 running
> juju-1.
> 2014-04-23 14:45:35 INFO juju.provider.
> opening environment "test-cloud-
> 2014-04-23 14:45:36 WARNING juju.environs open.go:289 failed to write
> bootstrap-verify file: cannot make Swift control container: failed to
> create container: 17338a9c21264d6
> caused by: Resource at
> https:/
> caused by: request (
> https:/
> returned unexpected status: 404; error info: 404 Not Found
>
> The resource could not be found.
>
> After juju tried to create a container, swift shows this (after the lib
> was hacked to survive the report a a unicode error):
>
> swift list
> Account GET failed:
>
> https:/
> ?
> format=json 403 Forbidden
> JMN+THII-IM b
>
> CI is not testing canonistack since juju and its accounts are crippled.
>
> ** Affects: juju-core
> Importance: High
> Status: Triaged
>
>
> ** Tags: openstack-provider
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https:/
>
> Title:
> open-stack provider breaks swift with standard config
>
> To manage notifications about this bug go to:
> https:/
>