r4.0.2.0 newton provision is stuck at openstack node

Bug #1722961 reported by wenqing liang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
New
High
Dheeraj Gautam
R4.0
New
High
Dheeraj Gautam

Bug Description

R4.0.2.0-80 newton provision sometimes get stuck at openstack node. Another provision of the same version went thru fine.

            "provision_role_sequence": "{'completed': [(u'server3', 'keepalived', '2017_10_10__23_24_49'), (u'server2', 'keepalived', '2017_10_10__23_24_49'), (u'server1', 'keepalived', '2017_10_10__23_39_03'), (u'server3', 'haproxy', '2017_10_10__23_39_30'), (u'server2', 'haproxy', '2017_10_10__23_39_32'), (u'server1', 'haproxy', '2017_10_10__23_40_59'), (u'server2', 'openstack', '2017_10_11__02_25_50'), (u'server3', 'openstack', '2017_10_11__02_26_47')], 'steps': [[(u'server1', u'openstack')], [(u'server1', u'pre_exec_vnc_galera')], [(u'server3', u'pre_exec_vnc_galera')], [(u'server2', u'pre_exec_vnc_galera')], [(u'server1', u'post_exec_vnc_galera')], [(u'server3', u'post_exec_vnc_galera')], [(u'server2', u'post_exec_vnc_galera')], [(u'server1', 'post_provision'), (u'server2', 'post_provision'), (u'server3', 'post_provision')]]}",

Oct 11 06:33:34 server1 systemd[1]: nova-scheduler.service: Main process exited, code=exited, status=1/FAILURE
Oct 11 06:33:34 server1 systemd[1]: nova-scheduler.service: Unit entered failed state.
Oct 11 06:33:34 server1 systemd[1]: nova-scheduler.service: Failed with result 'exit-code'.
Oct 11 06:33:34 server1 systemd[1]: nova-scheduler.service: Service hold-off time over, scheduling restart.
Oct 11 06:33:34 server1 systemd[1]: cinder-api.service: Main process exited, code=exited, status=1/FAILURE
Oct 11 06:33:34 server1 systemd[1]: cinder-api.service: Unit entered failed state.
Oct 11 06:33:34 server1 systemd[1]: cinder-api.service: Failed with result 'exit-code'.
Oct 11 06:33:34 server1 systemd[1]: Stopped OpenStack Compute Scheduler.
Oct 11 06:33:34 server1 systemd[1]: Starting OpenStack Compute Scheduler...
Oct 11 06:33:34 server1 systemd[1]: Started OpenStack Compute Scheduler.
Oct 11 06:33:34 server1 systemd[1]: cinder-api.service: Service hold-off time over, scheduling restart.
Oct 11 06:33:34 server1 systemd[1]: Stopped OpenStack Cinder Api.
Oct 11 06:33:34 server1 systemd[1]: Starting OpenStack Cinder Api...
Oct 11 06:33:34 server1 systemd[1]: Started OpenStack Cinder Api.
Oct 11 06:33:34 server1 cinder-scheduler[30499]: Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future.
Oct 11 06:33:35 server1 systemd[1]: cinder-scheduler.service: Main process exited, code=exited, status=1/FAILURE
Oct 11 06:33:35 server1 systemd[1]: cinder-scheduler.service: Unit entered failed state.
Oct 11 06:33:35 server1 systemd[1]: cinder-scheduler.service: Failed with result 'exit-code'.
Oct 11 06:33:35 server1 systemd[1]: cinder-scheduler.service: Service hold-off time over, scheduling restart.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.