RE: Cannot bootstrap due to “”precise“ images in RegionOne with arches [amd64 i386]” error

[Steven Hicks]

The JSON files were last generated with:
juju image-metadata -i 168e01e5-c9c5-4e2e-868b-f29138ebbeda -a amd64 -r RegionOne -s precise -e http://10.10.13.180:5000/v2.0

The –n is to select the metadata files to be generated for a specific environment.

-Steven Hicks
  Solutions Engineer
  Avnet Services (formerly Seamless Technologies Inc.)
  Office: +1 773 639 4219
  Email: shicks at seamlessti.com

From: Andreas Hasenack [mailto:andreas at canonical.com]
Sent: Tuesday, August 13, 2013 5:15 PM
To: Steven Hicks
Cc: juju
Subject: Re: Cannot bootstrap due to “”precise“ images in RegionOne with arches [amd64 i386]” error

On Tue, Aug 13, 2013 at 6:21 PM, Steven Hicks <shicks at seamlessti.com<mailto:shicks at seamlessti.com>> wrote:
I saw the same thing and thought of that as well.

It looks like this might be a bug with how the URL is formed within Juju.

This is copy and paste from environment.yml.

    # Usually set via the env variable OS_REGION_NAME, but can be specified here
    region: RegionOne
    public-bucket-url: http://10.10.13.180:8080/v1/AUTH_3[...]4e<http://10.10.13.180:8080/v1/AUTH_3%5B...%5D4e>
#https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60
#    default-series: precise

The JSON files appear to be correct.

I didn't say this before, but don't use the "-n" option when generating the json files. Stick with plain index.json and imagemetadata.json. I don't know in which case -n is used to be honest.


There was a request for:
(This stuck out to me as well)
/index.sjson

It's ok, juju will try some version of the files first (sjon stands for signed json I believe).

Ok, back to basics, I have no other ideas. See if you can get this to work:
swift post somecontainer
swift upload somecontainer/data/files somefile.txt
swift post -r ".r:*" somecontainer
wget <public-bucket-url>/somecontainer/data/files/somefile.txt

See if that wget gives you back the file you uploaded. This has to work. If not, then I suspect the public-bucket-url you are using is not the publicURL from the object-store service in the output of the "keystone catalog" command, or there is some misconfiguration in the swift service of your cloud.





CONFIDENTIALITY NOTICE: This email communication is intended only for the personal and confidential use of the recipient(s) designated above and may contain information which is subject to Federal and/or State privacy laws. In the event that you are not the intended recipient or the agent of the intended recipient, you are hereby notified that any review, disclosure, or use of the information contained herein is strictly prohibited. Do not copy or use the information contained within this communication, or allow it to be read, copied or utilized in any manner by any other person(s). If you have received this communication in error, please notify the sender immediately, either by response e-mail or by phone, and permanently delete the original e-mail, any attachment(s), and copies.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130813/fb3f9e2a/attachment.html>