Ask Your Question

BoW's profile - activity

2015-06-09 13:33:16 -0500 received badge  Popular Question (source)
2015-06-09 13:33:16 -0500 received badge  Notable Question (source)
2015-06-09 13:33:16 -0500 received badge  Famous Question (source)
2014-11-29 16:14:11 -0500 received badge  Famous Question (source)
2014-11-13 18:42:36 -0500 received badge  Notable Question (source)
2014-11-13 18:42:36 -0500 received badge  Popular Question (source)
2014-10-28 02:38:17 -0500 answered a question Fail to start the overcloud in Helion virt

Thanks kashifkarar. It is not a timeout issue, I have the log information while creating overcloud, it seems an immediate error and exit in one minutes, and it is caused by a error, not timeout.

  • echo 'HP - configuring overcloud - Fri Oct 24 00:58:49 UTC 2014' HP - configuring overcloud - Fri Oct 24 00:58:49 UTC 2014
  • [[ vlan101 == vlan* ]] … +--------------------------------------+------------+--------------------+----------------------+ | id | stack_name | stack_status | creation_time | +--------------------------------------+------------+--------------------+----------------------+ | 7e64d5c1-f3d0-4267-befb-fe7c2225f590 | overcloud | CREATE_IN_PROGRESS | 2014-10-24T00:59:42Z | +--------------------------------------+------------+--------------------+----------------------+ ++ echo 'Waiting for the overcloud stack to be ready' Waiting for the overcloud stack to be ready +++ date ++ echo 'HP: Fri Oct 24 00:59:54 UTC 2014 this could take up to 30 or more minutes' HP: Fri Oct 24 00:59:54 UTC 2014 this could take up to 30 or more minutes ++ wait_for_stack_ready 720 10 overcloud Command output matched '(CREATE|UPDATE)_FAILED'. Exiting...
2014-10-26 10:19:38 -0500 asked a question Fail to start the overcloud in Helion virt

Hi All,

I installed Helion virt multiple times, and I got a same error:

OVERCLOUD_NEUTRON_DVR=False

OVERCLOUD_NTP_SERVER=16.110.135.123

UNDERCLOUD_NTP_SERVER=16.110.135.123

root@hLinux:~# bash -x /root/tripleo/tripleo-incubator/scripts/hp_ced_installer.sh

+--------------------------------------+------------+--------------------+----------------------+

| id | stack_name | stack_status | creation_time |

+--------------------------------------+------------+--------------------+----------------------+

| f533a67f-5eb2-44a6-ab48-66419b725a1a | overcloud | CREATE_IN_PROGRESS | 2014-10-23T05:34:58Z |

+--------------------------------------+------------+--------------------+----------------------+

++ echo 'Waiting for the overcloud stack to be ready'

Waiting for the overcloud stack to be ready

+++ date

++ echo 'HP: Thu Oct 23 05:35:09 UTC 2014 this could take up to 30 or more minutes'

HP: Thu Oct 23 05:35:09 UTC 2014 this could take up to 30 or more minutes

++ wait_for_stack_ready 720 10 overcloud

Command output matched '(CREATE|UPDATE)_FAILED'. Exiting...

Which means the overcloud is created fail.

And I also get the nova status:

root@hLinux:~# source ~root/tripleo/tripleo-undercloud-passwords

root@hLinux:~# TE_DATAFILE=tripleo/testenv.json

root@hLinux:~# source ~root/tripleo/tripleo-incubator/undercloudrc

root@hLinux:~# nova list

+--------------------------------------+--------------------------------------+--------+------------+-------------+---------------------+

| ID | Name | Status | Task State | Power State | Networks |

+--------------------------------------+--------------------------------------+--------+------------+-------------+---------------------+

| 0a491749-e61f-4a8f-b57a-6b71d3f5173d | overcloud-NovaCompute0-4lmc7ocyqy5u | ERROR | - | NOSTATE | |

| b4c8ae31-fc06-4160-b618-4e49e1bbb5db | overcloud-SwiftStorage0-oovx2zfqwewi | ERROR | - | NOSTATE | |

| 52c55285-582c-4125-8227-415a1508ff88 | overcloud-SwiftStorage1-duyqeac4mjks | ACTIVE | - | Running | ctlplane=192.0.2.23 |

| 5c5a685f-8ab0-49e9-b029-1e6477b71edc | overcloud-controller0-2cs7ed7haina | ACTIVE | - | Running | ctlplane=192.0.2.24 |

+--------------------------------------+--------------------------------------+--------+------------+-------------+---------------------+

I checked the over cloud controller logs:

root@overcloud-controller0-5nbbwkeu53cv:~# tail /var/log/upstart/os-collect-config.log

dib-run-parts Thu Oct 23 08:25:25 UTC 2014 51-hosts completed dib-run-parts Thu Oct 23 08:25:25 UTC 2014 Running /opt/stack/os-config-refresh/configure.d/51-mysql-init We are neither cluster initializer or joiner. Refusing to bootstrap mysql cluster until role is known. [2014-10-23 08:25:25,136] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/configure.d']' returned non-zero exit stat us 1]

ERROR:os-refresh-config:during configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/configure.d']' returned non-zero exit status 1]

[2014-10-23 08:25:25,136] (os-refresh-config) [ERROR] Aborting... ERROR:os-refresh-config:Aborting... 2014-10-23 08:25:25.140 1112 ERROR os-collect-config [-] Command failed, will not cache new data. Command 'os-refresh-config' returned non-zero exit status 1 2014-10-23 08:25:25.140 1112 WARNING os-collect-config [-] Sleeping 30.00 seconds before re-exec.

I have tried about 6 times includeing reinstall OS (Ubuntu 13.10), but it is still failed with same error in os-collect-config.log.

Can anybody help?

Is anything wrong?

Thanks in advance!

BoW

2014-10-26 10:19:36 -0500 asked a question Fail to start the overcloud in Helion virt

Hi All,

I installed Helion virt multiple times, and I got a same error:

OVERCLOUD_NEUTRON_DVR=False
OVERCLOUD_NTP_SERVER=16.110.135.123
UNDERCLOUD_NTP_SERVER=16.110.135.123

root@hLinux:~# bash -x /root/tripleo/tripleo-incubator/scripts/hp_ced_installer.sh

+--------------------------------------+------------+--------------------+----------------------+

| id                                   | stack_name | stack_status       | creation_time        |

+--------------------------------------+------------+--------------------+----------------------+

| f533a67f-5eb2-44a6-ab48-66419b725a1a | overcloud  | CREATE_IN_PROGRESS | 2014-10-23T05:34:58Z |

+--------------------------------------+------------+--------------------+----------------------+

++ echo 'Waiting for the overcloud stack to be ready'

Waiting for the overcloud stack to be ready

+++ date

++ echo 'HP: Thu Oct 23 05:35:09 UTC 2014 this could take up to 30 or more minutes'

HP: Thu Oct 23 05:35:09 UTC 2014 this could take up to 30 or more minutes

++ wait_for_stack_ready 720 10 overcloud

Command output matched '(CREATE|UPDATE)_FAILED'. Exiting...

Which means the overcloud is created fail.

And I also get the nova status:

root@hLinux:~# source ~root/tripleo/tripleo-undercloud-passwords

root@hLinux:~# TE_DATAFILE=tripleo/testenv.json

root@hLinux:~# source ~root/tripleo/tripleo-incubator/undercloudrc

root@hLinux:~# nova list

+--------------------------------------+--------------------------------------+--------+------------+-------------+---------------------+

| ID                                   | Name                                 | Status | Task State | Power State | Networks            |

+--------------------------------------+--------------------------------------+--------+------------+-------------+---------------------+

| 0a491749-e61f-4a8f-b57a-6b71d3f5173d | overcloud-NovaCompute0-4lmc7ocyqy5u  | ERROR  | -          | NOSTATE     |                     |

| b4c8ae31-fc06-4160-b618-4e49e1bbb5db | overcloud-SwiftStorage0-oovx2zfqwewi | ERROR  | -          | NOSTATE     |                     |

| 52c55285-582c-4125-8227-415a1508ff88 | overcloud-SwiftStorage1-duyqeac4mjks | ACTIVE | -          | Running     | ctlplane=192.0.2.23 |

| 5c5a685f-8ab0-49e9-b029-1e6477b71edc | overcloud-controller0-2cs7ed7haina   | ACTIVE | -          | Running     | ctlplane=192.0.2.24 |

+--------------------------------------+--------------------------------------+--------+------------+-------------+---------------------+

I checked the over cloud controller logs:

root@overcloud-controller0-5nbbwkeu53cv:~# tail /var/log/upstart/os-collect-config.log

dib-run-parts Thu Oct 23 08:25:25 UTC 2014 51-hosts completed
dib-run-parts Thu Oct 23 08:25:25 UTC 2014 Running /opt/stack/os-config-refresh/configure.d/51-mysql-init
We are neither cluster initializer or joiner. Refusing to bootstrap mysql cluster until role is known.
[2014-10-23 08:25:25,136] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/configure.d']' returned non-zero exit stat
us 1]

ERROR:os-refresh-config:during configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/configure.d']' returned non-zero exit status 1]

[2014-10-23 08:25:25,136] (os-refresh-config) [ERROR] Aborting...
ERROR:os-refresh-config:Aborting...
2014-10-23 08:25:25.140 1112 ERROR os-collect-config [-] Command failed, will not cache new data. Command 'os-refresh-config' returned non-zero exit status 1
2014-10-23 08:25:25.140 1112 WARNING os-collect-config [-] Sleeping 30.00 seconds before re-exec.

I tried about 6 times including reinstall OS (Ubuntu 13.10), but it is still failed with same error.

Can anybody help? Is anything wrong? Can anybody help?

Thanks in advance!

BoW