| 2014-09-18 18:03:15 |
Tatyana Dubyk |
bug |
|
|
added bug |
| 2014-09-18 18:06:03 |
Tatyana Dubyk |
description |
On Ubuntu in simple mode on vcenter's machine, when deploy of openstack has already been stopped on one of nodes then this node is bootstrapped, but provisioning is not started.
==============vcenter settings===========================
export VCENTER_IP='172.16.0.254'
export VCENTER_USERNAME='administrator@vsphere.local'
export VCENTER_PASSWORD='Qwer!1234'
export VCENTER_CLUSTERS='Cluster1,Cluster2'
=====================================================
Configuration:
===================================================
steps to reproduce:
1.set up lab on vcenter's machine from 5.1-11(RC5) iso
2.create env and start deploy:
OS: Ubuntu (simple mode)
create nodes with roles: 1st - controller,
2nd - cinder (vmdk)
3. start deployment
4. check that openstack has already been installed on node with controller role
and status is 'ready'
6. while openstack process is continued on node with cinder role
stop deploy by clicking button in Fuel UI.
7. wait until node with cinder role will be in 'offline' status
8. then wait until node with cinder role will be in 'pending addition' status
9. then start re-deploy on this node again.
10. check that node has already been bootstapped, but provisioning is not started
and in fuel ui we can see that still nothing happend on this node
but on master node 'fuel nodes list' command gives info that on this node provisioning is started.
11. And this node hangs on.
Expected result: Deployment process of openstack on each of nodes will be finished successfully
Actual result: deployment of openstack on node with controller role is hanging on after bootstarping.
--------------------------Logs------------------------------------
---------------------fuel-version---------------------------------
[root@nailgun ~]# fuel nodes list
id | status | name | cluster | ip | mac | roles | pending_roles | online
---|--------------|------------------|---------|---------------|-------------------|------------|---------------|-------
6 | ready | Untitled (c5:cf) | 4 | 10.108.10.3 | 64:8f:b2:8e:c5:cf | controller | | True
7 | discover | Untitled (49:62) | None | 10.108.10.130 | 64:ed:3f:72:49:62 | | | True
8 | discover | Untitled (08:a4) | None | 10.108.10.227 | 64:38:d7:88:08:a4 | | | True
10 | discover | Untitled (87:a4) | None | 10.108.10.191 | 64:ba:f4:e0:87:a4 | | | True
9 | provisioning | Untitled (b7:e2) | 4 | 10.108.10.197 | 64:47:93:c5:b7:e2 | cinder | | True |
On Ubuntu in simple mode on vcenter's machine, when deploy of openstack has already been stopped on one of nodes then this node is bootstrapped, but provisioning is not started.
==============vcenter settings===========================
export VCENTER_IP='172.16.0.254'
export VCENTER_USERNAME='administrator@vsphere.local'
export VCENTER_PASSWORD='Qwer!1234'
export VCENTER_CLUSTERS='Cluster1,Cluster2'
=====================================================
Configuration:
===================================================
steps to reproduce:
1.set up lab on vcenter's machine from 5.1-11(RC5) iso
2.create env and start deploy:
OS: Ubuntu (simple mode)
create nodes with roles: 1st - controller,
2nd - cinder (vmdk)
3. start deployment
4. check that openstack has already been installed on node with controller role
and status is 'ready'
6. while openstack process is continued on node with cinder role
stop deploy by clicking button in Fuel UI.
7. wait until node with cinder role will be in 'offline' status
8. then wait until node with cinder role will be in 'pending addition' status
9. then start re-deploy on this node again.
10. check that node has already been bootstapped, but provisioning is not started
and in fuel ui we can see that still nothing happend on this node
but on master node 'fuel nodes list' command gives info that on this node provisioning is started.
11. And this node hangs on.
Expected result: Deployment process of openstack on each of nodes will be finished successfully
Actual result: deployment of openstack on node with controller role is hanging on after bootstarping.
--------------------------Logs------------------------------------
---------------------fuel-version---------------------------------
[root@nailgun ~]# fuel nodes list
id | status | name | cluster | ip | mac | roles | pending_roles | online
---|--------------|------------------|---------|---------------|-------------------|------------|---------------|-------
6 | ready | Untitled (c5:cf) | 4 | 10.108.10.3 | 64:8f:b2:8e:c5:cf | controller | | True
7 | discover | Untitled (49:62) | None | 10.108.10.130 | 64:ed:3f:72:49:62 | | | True
8 | discover | Untitled (08:a4) | None | 10.108.10.227 | 64:38:d7:88:08:a4 | | | True
10 | discover | Untitled (87:a4) | None | 10.108.10.191 | 64:ba:f4:e0:87:a4 | | | True
9 | provisioning | Untitled (b7:e2) | 4 | 10.108.10.197 | 64:47:93:c5:b7:e2 | cinder | | True |
|
| 2014-09-18 18:06:54 |
Tatyana Dubyk |
attachment added |
|
Diagnostic snapshot https://bugs.launchpad.net/fuel/+bug/1371225/+attachment/4207782/+files/fuel-snapshot-2014-09-18_17-25-57.tgz |
|
| 2014-09-18 18:07:12 |
Tatyana Dubyk |
bug |
|
|
added subscriber Evgeniya Shumakher |
| 2014-09-18 18:07:32 |
Tatyana Dubyk |
bug |
|
|
added subscriber Eugene Korekin |
| 2014-09-18 18:07:42 |
Tatyana Dubyk |
bug |
|
|
added subscriber Igor Gajsin |
| 2014-09-18 18:08:10 |
Tatyana Dubyk |
bug |
|
|
added subscriber Andrey Danin |
| 2014-09-18 18:08:37 |
Tatyana Dubyk |
bug |
|
|
added subscriber Stepan Rogov |
| 2014-09-18 19:51:14 |
Bogdan Dobrelya |
fuel: assignee |
|
Fuel Python Team (fuel-python) |
|
| 2014-09-19 07:38:03 |
Ihor Kalnytskyi |
fuel: milestone |
|
6.0 |
|
| 2014-09-19 07:38:15 |
Ihor Kalnytskyi |
fuel: importance |
Undecided |
Medium |
|
| 2014-09-23 20:27:08 |
Dmitry Pyzhov |
fuel: assignee |
Fuel Python Team (fuel-python) |
Andrey Danin (gcon-monolake) |
|
| 2014-09-23 21:46:11 |
Evgeniya Shumakher |
fuel: assignee |
Andrey Danin (gcon-monolake) |
Fuel Partner Integration Team (fuel-partner) |
|
| 2014-10-23 18:44:23 |
Andrey Danin |
fuel: status |
New |
Confirmed |
|
| 2014-10-23 18:44:29 |
Andrey Danin |
fuel: assignee |
Fuel Partner Integration Team (fuel-partner) |
|
|
| 2014-10-23 19:24:50 |
Andrey Danin |
fuel: status |
Confirmed |
Triaged |
|
| 2014-10-23 19:25:50 |
Andrey Danin |
fuel: status |
Triaged |
Confirmed |
|
| 2014-10-23 19:26:32 |
Andrey Danin |
summary |
On Ubuntu in simple mode on vcenter's machine, when deploy of openstack has already been stopped on one of nodes then this node is bootstrapped, but provisioning is not started. |
nailgun-agent reports status back while node is deleting |
|
| 2014-10-28 11:48:31 |
Matthew Mosesohn |
fuel: assignee |
|
Fuel Python Team (fuel-python) |
|
| 2014-10-29 11:43:21 |
Andrey Danin |
tags |
vcenter |
|
|
| 2014-11-19 16:42:16 |
Roman Prykhodchenko |
fuel: milestone |
6.0 |
6.1 |
|
| 2014-12-17 13:02:36 |
Andrey Danin |
nominated for series |
|
fuel/6.0.x |
|
| 2014-12-17 13:02:36 |
Andrey Danin |
bug task added |
|
fuel/6.0.x |
|
| 2014-12-17 13:02:54 |
Andrey Danin |
nominated for series |
|
fuel/6.1.x |
|
| 2014-12-17 13:02:54 |
Andrey Danin |
bug task added |
|
fuel/6.1.x |
|
| 2014-12-17 13:03:12 |
Andrey Danin |
fuel/6.1.x: status |
New |
Confirmed |
|
| 2014-12-17 13:03:16 |
Andrey Danin |
fuel/6.1.x: importance |
Undecided |
Medium |
|
| 2014-12-17 13:03:26 |
Andrey Danin |
fuel/6.1.x: assignee |
|
Fuel Python Team (fuel-python) |
|
| 2014-12-17 13:03:31 |
Andrey Danin |
fuel/6.1.x: milestone |
|
6.1 |
|
| 2014-12-17 13:03:37 |
Andrey Danin |
fuel/6.0.x: milestone |
6.1 |
6.0 |
|
| 2014-12-17 13:03:42 |
Andrey Danin |
fuel/6.0.x: status |
Confirmed |
Won't Fix |
|
| 2014-12-17 13:08:28 |
Andrey Danin |
description |
On Ubuntu in simple mode on vcenter's machine, when deploy of openstack has already been stopped on one of nodes then this node is bootstrapped, but provisioning is not started.
==============vcenter settings===========================
export VCENTER_IP='172.16.0.254'
export VCENTER_USERNAME='administrator@vsphere.local'
export VCENTER_PASSWORD='Qwer!1234'
export VCENTER_CLUSTERS='Cluster1,Cluster2'
=====================================================
Configuration:
===================================================
steps to reproduce:
1.set up lab on vcenter's machine from 5.1-11(RC5) iso
2.create env and start deploy:
OS: Ubuntu (simple mode)
create nodes with roles: 1st - controller,
2nd - cinder (vmdk)
3. start deployment
4. check that openstack has already been installed on node with controller role
and status is 'ready'
6. while openstack process is continued on node with cinder role
stop deploy by clicking button in Fuel UI.
7. wait until node with cinder role will be in 'offline' status
8. then wait until node with cinder role will be in 'pending addition' status
9. then start re-deploy on this node again.
10. check that node has already been bootstapped, but provisioning is not started
and in fuel ui we can see that still nothing happend on this node
but on master node 'fuel nodes list' command gives info that on this node provisioning is started.
11. And this node hangs on.
Expected result: Deployment process of openstack on each of nodes will be finished successfully
Actual result: deployment of openstack on node with controller role is hanging on after bootstarping.
--------------------------Logs------------------------------------
---------------------fuel-version---------------------------------
[root@nailgun ~]# fuel nodes list
id | status | name | cluster | ip | mac | roles | pending_roles | online
---|--------------|------------------|---------|---------------|-------------------|------------|---------------|-------
6 | ready | Untitled (c5:cf) | 4 | 10.108.10.3 | 64:8f:b2:8e:c5:cf | controller | | True
7 | discover | Untitled (49:62) | None | 10.108.10.130 | 64:ed:3f:72:49:62 | | | True
8 | discover | Untitled (08:a4) | None | 10.108.10.227 | 64:38:d7:88:08:a4 | | | True
10 | discover | Untitled (87:a4) | None | 10.108.10.191 | 64:ba:f4:e0:87:a4 | | | True
9 | provisioning | Untitled (b7:e2) | 4 | 10.108.10.197 | 64:47:93:c5:b7:e2 | cinder | | True |
On Ubuntu in simple mode on vcenter's machine, when deploy of openstack has already been stopped on one of nodes then this node is bootstrapped, but provisioning is not started.
==============vcenter settings===========================
export VCENTER_IP='172.16.0.254'
export VCENTER_USERNAME='administrator@vsphere.local'
export VCENTER_PASSWORD='Qwer!1234'
export VCENTER_CLUSTERS='Cluster1,Cluster2'
=====================================================
Configuration:
===================================================
steps to reproduce:
1.set up lab on vcenter's machine from 5.1-11(RC5) iso
2.create env and start deploy:
OS: Ubuntu (simple mode)
create nodes with roles: 1st - controller,
2nd - cinder (vmdk)
3. start deployment
4. check that openstack has already been installed on node with controller role
and status is 'ready'
6. while openstack process is continued on node with cinder role
stop deploy by clicking button in Fuel UI.
7. wait until node with cinder role will be in 'offline' status
8. then wait until node with cinder role will be in 'pending addition' status
9. then start re-deploy on this node again.
10. check that node has already been bootstapped, but provisioning is not started
and in fuel ui we can see that still nothing happend on this node
but on master node 'fuel nodes list' command gives info that on this node provisioning is started.
11. And this node hangs on.
Expected result: Deployment process of openstack on each of nodes will be finished successfully
Actual result: deployment of openstack on node with controller role is hanging on after bootstarping.
--------------------------Logs------------------------------------
---------------------fuel-version---------------------------------
[root@nailgun ~]# fuel nodes list
id | status | name | cluster | ip | mac | roles | pending_roles | online
---|--------------|------------------|---------|---------------|-------------------|------------|---------------|-------
6 | ready | Untitled (c5:cf) | 4 | 10.108.10.3 | 64:8f:b2:8e:c5:cf | controller | | True
7 | discover | Untitled (49:62) | None | 10.108.10.130 | 64:ed:3f:72:49:62 | | | True
8 | discover | Untitled (08:a4) | None | 10.108.10.227 | 64:38:d7:88:08:a4 | | | True
10 | discover | Untitled (87:a4) | None | 10.108.10.191 | 64:ba:f4:e0:87:a4 | | | True
9 | provisioning | Untitled (b7:e2) | 4 | 10.108.10.197 | 64:47:93:c5:b7:e2 | cinder | | True
The reason:
It was because node-9 sent their status to Nailgun after the node was started to reboot by MCagent but before an actual reboot occured. It was because nailgun-agent checks the '/var/run/nodiscover' file and then sleeps the rand(30) interval. In case of this bug Astute created the /var/run/nodiscover file after nailgun-agent had checked the file but before the sleep finished.
How to fix:
We should just move this sleep before /var/run/nodiscover file checking. |
|
| 2014-12-17 13:12:47 |
Andrey Danin |
fuel: status |
Confirmed |
Won't Fix |
|
| 2014-12-17 13:12:53 |
Andrey Danin |
bug task deleted |
fuel/6.0.x |
|
|
| 2015-02-19 23:20:39 |
Dmitry Pyzhov |
bug task deleted |
fuel/6.1.x |
|
|
| 2015-02-19 23:20:43 |
Dmitry Pyzhov |
fuel: status |
Won't Fix |
Confirmed |
|
| 2015-02-19 23:20:46 |
Dmitry Pyzhov |
fuel: milestone |
6.0 |
6.1 |
|
| 2015-03-27 16:20:29 |
Dmitry Pyzhov |
tags |
|
module-nailgun-agent |
|
| 2015-04-02 14:13:15 |
Nikolay Markov |
fuel: assignee |
Fuel Python Team (fuel-python) |
Nikolay Markov (nmarkov) |
|
| 2015-04-03 14:21:19 |
Nikolay Markov |
fuel: status |
Confirmed |
In Progress |
|
| 2015-04-08 16:34:17 |
Nikolay Markov |
fuel: status |
In Progress |
Fix Committed |
|
