[8.0] After delete node from db using CLI and destroy it nova lost all alive computes

Bug #1580680 reported by Vadim Rovachev on 2016-05-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Fuel Sustaining

Bug Description

Detailed bug description:
Swarm test failed:
https://patching-ci.infra.mirantis.net/job/8.0.system_test.ubuntu.command_line/12/console
Steps to reproduce:
Create a cluster using Fuel CLI
Provision a controller node using Fuel CLI
Provision two compute+cinder nodes using Fuel CLI
Deploy the controller node using Fuel CLI
Deploy the compute+cinder nodes using Fuel CLI
Destroy one of computes
Wait until one of computes become offline
Delete offline compute from fuel db
run ostf.

Expected results:
smoke tests are passed

Actual result:
Failed 7 OSTF tests; should fail 1 tests. Names of failed tests:
  - Check that required services are running (failure) Some nova services have not been started.. Please refer to OpenStack logs for more details.
  - Create volume and boot instance from it (failure) Failed to get to expected status. In error state. Please refer to OpenStack logs for more details.
  - Create volume and attach it to instance (failure) Failed to get to expected status. In error state. Please refer to OpenStack logs for more details.
  - Check network connectivity from instance via floating IP (failure) Failed to get to expected status. In error state. Please refer to OpenStack logs for more details.
  - Launch instance (failure) Failed to get to expected status. In error state. Please refer to OpenStack logs for more details.
  - Launch instance with file injection (failure) Failed to get to expected status. In error state. Please refer to OpenStack logs for more details.
  - Launch instance, create snapshot, launch instance from snapshot (failure) Failed to get to expected status. In error state. Please refer to OpenStack logs for more details.

-------------------------------

[root@nailgun ~]# fuel nodes
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|--------|------------------|---------|------------|-------------------|-----------------|---------------|--------|---------
3 | ready | Untitled (36:e2) | 1 | 10.109.0.3 | 26:a2:2d:64:fb:32 | controller | | True | 1
2 | ready | Untitled (4d:22) | 1 | 10.109.0.4 | 64:fa:50:81:4d:22 | cinder, compute | | True | 1

-------------------------------

root@node-3:~# nova-manage service list
No handlers could be found for logger "oslo_config.cfg"
Binary Host Zone Status State Updated_At
nova-consoleauth node-3.test.domain.local internal enabled :-) 2016-05-11 16:15:00
nova-cert node-3.test.domain.local internal enabled :-) 2016-05-11 16:15:00
nova-scheduler node-3.test.domain.local internal enabled :-) 2016-05-11 16:15:00
nova-conductor node-3.test.domain.local internal enabled :-) 2016-05-11 16:15:00
nova-compute node-1.test.domain.local nova enabled XXX 2016-05-10 16:51:01

Vadim Rovachev (vrovachev) wrote :
Changed in fuel:
milestone: none → 8.0-updates
importance: Undecided → High
Peter Zhurba (pzhurba) on 2016-05-13
tags: added: area-library area-mos
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Peter Zhurba (pzhurba) wrote :
Changed in fuel:
status: New → Confirmed
Vadim Rovachev (vrovachev) wrote :

I think that it means that this bug is periodically.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers