Ask Your Question
0

New instance cannot communicate with metadata proxy on VMware NSX-T 2.4.1

asked 2019-07-31 10:17:43 -0500

Hello fellow OpenStackers -

We are using Openstack Stein, VMWare Vcenter (and esxi), as well as NSX-T for our deployment. We are using cloud-init, CentOS7, and also the VMWare NSX plugin. Our metadata proxies are being handled by NSX-T. Networking is setup and configured; however, when instances are deployed, during the boot process (when cloud-init is initializing) the machine has a problem with the metadata service.

During boot, after GRUB appears cloud-init is attempting some kind of transaction with the metadata proxy, fails, and loops for 2 minutes. Next, it attempts another action, fails for two minutes and then moves on to complete the booting of the operating system.

Message during boot states:
Finally, stating:
Next error states:
Lastly to add:

I can use curl to retrieve data from the controller:8775 where nova resides successfully. However, if I attempt to curl the metadata proxy on the link local address from within the same segment I get a 502 bad gateway message.

Please let me know if you have any insight or if there is more information I can provide.

Thank you!

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-08-08 08:24:02 -0500

Hello Everyone,

We were able to resolve this issue. When specifying the Nova endpoint in the NSX-T Metadata proxy, we were using HTTP. Seeing as this was a lab environment, we didn't think too much of it. Once we enables HTTPS, the issue was resolved! Just wanted to post an update to this in case anyone else may come across this issue!

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: 2019-07-31 10:17:43 -0500

Seen: 36 times

Last updated: Aug 08