Hi Vikas, It looks like the iscsi deploy process wasn't able to attach to the node. This could be a network issue.
Also, what kernel and ramdisk are you using for the deploy step? Did you download one, or build it with disk-image-builder? cirros is only suitable for the instance image, not the deploy. Regards, -Deva On Jul 29, 2015 5:56 PM, "Vikas Choudhary" <choudharyvika...@gmail.com> wrote: > Hi, > I am trying to boot an instance using pxe deployment process.I am using > cirros-0.3.4-x86_64-uec image to boot the baremetal server VM.ramdisk and > kernel images are being deployed successfully , but at kernel > initialization time its getting stuck there.In console logs I can see that > tgtd daemon is failing. > > CONSOLE LOGS: > Jul 29 23:17:18 (none) daemon.warn tgtd: tgtd logger started, pid:219 > debug:0^M > waiting for tgtd socket...found^M > Jul 29 23:17:19 (none) daemon.err tgtd: iser_ib_init(3351) Failed to > initialize RDMA; load kernel modules?^M > Jul 29 23:17:19 (none) daemon.err tgtd: work_timer_start(150) use signal > based scheduler^M > Jul 29 23:17:19 (none) daemon.err tgtd: bs_init_signalfd(271) could not > open backing-store module directory /usr/lib/tgt/backing-store > > ir-cond logs: > > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base [-] vendor_passthru > failed with method pass_deploy_info > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base Traceback (most > recent call last): > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base File > "/opt/stack/ironic/ironic/drivers/base.py", line 614, in passthru_handler > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base return > func(*args, **kwargs) > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base File > "/opt/stack/ironic/ironic/conductor/task_manager.py", line 129, in wrapper > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base return f(*args, > **kwargs) > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base File > "/opt/stack/ironic/ironic/drivers/modules/iscsi_deploy.py", line 815, in > pass_deploy_info > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base > uuid_dict_returned = continue_deploy(task, **kwargs) > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base File > "/opt/stack/ironic/ironic/drivers/modules/iscsi_deploy.py", line 392, in > continue_deploy > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base > _fail_deploy(task, msg) > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base File > "/opt/stack/ironic/ironic/drivers/modules/iscsi_deploy.py", line 365, in > _fail_deploy > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base raise exception. > InstanceDeployFailure(msg) > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base > InstanceDeployFailure: Deploy failed for instance > 42c3dea0-1f08-44f6-a38a-e6bd16d1212a. > Error: Unexpected error while running command. > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base Command: sudo > ironic-rootwrap /etc/ironic/rootwrap.conf iscsiadm -m discovery -t st -p > 50.0.0.10:3260 > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base Exit code: 4 > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base Stdout: u'' > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base Stderr: u'iscsiadm: > connect to 50.0.0.10 timed out\niscsiadm: connect to 50.0.0.10 timed > out\niscsiadm: connect to 50.0.0.10 timed out\niscsiadm: connect to > 50.0.0.10 timed out\niscsiadm: connect to 50.0.0.10 timed out\niscsiadm: > connect to 50.0.0.10 timed out\niscsiadm: connection login retries > (reopen_max) 5 exceeded\niscsiadm: Could not perform SendTargets discovery: > encountered connection failure\n' > 2015-07-30 04:55:47.095 355 ERROR ironic.drivers.base > 2015-07-30 04:55:47.217 355 DEBUG ironic.conductor.task_manager [-] > Successfully released exclusive lock for calling vendor passthru on node > ac0a1e31-2545-4d26-988a-56134584721e (lock was held 496.37 sec) > release_resources /opt/stack/ironic/ironic/conductor/task_manager.py:305 > > I would really appreciate any help/discussion/pointers.Please suggest. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev