Comment 34 for bug 1394188

Revision history for this message
Aleksandr Didenko (adidenko) wrote : Re: Deployment of additional/replace controller fails

Tested on 6.1 #315 ISO:
    "api": "1.0",
    "astute_sha": "36a3d54baf86480326866279778b867086aa4b05",
    "auth_required": true,
    "build_id": "2015-04-16_03-32-26",
    "build_number": "315",
    "feature_groups": [
        "mirantis"
    ],
    "fuellib_sha": "ab6dbba825a5e54f3183ed8582921a0328b211c7",
    "fuelmain_sha": "d3aa72d814c3f18799b566363004a22591161cef",
    "nailgun_sha": "24b56283fb4caaba6b6414056dad30e503a7c30f",
    "openstack_version": "2014.2-6.1",
    "ostf_sha": "90f232a25d10f98db9d5531a3b133319529f57aa",
    "production": "docker",
    "python-fuelclient_sha": "ff186de358cbda489a320723de47a9e61ae23364",
    "release": "6.1",

New controller and all existing nodes are in 'ready' state, no errors in puppet log:
http://paste.openstack.org/show/204180/

OpenStack is working, OSTF passes. But I can see the following issues in corosync cluster:
http://paste.openstack.org/show/204181/

According to the snapshot provided above, there was also some problem with adding new node to corosync cluster. Investigating it further.