Description of problem: A recent change making nova-metadata-api work with wsgi [1][2] moved the vendordata plugin parameters to the nova::metadata manifest. While this is conceptually correct as nova-metadata is the one that should be using this parameters. In practice, this doesn't work once you deploy the nova-metadata-api separate from nova-compute. This is because this parameters are used in the compute drivers (in the ironic driver, for instance). [1] https://review.openstack.org/#/c/582621/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1579866 Version-Release number of selected component (if applicable): OSP14 How reproducible: always Steps to Reproduce: 1. master/rocky deploy of a tls-everywhere env 2. overcloud nodes fail to get metadata vendordata information from novajoin Actual results: overcloud nodes fail to get metadata vendordata information from novajoin Expected results: overcloud nodes get metadata vendordata information from novajoin and overcloud installation is successful Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045