Timeout of provisioning - controller failed to reboot after the end of provisioning

Bug #1325483 reported by Andrey Sledzinskiy on 2014-06-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Fuel Python (Deprecated)

Bug Description

Reproduced on {

    "build_id": "2014-05-30_00-41-31",
    "mirantis": "yes",
    "build_number": "331",
    "nailgun_sha": "0828946af6a2e757fb018c2f69f7f81f0ea4b7f1",
    "ostf_sha": "3690709d95c1f42506b6d955b44221910cec8527",
    "fuelmain_sha": "7fbe99c86a4fffcb5ebc5b86046dcf1c20776f61",
    "astute_sha": "55df06b2e84fa5d71a1cc0e78dbccab5db29d968",
    "release": "4.1B",
    "fuellib_sha": "c64ffdc5e7bfe7fa8eb971be1fea2260ee849ab5"

}

Steps:
1. Create next cluster - CentOs, simple, KVM, Vlan Nova-Network with tagging, Ceph for volumes, Savanna
2. Add 1 controller, 1 compute, 2 ceph nodes
3. Deploy cluster

Actual result - controller node failed to reboot after provisioning and deployment timed out
Logs are attached

Dima Shulyak (dshulyak) wrote :

Hi, i cant find relevant info in snapshot, do you have environment with 4.1.1?

I'm pretty sure this is duplcate for https://bugs.launchpad.net/fuel/+bug/1322573

Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
Ryan Moe (rmoe) wrote :

I don't think this is a duplicate. It doesn't sound like this issue is related to stopping the deployment.

Changed in fuel:
status: New → Invalid
status: Invalid → Incomplete
milestone: 4.1.1 → 4.1.2
Aleksandra Fedorova (bookwar) wrote :

In 4.1 centos thread_1 system test (4.1_fuelmain.system_test.centos.thread_1/165/) we have three failures for node-1 provisioning. Snapshots attached.

Mike Scherbakov (mihgen) wrote :

There were no updates on this bug for a while. Closing this as Invalid. Please reopen/create new bug if you face an issue again, please try to get more information/logs/steps to reproduce.

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers