Ask Your Question
0

Instance unable to reach cloudformation publicURL

asked 2016-02-15 07:52:37 -0500

splash gravatar image

updated 2016-02-16 08:53:34 -0500

While testing AWS::CloudFormation::WaitConditionHandle and AWS::CloudFormation::WaitCondition, the VM is spawned and the script from within the VM tries to connect to:

curl -X PUT -H 'Content-Type:application/json' 'http://10.126.3.102:8000/v1/waitcondition/arn%3Aopenstack%3Aheat%3A%3A166ff133618a49c28f103153eff93d88%3Astacks%2Fstack-test%2F7e612dc0-1e01-49a7-bffb-ef677c5414df%2Fresources%2Ftest-vm_progress_handle?Timestamp=2016-02-15T12%3A48%3A59Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=5c41911cc1914654a68bb4f357d72e76&SignatureVersion=2&Signature=pqQV8hTPdqxGhdnAtsnkA3CVZ3mtweU7yg71XrAHSqo%3D' --data-binary '{"Status" : "SUCCESS","Reason" : "Configuration Finished","UniqueId" : "setup-status-4","Data" : "Finished installing the apache server}'

However the VM instance is unable to reach 10.126.3.103 (the official cloudformation publicURL)

I checked and keystone is reporting the cloudformation publicURL correctly. Where could be the problem that the VM is not able to reach the cloudformation publicURL?

I'm not the admin of the environment.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-02-22 17:36:08 -0500

zaneb gravatar image

You may need to set up your Neutron networks to allow your Nova server to access the API servers. Obviously 10.0.0.0/8 networks are not globally routable, so everything depends on the configuration that your operator is using. You'll probably need to check with them.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-02-15 07:52:37 -0500

Seen: 48 times

Last updated: Feb 22 '16