As specified in my original post, the issue persists whether "Enable SSL 
certificate verification" is checked or unchecked (it's currently 
unchecked).

On Monday, August 22, 2016 at 1:59:24 PM UTC-5, Marc O'Brien wrote:
>
> Hi Patrick,
>
> Can you provide a screenshot of your Openstack cloud credentials 
> configuration? You can mask your credentials.  We are looking for the 
> current status of the checkbox for "Enable SSL certificate verification for 
> Keystone endpoints."
>
> Many thanks,
> Wm. Marc O'Brien
> Scalr Technical Support
>
>
> On Wednesday, August 17, 2016 at 3:11:10 PM UTC-6, Patrick Vinas wrote:
>>
>> Thanks, Igor and Marc. Debug log is attached, with domain obfuscated.
>>
>> On Monday, August 15, 2016 at 4:53:40 PM UTC-5, DicsyDel wrote:
>>>
>>> We will need /var/log/scalarizr_debug.log file from the failed VM. You 
>>> can send it to igor [at] scalr.com 
>>>
>>> Thanks, 
>>> Igor 
>>>
>>> On 15 August 2016 at 08:59, Marc O'Brien <[email protected]> wrote: 
>>> > Hi Patrick, 
>>> > 
>>> > Could you attach the full error log here?  There was previously a 
>>> similar 
>>> > issue related to Python version that has since been resolved in 
>>> Enterprise 
>>> > Scalr 6.0.1.  Error log should hopefully provide a bit more context 
>>> for us. 
>>> > 
>>> > Many thanks, 
>>> > Wm. Marc O'Brien 
>>> > Scalr Technical Support 
>>> > 
>>> > 
>>> > On Saturday, August 13, 2016 at 11:12:48 AM UTC-6, Patrick Vinas 
>>> wrote: 
>>> >> 
>>> >> I've got both Openstack and AWS environments in an account in scalr 
>>> >> (5.11.22 Community, scalarizr agent v. 4.8.2 (stable) and 4.9.9 
>>> (latest) ) 
>>> >> 
>>> >> The only issue I'm having with launching a farm is with roles that 
>>> are 
>>> >> launching in Openstack with a storage volume attached. All AWS roles, 
>>> and 
>>> >> all Openstack roles without cinder storage volumes, launch 
>>> successfully. 
>>> >> 
>>> >> The error in the UI Servers->Initialization progress is "SSL 
>>> exception 
>>> >> connecting to https://<controller>:5000/v3/auth/tokens: [SSL: 
>>> >> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)" 
>>> >> 
>>> >> First tried adding my internal CA cert to the system trust for the 
>>> image, 
>>> >> to no effect. I can ssh into the failed instances, and I've verified 
>>> that I 
>>> >> can connect to the keystone service at that port (curl 
>>> >> https://<controller>:5000/v3 returns as expected). There aren't any 
>>> errors 
>>> >> in the keystone or cinder logs, and the Scalr internal messaging and 
>>> system 
>>> >> logs look fine. If I turn off SSL verification of endpoints in the 
>>> >> environment settings, this error persists. 
>>> >> 
>>> >> Does anyone have any ideas for further troubleshooting? 
>>> > 
>>> > -- 
>>> > 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/d/optout. 
>>>
>>

-- 
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/d/optout.

Reply via email to