[nailgun][python-fuelclient] Nailgun reports about successful cluster deployment without any nodes if use python-fuelclient
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
In Progress
|
Low
|
Nikolay Tymtsiv | ||
Mitaka |
Confirmed
|
Low
|
Fuel Sustaining |
Bug Description
Detailed bug description:
Nailgun reports about successful 'empty' cluster deployment if use python-fuelclient.
Steps to reproduce:
1. Deploy Fuel (e.g. 1 master + 5 nodes).
2. Create env and DO NOT add any nodes to it.
3. Try to deploy 'empty' environment:
[root@fuel ~]# fuel2 env deploy 2
Deployment task with id 3 for the environment 2 has been started.
4. Fuel Dashboard reports about successful cluster deployment in a 5-6 seconds (see attached).
5 Also try to get list of tasks:
[root@fuel ~]# fuel2 task list
+----+-
| id | status | name | cluster | result | progress |
+----+-
| 1 | ready | cluster_deletion | None | {} | 100 |
| 3 | ready | deploy | 2 | {} | 100 |
| 6 | ready | deployment | 2 | {} | 100 |
+----+-
[root@fuel ~]# fuel2 task show 3
+------
| Field | Value |
+------
| id | 3 |
| uuid | 681a2fc1-
| status | ready |
| name | deploy |
| cluster | 2 |
| result | {} |
| progress | 100 |
| message | Deployment is done. No changes. |
+------
[root@fuel ~]# fuel2 task show 6
+------
| Field | Value |
+------
| id | 6 |
| uuid | fd4c629a-
| status | ready |
| name | deployment |
| cluster | 2 |
| result | {} |
| progress | 100 |
| message | Deployment is done. No changes. |
+------
[root@fuel ~]# fuel2 task history show 6
Result: http://
Reproducibility:
Always
Description of the environment:
[root@fuel ~]# shotgun2 short-report
cat /etc/fuel_build_id:
401
cat /etc/fuel_
401
cat /etc/fuel_release:
10.0
cat /etc/fuel_
newton-10.0
no longer affects: | fuel/newton |
@Masksim, this bug is reproduced in fuel/newton (IS0 410): 0-community- 410-2016- 07-15_11- 14-00
15 Jul 2016 11:40:49 fuel-10.
[root@fuel ~]# shotgun2 short-report build_number: openstack_ version: network- checker| nailgun| packetary| shotgun' : 10.0.0- 1.mos290. noarch 10.0.0- 1.mos308. noarch 10.0.0- 1.mos8658. noarch 10.0.0- 1.mos93. noarch 10.0.0- 1.mos8658. noarch 10.0.0- 1.mos6367. noarch -metadata- 10.0.0- 1.mos8857. noarch 10.0.0- 1.mos947. noarch 10.0.0- 1.mos6367. noarch astute- 10.0.0- 1.mos765. noarch fuelclient- 10.0.0- 1.mos356. noarch checker- 10.0.0- 1.mos77. x86_64 10.0.0- 1.mos8658. noarch 10.0.0- 1.mos8857. noarch mcagents- 10.0.0- 1.mos765. noarch 10.0.0- 1.mos8658. noarch .0-10.0. 0-1.mos8658. noarch 10.0.0- 1.mos2835. noarch 0.0-1.mos6367. noarch -cli-10. 0.0-1.mos308. noarch
cat /etc/fuel_build_id:
410
cat /etc/fuel_
410
cat /etc/fuel_release:
10.0
cat /etc/fuel_
newton-10.0
rpm -qa | egrep 'fuel|astute|
fuelmenu-
fuel-agent-
fuel-migrate-
shotgun-
fuel-notify-
fuel-release-
fuel-openstack
fuel-ostf-
fuel-setup-
rubygem-
python-
network-
fuel-utils-
fuel-nailgun-
nailgun-
fuel-misc-
fuel-library10
fuel-ui-
fuel-10.
fuel-bootstrap
Here is the results from CLI: http:// paste.openstack .org/show/ 533091/
AS you can see cluster is in operational mode