Missing X-Auth-User header when sending request to Head

[Manuel Buil]

When creating the vnf after registering the vnfd, we can see an error in tacker logs:

 HTTPBadRequest: ERROR: <ErrorResponse><Error><Message>The request signature does not conform to AWS standards</Message><Code>IncompleteSignature</Code><Type>Sender</Type></Error></ErrorResponse>

looking at HEAT code it looks like it reports this error if there's no X-Auth-User header. i.e. if there's no Keystone auth info it assumes you're trying to auth with an AWS signature, and if that isn't there either then it fails with an error:

https://git.openstack.org/cgit/openstack/heat/tree/heat/api/aws/ec2token.py#n165

[Cong Phuoc Hoang (hoangphuoc)]

Can you give me tacker and heat version, and VNF descriptor too? I will check it asap. Thanks.

[Manuel Buil (mbuil)]

I am using heat from July 2018. This is the SHA: 9e463f4af77513980b1fd215d5d2ad3bf7b979f9
I am using Tacker from July 2018. This is the SHA: 7d0c22524ac8352a50af2e017eed4b5be28d4c31

This is the vnfd we use: https://github.com/opnfv/sfc/blob/master/sfc/tests/functest/vnfd-templates/test-one-chain-vnfd1.yaml

[Cong Phuoc Hoang (hoangphuoc)]

I am sorry because I can not produce that error in devstack.

In Tacker code, we added authentication attributes to heat client (https://github.com/openstack/tacker/blob/master/tacker/vnfm/infra_drivers/openstack/openstack.py#L101), so we need to investigate that issue.

[Rabi Mishra (rabi)]

Sorry, I don't see any heat logs to tell what's the issue where. I'm not sure why the signature would be missing for ec2 auth at the first place.