On Fri, Mar 28, 2014 at 1:03 PM, Sebastian <sebas5...@gmail.com> wrote:
> maybe I'm with the same problem, because i'm not setting those. > > What are that urls? theres a real example for better understanding? > The URL must point to a location that contains the tools tarballs and tools metadata. For OpenStack, this would typically be a swift container. In Hui's case, it's in the original email: http://10.55.32.149:8080/v1/AUTH_02db550787604a85a3df364b5cdf9ac4/2ae43fe4-eb72-4402-9c5c-4a42749cfee3/ tools Sebas. > > > > 2014-03-28 1:57 GMT-03:00 Andrew Wilkins <andrew.wilk...@canonical.com>: > > On Fri, Mar 28, 2014 at 12:49 PM, Hui Xiang <hui.xi...@canonical.com>wrote: >> >>> Hi Andrew, >>> >>> I didn't set tools-url and tools-metadata-url, looks like you find the >>> root cause, what it should be like, I failed to find info of it except : >>> # tools-url: https://you-tools-url >>> >>> I am not sure what tools url is, juju tool? >>> >>> Thanks for your great help : ) >>> >> >> The other place that Juju consults is the "juju-tools" keystone service >> endpoint. Did you define that? >> If not, I'm probably not going to be of much more help - I don't know the >> OpenStack provider all that well. >> >> >>> Sebas, >>> >>> Try to redeploy OpenStack with enable swift, that's what I did to move >>> on fast. >>> >>> Regards. >>> Hui >>> >>> >>> >>> On Fri, Mar 28, 2014 at 12:42 PM, Sebastian <sebas5...@gmail.com> wrote: >>> >>>> yeah, maybe you are right, well at least Im not the only one suffering >>>> from swift and juju relationship, hehe. >>>> >>>> Seems to me juju is getting a wrong url for their tools, as Andrew >>>> noticed. >>>> >>>> Abs, >>>> Sebas. >>>> >>>> >>>> >>>> 2014-03-28 1:39 GMT-03:00 Andrew Wilkins <andrew.wilk...@canonical.com> >>>> : >>>> >>>>> On Fri, Mar 28, 2014 at 12:24 PM, Hui Xiang >>>>> <hui.xi...@canonical.com>wrote: >>>>> >>>>>> Hi juju community, >>>>>> >>>>>> I hit en error when using juju plus OpenStack provider, below is >>>>>> the environment and what I found, please give me a help to let me move >>>>>> on. >>>>>> >>>>>> OpenStackļ¼ Havana(deployed with devstack) >>>>>> juju : 1.16.6-precise-amd64 >>>>>> >>>>>> swift works well: >>>>>> ubuntu@havana:~$ swift list >>>>>> dfc9e845-2d67-4be4-892a-648a7a13e881 >>>>>> >>>>>> But when running "ubuntu@havana:~/.juju$ sudo juju bootstrap >>>>>> --debug" , it goes wrong with log: >>>>>> >>>>>> 2014-03-28 04:09:16 DEBUG juju.environs.simplestreams >>>>>> simplestreams.go:458 fetchData failed for >>>>>> "*http://10.55.32.149:8080/v1/AUTH_02db550787604a85a3df364b5cdf9ac4/2ae43fe4-eb72-4402-9c5c-4a42749cfee3/streams/v1/index.json >>>>>> <http://10.55.32.149:8080/v1/AUTH_02db550787604a85a3df364b5cdf9ac4/2ae43fe4-eb72-4402-9c5c-4a42749cfee3/streams/v1/index.json>*": >>>>>> failed to GET object streams/v1/index.json from container >>>>>> 2ae43fe4-eb72-4402-9c5c-4a42749cfee3 >>>>>> ERROR juju supercommand.go:282 cannot start bootstrap instance: >>>>>> index file has no data for cloud {RegionOne >>>>>> http://10.55.32.149:35357/v2.0/} not found >>>>>> >>>>>> So I check the swift container, juju seems create the container >>>>>> with my specified control_bucket, adding a new container: >>>>>> ubuntu@havana:~$ swift list >>>>>> *2ae43fe4-eb72-4402-9c5c-4a42749cfee3* >>>>>> dfc9e845-2d67-4be4-892a-648a7a13e881 >>>>>> >>>>>> >>>>>> Then I try to check the link automatically >>>>>> ubuntu@havana:~/.juju$ curl >>>>>> http://10.55.32.149:8080/v1/AUTH_02db550787604a85a3df364b5cdf9ac4/2ae43fe4-eb72-4402-9c5c-4a42749cfee3/streams/v1/index.json >>>>>> <html><h1>Not Found</h1><p>*The resource could not be found.* >>>>>> </p></html> >>>>>> But it will success by add the "tools" in front of >>>>>> /streams/v1/index.json >>>>>> ubuntu@havana:~/.juju$ curl >>>>>> http://10.55.32.149:8080/v1/AUTH_02db550787604a85a3df364b5cdf9ac4/2ae43fe4-eb72-4402-9c5c-4a42749cfee3/ >>>>>> *tools*/streams/v1/index.json >>>>>> { >>>>>> "index": { >>>>>> "com.ubuntu.juju:released:tools": { >>>>>> "updated": "Fri, 28 Mar 2014 04:09:15 +0000", >>>>>> "format": "products:1.0", >>>>>> "datatype": "content-download", >>>>>> "path": "streams/v1/com.ubuntu.juju:released:tools.json", >>>>>> "products": [ >>>>>> "com.ubuntu.juju:12.04:amd64", >>>>>> "com.ubuntu.juju:12.04:armhf", >>>>>> "com.ubuntu.juju:12.04:i386", >>>>>> "com.ubuntu.juju:12.10:amd64", >>>>>> "com.ubuntu.juju:12.10:i386", >>>>>> "com.ubuntu.juju:13.10:amd64", >>>>>> "com.ubuntu.juju:13.10:armhf", >>>>>> "com.ubuntu.juju:13.10:i386", >>>>>> "com.ubuntu.juju:14.04:amd64", >>>>>> "com.ubuntu.juju:14.04:armhf", >>>>>> "com.ubuntu.juju:14.04:i386" >>>>>> ] >>>>>> } >>>>>> }, >>>>>> "updated": "Fri, 28 Mar 2014 04:09:15 +0000", >>>>>> "format": "index:1.0" >>>>>> >>>>>> >>>>>> How should I fix this, as juju changed the link but when bootstrap >>>>>> did not call with the same link, anyone can help me is really >>>>>> appreciated. >>>>>> >>>>>> Regards. >>>>>> >>>>>> Hui. >>>>>> >>>>> >>>>> Have you set tools-url or tools-metadata-url in your environments.yaml? >>>>> Looks a bit like they might be set (incorrectly). >>>>> >>>>> -- >>>>> Juju mailing list >>>>> Juju@lists.ubuntu.com >>>>> Modify settings or unsubscribe at: >>>>> https://lists.ubuntu.com/mailman/listinfo/juju >>>>> >>>>> >>>> >>> >> >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
