Keystone isn't started after destroy/start master node

Bug #1366742 reported by Andrey Sledzinskiy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
Medium
Fuel Library (Deprecated)

Bug Description

{

    "build_id": "2014-09-08_00-01-11",
    "ostf_sha": "f7b5d9d0d1cfaba5f1fe1e2c634493e92bce11db",
    "build_number": "503",
    "auth_required": true,
    "api": "1.0",
    "nailgun_sha": "c1ec85c185d3be1bd6c97cf1a821d1e020253a23",
    "production": "docker",
    "fuelmain_sha": "9978b759c7bdefff887e2ffb39588ef616b88517",
    "astute_sha": "b622d9b36dbdd1e03b282b9ee5b7435ba649e711",
    "feature_groups": [
        "mirantis"
    ],
    "release": "5.1",
    "release_versions": {
        "2014.1.1-5.1": {
            "VERSION": {
                "build_id": "2014-09-08_00-01-11",
                "ostf_sha": "f7b5d9d0d1cfaba5f1fe1e2c634493e92bce11db",
                "build_number": "503",
                "api": "1.0",
                "nailgun_sha": "c1ec85c185d3be1bd6c97cf1a821d1e020253a23",
                "production": "docker",
                "fuelmain_sha": "9978b759c7bdefff887e2ffb39588ef616b88517",
                "astute_sha": "b622d9b36dbdd1e03b282b9ee5b7435ba649e711",
                "feature_groups": [
                    "mirantis"
                ],
                "release": "5.1",
                "fuellib_sha": "36ae367f521b1352b6303c6bddbe6a44519704f5"
            }
        }
    },
    "fuellib_sha": "36ae367f521b1352b6303c6bddbe6a44519704f5"

}

Problem is reproduced only on CI after reverting snapshot and destroy and start master node

Steps:
1. Deploy any ha cluster
2. After deployment destroy master node and then start it

Expected - cluster is operable, all containers are Up
Actual - Keystone container wasn't started

I wasn't able to reproduce this issue locally by destroying and starting master node

Logs are attached

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :
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.