Fuel Master 5.1 upgrade fails due to unexpected docker issues

Bug #1362685 reported by Matthew Mosesohn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Evgeniy L

Bug Description

This is a placeholder bug to refer users to more troubleshooting of Fuel Master 5.1 upgrades.

There are two known issues to address:
1 - Docker IP address allocation made a mistake and gave the same IP to 2 different containers
2 - Docker unexpectedly crashed during the upgrade process

A user should run `service docker start` and then `dockerctl build` to turn on all containers and then repeat the upgrade process.

Tags: upgrade
Evgeniy L (rustyrobot)
tags: added: upgrade
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to fuel-web (master)

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

Changed in fuel:
assignee: Matthew Mosesohn (raytrac3r) → Evgeniy L (rustyrobot)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (master)

Reviewed: https://review.openstack.org/117818
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=baaeee59026cdad605532dd4e6db04cb6bad306a
Submitter: Jenkins
Branch: master

commit baaeee59026cdad605532dd4e6db04cb6bad306a
Author: Evgeniy L <email address hidden>
Date: Fri Aug 29 19:29:18 2014 +0400

    Upgrades, added documentation for user in case of errors

    We have some known issues which we cannot
    address right now, in order to make user's
    live better, we decided to add documentation
    which will help user to workaround problems
    which he can have during the upgrade.

    Change-Id: I7381545f027d06d04b4144a466830af1e4a59b92
    Closes-bug: #1362685

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Evgeniy L (rustyrobot) wrote :

Merged in 5.1 because it's more about documentation.

Changed in fuel:
status: Fix Committed → Fix Released
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.