[upgrade][8.0] Keystone failed to start - wrong container restart order

Bug #1599094 reported by Vladimir Khlyunev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Sergey Abramov

Bug Description

Steps to reproduce:
1. Deploy 7.0 Fuel master
2. Backup data using octane
3. Install Fuel 8.0
4. Apply latest MU + proposed MU
5. Try to restore the backup

Result:
2016-07-04 16:34:17 INFO octane.util.subprocess dockerctl[12748] stdout: checking with command "! shell_container keystone pgrep puppet"
2016-07-04 16:34:17 INFO octane.util.subprocess dockerctl[12748] stdout: ERROR: keystone failed to start.
2016-07-04 16:34:17 INFO octane.util.subprocess Process dockerctl finished with return value 1

Changed in fuel:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-octane (stable/8.0)

Reviewed: https://review.openstack.org/337565
Committed: https://git.openstack.org/cgit/openstack/fuel-octane/commit/?id=1e6bc80ee323cec2be1febd646b9e8ca170afa1d
Submitter: Jenkins
Branch: stable/8.0

commit 1e6bc80ee323cec2be1febd646b9e8ca170afa1d
Author: Sergey Abramov <email address hidden>
Date: Tue Jul 5 12:08:45 2016 +0300

    Stop all docker containers using docker destroy all

    Required for stop and start docker containers
    in order listed by dockerctl.

    Change-Id: Ifb8cf38f3151bff19891d7877180b99406acb06b
    Closes-bug: 1599094

Changed in fuel:
status: Confirmed → 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.