Bug #1473129 “When deploying an environment containing only a He...” : Series kilo : Bugs : Murano

Revision history for this message

Yuki Nishiwaki (uckey-1067) wrote on 2015-07-10:

#1

I encountered this phenomenon too. But I don't make out if this is bug.

Serg Melikyan (smelikyan) on 2015-07-14

Changed in murano:
milestone:	none → liberty-2
status:	New → Confirmed
importance:	Undecided → Medium

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2015-07-30: Fix proposed to murano (master)

#2

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

Changed in murano:
assignee:	nobody → Stan Lagun (slagun)
status:	Confirmed → In Progress

Kirill Zaitsev (kzaitsev) on 2015-07-31

tags:	added: kilo-backport-potential
tags:	added: engine

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2015-08-02: Fix merged to murano (master)

#3

Reviewed: https://review.openstack.org/207642
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=fc586b949d489343de9894ec92d21990f65a1e32
Submitter: Jenkins
Branch: master

commit fc586b949d489343de9894ec92d21990f65a1e32
Author: Stan Lagun <email address hidden>
Date: Fri Jul 31 00:50:34 2015 +0300

Removes early creation of Heat stack

    Murano environment deployment started with empty stack
    creation so that it can be done prior to keystone token expiration
    for Heat to establish trusts based on user's token.
    When environment does nothing with the stack (for example
    all environment applications are HOT based and deploy into their
    own stacks) empty stack remains. Because most applications
    start their deployment with instance/other resources deployment
    stack will be created early anyway. So this strategy is redundant.

Change-Id: Id8ec1df2c83f540b272ef70bd054f70de9da7715
Closes-Bug: #1473129

Changed in murano:
status:	In Progress → Fix Committed

Serg Melikyan (smelikyan) on 2015-08-03

summary:

- When deploying an environment containnig only a Heat generated package,
+ When deploying an environment containing only a Heat generated package,
an extra empty stack is created in Heat

Serg Melikyan (smelikyan) on 2015-08-03

Changed in murano:
status:	Fix Committed → Fix Released

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2015-08-10: Fix proposed to murano (stable/kilo)

#4

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/211155

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2015-08-11: Fix merged to murano (stable/kilo)

#5

Reviewed: https://review.openstack.org/211155
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=35496249d19f4b3f086e14dca964edf43fe9356d
Submitter: Jenkins
Branch: stable/kilo

commit 35496249d19f4b3f086e14dca964edf43fe9356d
Author: Stan Lagun <email address hidden>
Date: Fri Jul 31 00:50:34 2015 +0300

Removes early creation of Heat stack

    Murano environment deployment started with empty stack
    creation so that it can be done prior to keystone token expiration
    for Heat to establish trusts based on user's token.
    When environment does nothing with the stack (for example
    all environment applications are HOT based and deploy into their
    own stacks) empty stack remains. Because most applications
    start their deployment with instance/other resources deployment
    stack will be created early anyway. So this strategy is redundant.

    Change-Id: Id8ec1df2c83f540b272ef70bd054f70de9da7715
    Closes-Bug: #1473129
    (cherry picked from commit fc586b949d489343de9894ec92d21990f65a1e32)

Serg Melikyan (smelikyan) on 2015-10-15

Changed in murano:
milestone:	liberty-2 → 1.0.0

Kirill Zaitsev (kzaitsev) on 2015-11-06

Changed in murano:
milestone:	1.0.0 → 1.0.1

Revision history for this message

Doug Hellmann (doug-hellmann) wrote on 2016-06-08: Fix included in openstack/murano 2015.1.1

#6

This issue was fixed in the openstack/murano 2015.1.1 release.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-11-10:

#7

This issue was fixed in the openstack/murano 2015.1.1 release.

Murano

When deploying an environment containing only a Heat generated package, an extra empty stack is created in Heat

Bug Description

Other bug subscribers

Remote bug watches

Affects		Status	Importance	Assigned to	Milestone
	Murano	Fix Released	Medium	Stan Lagun	Murano 1.0.1
	Kilo	Fix Committed	Undecided	Kirill Zaitsev