Deleting a software deployment doesn't push new metadata

Bug #1523705 reported by Steve Baker on 2015-12-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Steve Baker

Bug Description

This is not known to cause any issues, but metadata should immediately reflect current active deployments, so deletions should propagate immediately.

Changed in heat:
importance: Undecided → Medium
assignee: nobody → Steve Baker (steve-stevebaker)

Fix proposed to branch: master
Review: https://review.openstack.org/254433

Changed in heat:
status: New → In Progress
Changed in heat:
milestone: none → mitaka-2
Changed in heat:
milestone: mitaka-2 → mitaka-3

Reviewed: https://review.openstack.org/254433
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=4b3a4aa96a9973166947b4e16a5f5c6354437bfa
Submitter: Jenkins
Branch: master

commit 4b3a4aa96a9973166947b4e16a5f5c6354437bfa
Author: Steve Baker <email address hidden>
Date: Wed Jan 20 09:17:52 2016 +1300

    Push deployments metadata on delete

    When a deployment is deleted the metadata needs to be pushed so that
    stale deployment data is not present in the metadata. There is a risk
    that stale data will mask other deployments.

    Change-Id: I3df4d9a27be5e59609ac4374556d3c0c707b068b
    Closes-Bug: #1523705

Changed in heat:
status: In Progress → Fix Released

This issue was fixed in the openstack/heat 6.0.0.0b3 development milestone.

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

Other bug subscribers