Ask Your Question

scampo's profile - activity

2019-01-29 10:02:37 -0500 received badge  Popular Question (source)
2018-04-16 03:51:21 -0500 received badge  Famous Question (source)
2018-03-06 04:13:55 -0500 commented answer Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

Sorry @Bernd Bausch, but I needed to use a shorter node name to respect the comment maximum lenght limitation. I am sure that the hostname is not the root of the problem, it is correct.

2018-03-05 11:31:07 -0500 commented answer Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

It seems that n-cpu wasn't successful in registering the host. Is it correct? What can I do? Thanks!

2018-03-05 11:31:07 -0500 received badge  Commentator
2018-03-05 11:27:19 -0500 commented answer Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

n-cpu log

node.node nova-compute[19161]: WARNING nova.virt.libvirt.driver [None
req-162330c2-9062-4505-8fa7-54c1b0993a43 None None] Cannot update service status on host
node.node" since it is not registered.: ComputeHostNotFound_Remote: 
Compute host node.node could not be found.
2018-03-05 11:16:13 -0500 commented answer Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

I also tried to check the status and the logs of devstack@n-cpu and devstack@placement-api. I hope to answer to your first question pasting a piece of n-cpu logs in the next comment.

2018-03-05 11:03:59 -0500 commented answer Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

Then, I tried to look into the databases, but without success. To more clearify: I looked into resource_provider table for each of these databases: nova-api, nova_cell0 and nova_cell1. But all tables are empty!

2018-03-05 10:56:11 -0500 commented answer Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

Hi @Bernd Bausch

I tried to launch the nova-status upgrade check getting the expected result that you shown previously.

2018-02-28 04:52:37 -0500 received badge  Scholar (source)
2018-02-28 04:51:56 -0500 commented answer Openstack metadata - Why I am not able to access to the metadata?

Thank you @doka.ua !

The problem was that I was not trying to access metadata in the correct way. I tried from Controller Node and Compute Node before starting VMs, obtaining the initial error.

Thank you very much

2018-02-28 03:02:11 -0500 received badge  Famous Question (source)
2018-02-27 22:43:09 -0500 received badge  Notable Question (source)
2018-02-27 22:43:04 -0500 received badge  Famous Question (source)
2018-02-27 11:41:18 -0500 edited question Error during OpenStack installation: ./stack.sh:exit_trap:539 echo 'Error on exit'

I am new to OpenStack. While installing devstack on my Ubuntu 16.04 VM, during the execution of

./stack.sh

I got the following error:

+lib/etcd3:install_etcd3:121               echo ' /opt/stack/devstack/files/etcd-v3.1.7-linux-arm64.tar.gz'
+lib/etcd3:install_etcd3:123               sha256sum -c /opt/stack/devstack/files/etcd.sha256sum
sha256sum: /opt/stack/devstack/files/etcd.sha256sum: no properly formatted SHA256 checksum lines found
+lib/etcd3:install_etcd3:1                 exit_trap
+./stack.sh:exit_trap:521                  local r=1
++./stack.sh:exit_trap:522                  jobs -p
+./stack.sh:exit_trap:522                  jobs=
+./stack.sh:exit_trap:525                  [[ -n '' ]]
+./stack.sh:exit_trap:531                  '[' -f '' ']'
+./stack.sh:exit_trap:536                  kill_spinner
+./stack.sh:kill_spinner:417               '[' '!' -z '' ']'
+./stack.sh:exit_trap:538                  [[ 1 -ne 0 ]]
+./stack.sh:exit_trap:539                  echo 'Error on exit'
Error on exit
+./stack.sh:exit_trap:540                  generate-subunit 1517844452 85 fail
+./stack.sh:exit_trap:541                  [[ -z /opt/stack/logs ]]
+./stack.sh:exit_trap:544                  /opt/stack/devstack/tools/worlddump.py -d /opt/stack/logs
World dumping... see /opt/stack/logs/worlddump-2018-02-05-152857.txt for details
+./stack.sh:exit_trap:550                  exit 1

I also checked the worlddump file, but I didn't see nothing strange, in my opinion.

I strictly followed the steps described in the devstack openstack guide.

Any tips, please? Thanks!

2018-02-27 11:39:38 -0500 received badge  Popular Question (source)
2018-02-27 11:24:28 -0500 answered a question Openstack metadata - Why I am not able to access to the metadata?

Thank you @doka.ua !

The problem was that I was not trying to access metadata in the correct way. I tried from Controller Node and Compute Node before starting VMs, obtaining the initial error.

Thank you very much

2018-02-27 10:49:21 -0500 answered a question Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

Hi @Bernd Bausch

I set virt_type to qemu value as you suggested.

I restarted the nova compute services and I tried to create a new instance with the same error.

I found the log and I paste a little bit sequence here:

Feb 27 09:36:08 node devstack@n-api.service[959]: Tue Feb 27 09:36:08 2018 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /compute/v2.1/flavors/m1.small (ip 12.12.12.12) !!!
Feb 27 09:36:08 node devstack@n-api.service[959]: Tue Feb 27 09:36:08 2018 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /compute/v2.1/flavors/m1.small (ip 12.12.12.12) !!!
Feb 27 09:36:08 node devstack@n-api.service[959]: #033[00;36mINFO nova.api.openstack.wsgi [#033[01;36mNone req-b3f9c7aa-2881-4777-a043-3cd8a451a7f0 #033[00;36mdemo admin#033[00;36m] #033[01;35m#033[00;36mHTTP exception thrown: Flavor m1.small could not be found.#033[00m
Feb 27 09:36:08 node devstack@n-api.service[959]: #033[00;32mDEBUG nova.api.openstack.wsgi [#033[01;36mNone req-b3f9c7aa-2881-4777-a043-3cd8a451a7f0 #033[00;36mdemo admin#033[00;32m] #033[01;35m#033[00;32mReturning 404 to user: Flavor m1.small could not be found.#033[00m #033[00;33m{{(pid=988) __call__ /opt/stack/nova/nova/api/openstack/wsgi.py:1029}}#033[00m

I got those messages several times. After I got also:

Feb 27 09:36:10 node devstack@keystone.service[918]: #033[00;32mDEBUG keystone.middleware.auth [#033[01;36mNone req-709db444-27c3-4e33-af86-9a1de2b52532 #033[00;36mNone None#033[00;32m] #033[01;35m#033[00;32mAuthenticating user token#033[00m #033[00;33m{{(pid=931) process_request /usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py:400}}#033[00m
Feb 27 09:36:10 node nova-conductor[957]: #033[01;31mERROR nova.conductor.manager [#033[01;36mNone req-92bfafc4-5781-442c-ba51-e9bcf3b5520b #033[00;36mdemo admin#033[01;31m] #033[01;35m#033[01;31mFailed to schedule instances#033[00m: NoValidHost_Remote: No valid host was found.
Feb 27 09:36:10 node nova-conductor[957]: Traceback (most recent call last):
Feb 27 09:36:10 node nova-conductor[957]:   File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 232, in inner
Feb 27 09:36:10 node nova-conductor[957]:     return func(*args, **kwargs)
Feb 27 09:36:10 node nova-conductor[957]:   File "/opt/stack/nova/nova/scheduler/manager.py", line 137, in select_destinations
Feb 27 09:36:10 node nova-conductor[957]:     raise exception.NoValidHost(reason="")
Feb 27 09:36:10 node nova-conductor[957]: NoValidHost: No valid host was found.
Feb 27 09:36:10 node nova-conductor[957]: ERROR nova.conductor.manager #033[01;35m#033[00mTraceback (most recent call last):
Feb 27 09:36:10 node nova-conductor[957]: ERROR nova.conductor.manager #033[01;35m#033[00m  File "/opt/stack/nova/nova/conductor/manager.py", line 1049, in schedule_and_build_instances
Feb 27 09:36:10 node nova-conductor[957]: ERROR nova.conductor.manager #033[01 ...
(more)
2018-02-26 03:03:26 -0500 received badge  Notable Question (source)
2018-02-25 09:47:17 -0500 received badge  Notable Question (source)
2018-02-24 05:48:24 -0500 received badge  Student (source)
2018-02-21 19:28:50 -0500 received badge  Popular Question (source)
2018-02-21 08:57:32 -0500 commented answer Openstack metadata - Why I am not able to access to the metadata?

Thank you! I'll give you a feedback asap!

2018-02-21 08:56:40 -0500 received badge  Popular Question (source)
2018-02-20 10:04:32 -0500 asked a question Openstack metadata - Why I am not able to access to the metadata?

Hi all,

I'm new to Openstack metadata services and I'm trying to play with them.

I am working with Mitaka. As suggested in the official documentation (https://docs.openstack.org/nova/latest/admin/networking-nova.html#metadata-service (https://docs.openstack.org/nova/lates...)) I checked my nova.conf file and I successfully tried to curl as shown below:

curl http://192.168.1.1:8775
1.0
2007-01-19
2007-03-01
..........

The problem occured when I tried to access the other subdirectories.

For Instance, if I try to make a curl asking the metadata in 2007-01-19 , I get the a 400 Bad Request error.

Why? Any tips?

Thank you!

2018-02-20 08:34:05 -0500 commented question Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

Thank you! I'll give you a feedback asap!

2018-02-20 04:33:07 -0500 commented answer No valid host was found. There are not enough hosts available.

I've already checked the amount of memory or disk space. Fortunately it is enough. Now, I am going to check the log files.

2018-02-20 04:31:25 -0500 commented answer No valid host was found. There are not enough hosts available.

Thanks for the suggestions! I reposted my question here https://ask.openstack.org/en/question/112654/devstack-no-valid-host-was-found-there-are-not-enough-hosts-available-code-500-failure-checking-if-device-devkvm-is-accessible/ (https://ask.openstack.org/en/question...)

2018-02-20 04:23:32 -0500 asked a question Devstack - No valid host was found. There are not enough hosts available. - code 500 - Failure Checking if device /dev/kvm is accessible

Hi all, (I repost my question here as new) I got this error while I was working with DEVSTACK.

I successfully installed Devstack based on the latest stable version (Pike) and when i tried to launch an instance I got the error message "message: No valid host was found. There are not enough hosts available. code: 500".

I tried to execute the virt-host-validate command with the result shown below:

:~$ virt-host-validate
QEMU: Checking for hardware virtualization                                 : PASS
QEMU: Checking if device /dev/kvm exists                                   : PASS
QEMU: Checking if device /dev/kvm is accessible                            : FAIL (Check /dev/kvm is world writable or you are in a group that is allowed to access it)
QEMU: Checking if device /dev/vhost-net exists                             : PASS
QEMU: Checking if device /dev/net/tun exists                               : PASS
QEMU: Checking for cgroup 'memory' controller support                      : PASS
QEMU: Checking for cgroup 'memory' controller mount-point                  : PASS
QEMU: Checking for cgroup 'cpu' controller support                         : PASS
QEMU: Checking for cgroup 'cpu' controller mount-point                     : PASS
QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
QEMU: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
QEMU: Checking for cgroup 'cpuset' controller mount-point                  : PASS
QEMU: Checking for cgroup 'devices' controller support                     : PASS
QEMU: Checking for cgroup 'devices' controller mount-point                 : PASS
QEMU: Checking for cgroup 'blkio' controller support                       : PASS
QEMU: Checking for cgroup 'blkio' controller mount-point                   : PASS
QEMU: Checking for device assignment IOMMU support                         : PASS
QEMU: Checking if IOMMU is enabled by kernel                               : WARN (IOMMU appears to be disabled in kernel. Add intel_iommu=on to kernel cmdline arguments)
LXC: Checking for Linux >= 2.6.26                                         : PASS
LXC: Checking for namespace ipc                                           : PASS
LXC: Checking for namespace mnt                                           : PASS
LXC: Checking for namespace pid                                           : PASS
LXC: Checking for namespace uts                                           : PASS
LXC: Checking for namespace net                                           : PASS
LXC: Checking for namespace user                                          : PASS
LXC: Checking for cgroup 'memory' controller support                      : PASS
LXC: Checking for cgroup 'memory' controller mount-point                  : PASS
LXC: Checking for cgroup 'cpu' controller support                         : PASS
LXC: Checking for cgroup 'cpu' controller mount-point                     : PASS
LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
LXC: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
LXC: Checking for cgroup 'cpuset' controller support                      : PASS
LXC: Checking for cgroup 'cpuset' controller mount-point                  : PASS
LXC: Checking for cgroup 'devices' controller support                     : PASS
LXC: Checking for cgroup 'devices' controller mount-point                 : PASS
LXC: Checking for cgroup 'blkio' controller support                       : PASS
LXC: Checking for cgroup 'blkio' controller mount-point                   : PASS

Any tips to solve the failure got while "Checking if device /dev/kvm is accessible"?

I tried, without success, following the tips in this page "https://help.ubuntu.com/community/KVM/Installation" and in this question "https://ask.openstack.org/en/question/92701/no-valid-host-was-found-there-are-not-enough-hosts-available"

Thanks

2018-02-19 09:08:30 -0500 answered a question No valid host was found. There are not enough hosts available.

Hi all,

I got this error while I was working with DEVSTACK.

I successfully installed Devstack based on the latest stable version (Pike) and when i tried to launch an instance I got the error message "message: No valid host was found. There are not enough hosts available. code: 500".

I tried to execute the virt-host-validate command with the result shown below:

:~$ virt-host-validate
QEMU: Checking for hardware virtualization                                 : PASS
QEMU: Checking if device /dev/kvm exists                                   : PASS
QEMU: Checking if device /dev/kvm is accessible                            : FAIL (Check /dev/kvm is world writable or you are in a group that is allowed to access it)
QEMU: Checking if device /dev/vhost-net exists                             : PASS
QEMU: Checking if device /dev/net/tun exists                               : PASS
QEMU: Checking for cgroup 'memory' controller support                      : PASS
QEMU: Checking for cgroup 'memory' controller mount-point                  : PASS
QEMU: Checking for cgroup 'cpu' controller support                         : PASS
QEMU: Checking for cgroup 'cpu' controller mount-point                     : PASS
QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
QEMU: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
QEMU: Checking for cgroup 'cpuset' controller mount-point                  : PASS
QEMU: Checking for cgroup 'devices' controller support                     : PASS
QEMU: Checking for cgroup 'devices' controller mount-point                 : PASS
QEMU: Checking for cgroup 'blkio' controller support                       : PASS
QEMU: Checking for cgroup 'blkio' controller mount-point                   : PASS
QEMU: Checking for device assignment IOMMU support                         : PASS
QEMU: Checking if IOMMU is enabled by kernel                               : WARN (IOMMU appears to be disabled in kernel. Add intel_iommu=on to kernel cmdline arguments)
LXC: Checking for Linux >= 2.6.26                                         : PASS
LXC: Checking for namespace ipc                                           : PASS
LXC: Checking for namespace mnt                                           : PASS
LXC: Checking for namespace pid                                           : PASS
LXC: Checking for namespace uts                                           : PASS
LXC: Checking for namespace net                                           : PASS
LXC: Checking for namespace user                                          : PASS
LXC: Checking for cgroup 'memory' controller support                      : PASS
LXC: Checking for cgroup 'memory' controller mount-point                  : PASS
LXC: Checking for cgroup 'cpu' controller support                         : PASS
LXC: Checking for cgroup 'cpu' controller mount-point                     : PASS
LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
LXC: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
LXC: Checking for cgroup 'cpuset' controller support                      : PASS
LXC: Checking for cgroup 'cpuset' controller mount-point                  : PASS
LXC: Checking for cgroup 'devices' controller support                     : PASS
LXC: Checking for cgroup 'devices' controller mount-point                 : PASS
LXC: Checking for cgroup 'blkio' controller support                       : PASS
LXC: Checking for cgroup 'blkio' controller mount-point                   : PASS

Any tips to solve the failure got while "Checking if device /dev/kvm is accessible"?

I tried, without success, following the tips in this page: https://help.ubuntu.com/community/KVM/Installation (https://help.ubuntu.com/community/KVM...).

Thanks

2018-02-13 11:49:46 -0500 received badge  Notable Question (source)
2018-02-08 15:18:16 -0500 received badge  Popular Question (source)
2018-02-02 07:41:16 -0500 received badge  Editor (source)
2018-02-02 06:42:45 -0500 asked a question OpenStack: Do I need to ensure OpenStack network state is clean before integrate OpenContrail with an existing Openstack?

I'm trying to integrate OpenContrail as SDN Controller with an existing OpenStack installation.

Before this choice i also read the OpenDaylight project documentation for the ODL Installation on an existing OpenStack. I learnt that, before the installation, I should ensure OpenStack network state is clean.

OpenContrail documentation doesn't refer to this kind of requirements.

The question is: Do I need to ensure OpenStack network state is clean before integrate OpenContrail with an existing Openstack?

2018-02-01 04:06:05 -0500 received badge  Supporter (source)
2018-02-01 03:36:20 -0500 received badge  Enthusiast
2018-01-30 09:59:51 -0500 asked a question OpenStack:What is the difference between using “CLI to the OpenStack APIs” and the separate APIs of the components?

What is the difference between:

  • using "the Command-line interface to the OpenStack APIs" through the command "openstack"

and

  • using the separate APIs of the different components (for example using the command-line interface to the Neutron APIs directly)?

Advantages and disadvantages?