Stop deployment while adding compute node to existing cluster leads to the destruction of the cluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Artem Roma | ||
5.1.x |
In Progress
|
Critical
|
Rodion Tikunov | ||
6.0.x |
In Progress
|
Critical
|
Rodion Tikunov | ||
6.1.x |
Fix Released
|
Critical
|
Rodion Tikunov | ||
7.0.x |
Fix Released
|
Critical
|
Rodion Tikunov | ||
8.0.x |
Fix Released
|
Critical
|
Artem Roma | ||
Mitaka |
Fix Released
|
Critical
|
Artem Roma |
Bug Description
ISO # 361, KVM
Steps to reproduce :
1. Deploy any environment with 3 controllers, 1 compute and NeutronTUN or NeutronVLAN
2. Add 1 compute to the cluster
3. Deploy changes
4. Stop deployment at the middle of re-deployment of non-primary controllers
5. Run OSTF
Actual result:
After stopped deployment process - non primary controller's are deleted and new compute - become "ready".
From astute log:
2015-12-28 18:15:04 INFO [847] Replace running task 56f35e3d-
{"args"=>
{"engine"=>
{"url"=>"http://
"username"
"password"
"master_
"nodes"=>
[{"
"uid"=>"3",
"
"
{"
"uid"=>"2",
"
"
"stop_
"task_
"respond_
"method"
"api_version"
2015-12-28 18:15:04 INFO [847] Processing RPC call 'stop_deploy_task'
There is no way to run OSTF via WEB-UI, only via CLI with --force flag
[root@nailgun ~]# fuel --env 1 health --check smoke --force
[ 1 of 12] [failure] 'Create instance flavor' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[ 2 of 12] [failure] 'Check create, update and delete image actions using Glance v2' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[ 3 of 12] [failure] 'Create volume and boot instance from it' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[ 4 of 12] [failure] 'Create volume and attach it to instance' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[ 5 of 12] [failure] 'Check network connectivity from instance via floating IP' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[ 6 of 12] [failure] 'Create keypair' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[ 7 of 12] [failure] 'Create security group' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[ 8 of 12] [failure] 'Check network parameters' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[ 9 of 12] [failure] 'Launch instance' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[10 of 12] [failure] 'Launch instance with file injection' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[11 of 12] [failure] 'Launch instance, create snapshot, launch instance from snapshot' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
[12 of 12] [failure] 'Create user and authenticate with it.' (0.0 s) Can not set proxy for Health Check.Make sure that network configuration for controllers is correct
Keystone service - is completely dead on primary controller
root@node-1:~# source openrc
root@node-1:~# keystone catalog
/usr/lib/
'python-
/usr/lib/
'the 2.0.0 release.', DeprecationWarning)
/usr/lib/
super(Client, self)._
/usr/lib/
return f(*args, **kwargs)
/usr/lib/
'the 2.0.0 release.', DeprecationWarning)
Authorization Failed: Unable to establish connection to http://
root@node-1:~# glance image-list
Unable to establish connection to http://
summary: |
- Stop deployment while adding node to existing clusterleads to the + Stop deployment while adding node to existing cluster leads to the destruction of the cluster |
description: | updated |
summary: |
- Stop deployment while adding node to existing cluster leads to the - destruction of the cluster + Stop deployment while adding compute node to existing cluster leads to + the destruction of the cluster |
description: | updated |
tags: |
added: area-library removed: area-python |
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
no longer affects: | fuel/mitaka |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
tags: | added: team-bugfix |
Changed in fuel: | |
status: | Incomplete → Confirmed |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Artem Roma (aroma-x) |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: on-verification |
tags: | added: customer-found |
tags: | added: on-verification |
tags: | added: on-verification |
no workarounds - redeploy is not possible