Incorrect status of master node after restore

Bug #1342018 reported by Egor Kotko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Matthew Mosesohn

Bug Description

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "5.1"
  api: "1.0"
  build_number: "317"
  build_id: "2014-07-14_02-01-14"
  astute_sha: "d68cc542290b3176b7a556eb9accba5a38a88519"
  fuellib_sha: "1b17a7999969d87babbc7a07ba1c5c805d1588d8"
  ostf_sha: "9863db951a6e159f4fa6e6861c8331e1af069cf8"
  nailgun_sha: "638f4e09c5696d549482fabd0116f6008973291a"
  fuelmain_sha: "f32b958788e9d7acd904b31962b6bb71f9b66766"

Steps to reproduce:
1. Setup master node
2. Backup master node:
# dockerctl backup
3. Deploy cluster:
1Controller 1Compute, nova network
4. Restore master node:
# dockerctl restore <path/to/backup/arch.tar.lrz>

Expected result:
Workable master

Actual result:
Master node in non workable state.
http://paste.openstack.org/show/86521/

Tags: library
Changed in fuel:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Matthew Mosesohn (raytrac3r)
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :
Changed in fuel:
status: Confirmed → In Progress
Changed in fuel:
status: In Progress → 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.