kolla-ansible

support barbican upgrade permission issue

Bug #1646008 reported by zhubingbing on 2016-11-30

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
kolla	Fix Released	Undecided	Unassigned
Newton	Fix Released	High	Eduardo Gonzalez
kolla-ansible	Fix Released	High	zhubingbing	kolla-ansible ocata-3 "o3"

zhubingbing (zhubingbing) on 2016-11-30

Changed in kolla-ansible:
status:	New → Confirmed
importance:	Undecided → High
assignee:	nobody → zhubingbing (zhubingbing)
milestone:	none → ocata-3

Revision history for this message

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

Changed in kolla-ansible:
status:	Confirmed → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-12-02: Fix merged to kolla-ansible (master)

commit af3eaa5a23723d3c1cc1efccf737c9666fcbf746
Author: zhubingbing <email address hidden>
Date: Wed Nov 30 07:20:43 2016 +0000

Fix barbican upgrade permission issue

Change-Id: I08bfa65223fd42df218bfd9e81765d6f1a4e10c8
Closes-Bug: #1646008

Changed in kolla-ansible:
status:	In Progress → Fix Released

Revision history for this message

Eduardo Gonzalez (egonzalez90) wrote on 2016-12-14:

Don't know why but launchpad didnt tracked it.

Revision history for this message

This issue was fixed in the openstack/kolla-ansible 4.0.0.0b2 development milestone.

Revision history for this message

This issue was fixed in the openstack/kolla 3.0.2 release.

Eduardo Gonzalez (egonzalez90) on 2017-01-12

Changed in kolla:
status:	New → Fix Released

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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