Comment 19 for bug 1318567

Revision history for this message
Kirill Omelchenko (komelchenko) wrote : Re: [systest] Node failed to get online state within allocated timeout after stopping deployment

One more reproduced on system tests:
http://jenkins-product.srt.mirantis.net:8080/view/0_master_swarm/job/master_fuelmain.system_test.ubuntu.thread_2/153/testReport/?

Scenario:
CentOS, Simple
1. Add 1x controller, 1x compute
2. Deploy
3. Wait for the progress to reach 10%
4. Stop deployment, wait for nodes to become ready for deployment
5. Add 1x cinder node
6. Deploy

Expected:
Nodes get provisioned and the cluster is set up.

Actual:
Controller node is offline in the UI and CLI:
[root@nailgun ~]# fuel node
id | status | name | cluster | ip | mac | roles | pending_roles | online
---|-------------|---------------------|---------|---------------|-------------------|------------|---------------|-------
1 | provisioned | slave-01_controller | 1 | 10.108.30.166 | 64:ca:a9:60:57:43 | controller | | False
2 | provisioned | slave-02_compute | 1 | 10.108.30.4 | 64:92:27:73:36:d4 | compute | | True
3 | provisioned | slave-03_cinder | 1 | 10.108.30.5 | 64:d7:1b:35:ef:98 | cinder | | True
[root@nailgun ~]# ping node-1
PING node-1.test.domain.local (10.108.30.3) 56(84) bytes of data.
64 bytes from node-1.test.domain.local (10.108.30.3): icmp_seq=1 ttl=64 time=0.308 ms
64 bytes from node-1.test.domain.local (10.108.30.3): icmp_seq=2 ttl=64 time=0.531 ms

In fact the node is in bootstrap state.
astute.log contains records http://paste.openstack.org/show/102416/
I assume they indicate that it either hasn't been rebooted or has been marked as bootstrap.