Fuel for OpenStack

[octane] replaced_deployment_info should be dropped after upgrade-control

Bug #1621439 reported by Roman Sokolkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Ilya Kharin
Fuel for OpenStack 9.1

Bug Description

Octane uses replaced_deployment_info to deploy primary controller in isolated mode. We need to wipe replaced_deployment_info when transition phase passed.

We will get errors if user will change smth in environment after upgrade.

Workaround:
Execute following command after octane upgrade-control

fuel deployment default --delete --node <UPGRADED_CONTROLLER> --env <SEED>

See original description
Roman Sokolkov (rsokolkov)
description: updated
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: nobody → Fuel Octane (fuel-octane-team)
importance: Undecided → High
milestone: none → 9.1
Ilya Kharin (akscram)
Changed in fuel:
status: New → Confirmed
assignee: Fuel Octane (fuel-octane-team) → Ilya Kharin (akscram)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-octane (master)

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

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-octane (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/368363

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-octane (master)

Reviewed: https://review.openstack.org/368271
Committed: https://git.openstack.org/cgit/openstack/fuel-octane/commit/?id=f3c6b95a45ea28cd615a0d484b972bc086b44740
Submitter: Jenkins
Branch: master

commit f3c6b95a45ea28cd615a0d484b972bc086b44740
Author: Ilya Kharin <email address hidden>
Date: Sat Sep 10 03:49:45 2016 +0300

    Remove replaced deployment info

    The replaced deployment information have to be removed after the
    upgrade-control operation because it contains some specific
    modifications only to support isolation mode on the primary controller
    and after removing of the isolation mode there is no more necessity in
    it.

    Change-Id: I5b056a5afcefb0114ec374d2ee9596abccf967fa
    Closes-Bug: #1621439

Changed in fuel:
status: In Progress → Fix Committed
tags: added: in-stable-mitaka
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-octane (stable/mitaka)

Reviewed: https://review.openstack.org/368363
Committed: https://git.openstack.org/cgit/openstack/fuel-octane/commit/?id=ba2289bb043c077548cedaff7f20870f4257466c
Submitter: Jenkins
Branch: stable/mitaka

commit ba2289bb043c077548cedaff7f20870f4257466c
Author: Ilya Kharin <email address hidden>
Date: Sat Sep 10 03:49:45 2016 +0300

    Remove replaced deployment info

    The replaced deployment information have to be removed after the
    upgrade-control operation because it contains some specific
    modifications only to support isolation mode on the primary controller
    and after removing of the isolation mode there is no more necessity in
    it.

    Change-Id: I5b056a5afcefb0114ec374d2ee9596abccf967fa
    Closes-Bug: #1621439

Revision history for this message
Vladimir Khlyunev (vkhlyunev) wrote :

Snapshot 298 - no regression, cluster upgraded successfully 3 times in a row

Changed in fuel:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/fuel-octane ocata-eol

This issue was fixed in the openstack/fuel-octane ocata-eol release.

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

Other bug subscribers

Remote bug watches

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