I'm currently evaluating Scalr, and I have devstack/Openstack installed. I 
get the "Whoops! Something went wrong, and we have been notified. Try 
reloading the page if things don't work" error when I try to "Create role 
from non-Scalr server". Is there a patch or update on how to get this 
working?

Thanks.

On Thursday, May 2, 2013 5:16:35 PM UTC-7, Sebastian Stadil wrote:
>
> We found the issue and have fixed it upstream, but it might be some time 
> before we make another release. 
>
> If you are under a deadline, please consider supporting the project by 
> contacting sales. 
>
> On Thursday, May 2, 2013, Justice London wrote:
>
>> Any update to be had here? Kind of a show-stopper.
>>
>> On Tuesday, April 30, 2013 8:41:18 AM UTC-7, Justice London wrote:
>>>
>>> Sure. Perhaps there is something we need to change from older versions 
>>> (perhaps cronjobs?), but specifically the message queue tasks don't seem to 
>>> work with openstack. When the szrmessaging task runs:
>>>
>>> /usr/local/scalr/current/cron/**cron.php --SzrMessaging
>>>
>>> We have the following errors:
>>>
>>> 2013-04-27 19:55:19,345 - ERROR [tran517c2cd9bde87:Logger@628] - 'Cannot 
>>> handle message \'Hello\' (message_id: 
>>> 883b1ebe-dfe5-4561-aa55-**573b1dedaf82) 
>>> from server \'172.20.0.143\' (server_id: 
>>> a7e47af1-85c0-4b76-8663-**9d71e3aa1a7b). 
>>> Request to Openstack failed (Code: 0): <!DOCTYPE HTML PUBLIC \"-//IETF//DTD 
>>> HTML 2.0//EN\">\n<html><head>\n<**title>404 Not 
>>> Found</title>\n</head><body>\**n<h1>Not Found</h1>\n<p>The requested 
>>> URL /v2.0/tokens was not found on this 
>>> server.</p>\n<hr>\n<address>**Apache/2.2.22 
>>> (Ubuntu) Server at localhost Port 80</address>\n</body></html>(/**
>>> usr/local/scalr/Scalr-scalr-**fb66258/app/src/Scalr/Service/**
>>> Cloud/Openstack/Connection.**php:111
>>>
>>> We tracked it down, and all of the variables are attempting to be pulled 
>>> from server_properties, while they appear to have been moved to a hashed 
>>> table called client_environment_properties. Perhaps there are changes 
>>> needed to scripts used in 4.1?
>>>
>>>
>>> On Monday, April 29, 2013 5:08:53 PM UTC-7, DicsyDel wrote:
>>>>
>>>> Justice,
>>>>
>>>> 4.1 have working support for Openstack. Can you please let me know, 
>>>> what exactly doesn't work on your setup?
>>>>
>>>> Thanks,
>>>> Igor
>>>>
>>>> On 29 April 2013 15:04, Justice London <[email protected]> wrote:
>>>>
>>>>> Hello, I see that you release 4.1 on github. Is this meant to be a 
>>>>> working implementation for openstack? It appears that you are using 
>>>>> variables like API_URL which don't actually exist (I believe it should be 
>>>>> KEYSTONE_URL) and beyond that other variable issues. 
>>>>>
>>>>> What's happening is that there is no API url or correct login 
>>>>> information passed to the SZR messaging scripts, which in turn always 
>>>>> produce a 'failure' status on trying to import a role.
>>>>>
>>>>> Justice
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "scalr-discuss" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to scalr-discus...@googlegroups.**com.
>>>>> For more options, visit 
>>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>>> .
>>>>>  
>>>>>  
>>>>>
>>>>
>>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "scalr-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>
> -- 
>
>
> Follow us: Twitter <https://twitter.com/#!/scalr> - 
> Facebook<https://www.facebook.com/Scalr>
>  - Blog <http://blog.scalr.net/>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to