Vendordata plugins are not functional

Bug #1799352 reported by Juan Antonio Osorio Robles
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-nova
Fix Released
Undecided
Martin Schuppert

Bug Description

A recent change making nova-metadata-api work with wsgi [1] 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/

description: updated
description: updated
Changed in puppet-nova:
assignee: nobody → Martin Schuppert (mschuppert)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to puppet-nova (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/612964

Revision history for this message
Martin Schuppert (mschuppert) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to puppet-nova (master)

Reviewed: https://review.openstack.org/612964
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=6686406bce9e7fc9623dea130daa3f16c0f93905
Submitter: Zuul
Branch: master

commit 6686406bce9e7fc9623dea130daa3f16c0f93905
Author: Martin Schuppert <email address hidden>
Date: Tue Oct 23 17:10:32 2018 +0200

    Split off metadata vendordata plugin in own class

    A recent change making nova-metadata-api work with wsgi [1] 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 the parameters are also
    used in compute drivers (in the ironic driver, for instance), thats
    why we should split them to be able to deploy nova-metadata-api
    separate from nova-compute.

    [1] https://review.openstack.org/#/c/582621/

    Change-Id: Ic3654c79d8cf275f0c58d57a4b66e2598450a7ed
    Related-Bug: 1799352

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to puppet-nova (stable/rocky)

Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/614083

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to puppet-nova (stable/rocky)

Reviewed: https://review.openstack.org/614083
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=a378567fa8e175a08bda5da85e1d58b9def4ee7a
Submitter: Zuul
Branch: stable/rocky

commit a378567fa8e175a08bda5da85e1d58b9def4ee7a
Author: Martin Schuppert <email address hidden>
Date: Tue Oct 23 17:10:32 2018 +0200

    Split off metadata vendordata plugin in own class

    A recent change making nova-metadata-api work with wsgi [1] 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 the parameters are also
    used in compute drivers (in the ironic driver, for instance), thats
    why we should split them to be able to deploy nova-metadata-api
    separate from nova-compute.

    [1] https://review.openstack.org/#/c/582621/

    Change-Id: Ic3654c79d8cf275f0c58d57a4b66e2598450a7ed
    Related-Bug: 1799352
    (cherry picked from commit 6686406bce9e7fc9623dea130daa3f16c0f93905)

tags: added: in-stable-rocky
Changed in puppet-nova:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 10.2.0

This issue was fixed in the openstack/tripleo-heat-templates 10.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 9.1.0

This issue was fixed in the openstack/tripleo-heat-templates 9.1.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.