Ask Your Question

Abhi1988's profile - activity

2018-06-15 00:48:03 -0500 received badge  Enthusiast
2018-06-07 05:20:15 -0500 commented question Unable to launch an instance

Oh! Sorry about that confusion. We changed few things in the config files and later it was trying to allocate storage in compute node(slabnode1210). But this failed as there was no much space in the "/" partition of slabnode1210. Now everything is working fine! thanks a lot for your help!

2018-06-07 00:24:33 -0500 commented question Unable to launch an instance

Here, as seen in the log above, it is trying to find space in the "/" partition in the compute nodes.

2018-06-07 00:23:46 -0500 commented question Unable to launch an instance

2018-06-07 07:16:37.417 6976 DEBUG nova.scheduler.filters.disk_filter [req-415ffa17-ee20d - - -] (http://slabnode1210.netact.nsn-rdnet.net, http://slabnode1210.netact.nsn-rdnet.net) ram: 130303MB disk: 48128MB io_ops: 0 instances: 0 does not have 81920 MB usable disk space before overcommit, it only has 50176 MB.

2018-06-07 00:23:46 -0500 received badge  Commentator
2018-06-06 23:58:49 -0500 commented question Unable to launch an instance

Log from /var/log/nova/nova-conductor.log 2018-06-07 07:48:16.735 7127 WARNING nova.scheduler.utils [req-70399438-d6 - - -] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available.

2018-06-06 09:12:02 -0500 received badge  Famous Question (source)
2018-06-06 08:41:42 -0500 commented question Unable to launch an instance

This is actually related to the question. I am able to successfully deploy an instance of smaller size where the space is considered from the controller node's "/" storage. But an instance of larger size(larger than / size of controller node), it fails as said in the question.

2018-06-06 04:54:48 -0500 commented question Unable to launch an instance

And in lsblk output, not able to see any LVM mount points where it belongs to cinder group. Currently it belongs to controller node. And hence, considering storage space from controller node

2018-06-06 04:51:30 -0500 commented question Unable to launch an instance

Asso my another finding is that, there is no iscsi lun created for any volume I create [root@slabnode1202 ~]# targetcli

/iscsi> ls o- iscsi .............................................................................................................. [Targets: 0] /iscsi>

2018-06-06 04:49:37 -0500 commented question Unable to launch an instance

But the image still exists [root@slabnode1202 ~]# glance image-list +--------------------------------------+-------------------+ | ID | Name | +--------------------------------------+-------------------+ | 58d65160-453c-459b-8449-0839991f7906 | rhel7_in

2018-06-06 04:49:02 -0500 commented question Unable to launch an instance

The error message is as below when I did nove show for that instance.

image | Attempt to boot from volume - no image supplied

2018-06-06 02:30:09 -0500 commented question Unable to launch an instance

The problem is, whenever i am creating an instance, the space is not being taken from the external storage attached to the blade. But is being taken from the controller node's local storage. Don't know how to map the storage to consider external storage.

2018-06-06 02:29:50 -0500 commented question Unable to launch an instance

There is no problem in the authentication data. I double checked it.

2018-06-04 04:16:01 -0500 commented question Unable to launch an instance

Tried adding configuration details to nova.conf under keystone_authtoken section on that compute host. But still didn't help!

2018-06-02 22:21:36 -0500 received badge  Notable Question (source)
2018-06-01 16:11:45 -0500 received badge  Popular Question (source)
2018-06-01 05:36:57 -0500 asked a question Unable to launch an instance

Failing while creating an instance as below

2018-06-01 12:07:11.218 6800 ERROR nova.scheduler.utils [req-d7decb2e-b75f-4f73-8666-799badbb0e41 15f5b7bee619432880240dbbd5a42c89 98c2bf7cd43f4f108de86b6eee207ecd - - -] [instance: 334b80c0-ab52-4bfe-9947-63ca02b0897f] Error from last host: http://slabnode1210.netact.nsn-rdnet.net (node http://slabnode1210.netact.nsn-rdnet.net): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1787, in _do_build_and_run_instance\n filter_properties)\n', u' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1985, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance 334b80c0-ab52-4bfe-9947-63ca02b0897f was re-scheduled: The request you have made requires authentication. (HTTP 401) (Request-ID: req-a1969249-59f9-4173-b377-72e74cb5f813)\n']

Any idea on what kind of authentication it is asking for? There is already password-less authentication between all the compute nodes and the controller node back and fro.

2018-04-29 11:40:29 -0500 asked a question create instances using Heat failing

Hello everyone, I am trying to create instances using Heat but it is failing with the error

Resource CREATE failed: BadRequest: resources.nbi3gc_instance_0.resources.nbi3gc_server: Invalid volume: volume '563297f4-3a9e-4315-a0b0-6f1accb02172' status must be 'available'. Currently in 'in-use' (HTTP 400) (Request-ID: req-14be84d8-24c6-4dc7-b861-8f

Any clues?