Bug 1326185

Summary: Wait Condition Handle Fails to send signal to the heat orchestration
Product: Red Hat OpenStack Reporter: Jaison Raju <jraju>
Component: openstack-heatAssignee: Zane Bitter <zbitter>
Status: CLOSED NOTABUG QA Contact: Amit Ugol <augol>
Severity: medium Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: jraju, mburns, rhel-osp-director-maint, sbaker, shardy, therve, yeylon
Target Milestone: ---Keywords: Unconfirmed, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-12 12:36:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jaison Raju 2016-04-12 06:00:05 UTC 
Description of problem:
Wait Condition Handle Fails to send signal to the heat orchestration, engine and stack fails after timeout period expires.

# curl -i -X POST -H 'X-Auth-Token: xxxxxxxxxxxxxxxxxxxxxxx' -H 'Content-Type: application/json' -H 'Accept: application/json' http://controller.example.com:8004/v1/xxxxxxxxxxxxxxxxxxxxxx/stacks/wait_condition_fail/xxxxxxxxxxxxxxxxxxxxxxxx/resources/wait_handle_srv/signal --data-binary '{"status": "SUCCESS"}'
HTTP/1.1 401 Unauthorized
Www-Authenticate: Keystone uri='https://openstack.example.com:5000/v2.0'
Content-Type: text/plain
X-Openstack-Request-Id: req-692f974c-f248-4e1c-9806-42655240ba48
Content-Length: 23
Date: Tue, 05 Apr 2016 04:52:48 GMT

Version-Release number of selected component (if applicable):


How reproducible:
Always at customer end .

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
This behaviour may be a bug .
https://review.openstack.org/#/c/232124/
Comment 3 Thomas Hervé 2016-04-12 08:11:12 UTC 
Authentication fails with "Non-default domain is not supported". It means we're talking to Keystone v2.0 API while we should be talking to the v3 one.

I notice the configuration mentions auth_version=v2.0 in the keystone_authtoken section for Heat. I would remove that.
Comment 4 Jaison Raju 2016-04-12 12:36:01 UTC 
Thanks Thomas ,

As noticed , customer confirmed that the issue was an incorrect token version .
I will close this bug .