-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to sort through the ssl stuff, and I noticed the recent changes stopped calling "openstack.NewPublicClient".
This means that PublicStorage is returning an authenticating client (s.client). Which I *think* means that if you had been setting public-bucket to point to an account which isn't yours, we'll be making requests for that data with your creds (rather than no creds). Even with the changes to DataStore, you still go via the StorageReader. I just tested it with Canonistack and public-bucket-url set (and FORCE-VERSION=1.13.3). With those bits, I see it try to connect to my private bucket, and then fall back to what seems to be public-bucket-url. Both of which fail. Then it tries the same public URL again and it succeeds. So I'm pretty sure that public-bucket-url is just broken now, and bootstrap is only succeeding because it falls back to the keystone entry which it then accesses as a Raw URL rather than a Swift bucket. Also, with all of the URL probing it now does, bootstrap is *much* slower. It took about 1m40s for bootstrap to complete. See http://pad.lv/1219582 where I added some debug logs. John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (Cygwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlI1kQEACgkQJdeBCYSNAAPtKQCguM0eoMSPgbxmaehU4DLJ09G6 CpgAmgKBrpUSIl5UZMEz5Bj8HuE7Miz1 =Tyh6 -----END PGP SIGNATURE----- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
