|
2016-05-19 19:28:23 -0600
| received badge | ● Taxonomist
|
|
2015-09-20 19:26:58 -0600
| received badge | ● Famous Question
(source)
|
|
2015-05-27 07:41:55 -0600
| received badge | ● Student
(source)
|
|
2015-05-20 16:26:38 -0600
| received badge | ● Famous Question
(source)
|
|
2015-05-20 01:02:05 -0600
| received badge | ● Notable Question
(source)
|
|
2015-05-20 01:02:05 -0600
| received badge | ● Popular Question
(source)
|
|
2015-05-19 13:08:04 -0600
| asked a question | vm guest can ping first ip of floating ip range, but failed to ping gateway of floating ip Hi all,
I met a problem that my guest vm which is located under a tenant network, and it can ping the first range of floating ip successfully, but it failed to ping the gateway of floating ip. Host IP: 192.168.110.10
gateway: 192.168.110.254 I followed the section of initial network section of ubuntu installation guide to build the network, steps are following: neutron net-create ext-net --router:external \
--provider:physical_network external --provider:network_type flat
neutron subnet-create ext-net 192.168.110.0/24 --name ext-subnet \
--allocation-pool start=192.168.110.20,end=192.168.110.29 \
--disable-dhcp --gateway 192.168.110.254
neutron net-create admin-net
neutron subnet-create admin-net 192.168.1.0/24 \
--name admin-subnet --gateway 192.168.1.1
neutron router-create admin-router
neutron router-interface-add admin-router admin-subnet
neutron router-gateway-set admin-router ext-net
on the host side, I can ping the first ip of floating ip range which is 192.168.110.20 user@controller01:~$ ping 192.168.110.20
PING 192.168.110.20 (192.168.110.20) 56(84) bytes of data.
64 bytes from 192.168.110.20: icmp_seq=9 ttl=64 time=0.440 ms
64 bytes from 192.168.110.20: icmp_seq=10 ttl=64 time=0.071 ms
64 bytes from 192.168.110.20: icmp_seq=11 ttl=64 time=0.067 ms
64 bytes from 192.168.110.20: icmp_seq=12 ttl=64 time=0.091 ms
in the guest vm(ip:192.168.1.3) which is located under the tenant network whose ip ranage is 192.168.1.1-254, and 192.168.1.1 is the gateway of tenant network within the guest vm can ping 192.168.1.1, 192.168.110.10(which is br-ex ip) and 192.168.110.20(which is first ip of floating ip range
(sorry, I tried to copy the ping results from guest vm but failed) and the result of traceroute from guest vm to 192.168.110.254 traveled 2 hubs and then stopped at 192.168.110.20 - 192.168.1.1
- 192.168.110.20
how should I trace furthur into the issue? thanks for your patient to finish my question! |
|
2015-05-16 18:22:35 -0600
| received badge | ● Notable Question
(source)
|
|
2015-05-16 18:12:10 -0600
| received badge | ● Scholar
(source)
|
|
2015-05-16 09:02:53 -0600
| received badge | ● Popular Question
(source)
|
|
2015-05-15 09:48:02 -0600
| asked a question | [neutron]Failed to find some config files: /etc/neutron/plugins_conf.ini Hi All,
I was trying to install neutron from github stable/kilo
and after finished installation, in /var/log/upstart/neutron-server.log it said Traceback (most recent call last):
File "/usr/local/bin/neutron-server", line 10, in <module>
sys.exit(main())
File "/home/cube01/github/neutron/neutron/cmd/eventlet/server/__init__.py", line 17, in main
server.main()
File "/home/cube01/github/neutron/neutron/server/__init__.py", line 36, in main
config.init(sys.argv[1:])
File "/home/cube01/github/neutron/neutron/common/config.py", line 185, in init
**kwargs)
File "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 1853, in __call__
raise ConfigFilesNotFoundError(self._namespace._files_not_found)
oslo_config.cfg.ConfigFilesNotFoundError: Failed to find some config files: /etc/neutron/plugins_conf.ini
and neutron-server was not starting successfully until I touched /etc/neutron/plugins_conf.ini I've checked neutron's github repository, in etc folder, there's no plugins_conf.ini or plugins_conf.ini.sample does anyone know what this plugins_conf.ini come from and what is it for?
thanks! |
|
2015-05-11 18:08:57 -0600
| received badge | ● Enthusiast
|
|
2015-05-09 01:40:43 -0600
| received badge | ● Famous Question
(source)
|
|
2015-05-06 18:07:54 -0600
| received badge | ● Notable Question
(source)
|
|
2015-05-02 11:12:16 -0600
| received badge | ● Popular Question
(source)
|
|
2015-04-30 19:56:34 -0600
| commented question | [kilo]Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available by the way, my ubuntu version is 14.04.1 |
|
2015-04-30 19:18:47 -0600
| received badge | ● Editor
(source)
|
|
2015-04-30 19:16:14 -0600
| asked a question | [kilo]Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available Hi All, I was trying to create instance on kilo and met this error. in control node, /var/log/nova/nova-conductor.log
it said: 2015-05-01 07:03:27.837 1742 WARNING nova.scheduler.utils [req-853c7c96-ce99-42a8-8b8b-7d0d2bc61835 17d55b88b52948b9a9eb64abbef51142 de39e7f8 aeea4461813e90cdbd1fc064 - -
-] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available. Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 142, in inner
return func(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/nova/scheduler/manager.py", line 86, in select_destinations
filter_properties)
File "/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py", line 80, in select_destinations
raise exception.NoValidHost(reason=reason)
NoValidHost: No valid host was found. There are not enough hosts available.
2015-05-01 07:03:27.838 1742 WARNING nova.scheduler.utils [req-853c7c96-ce99-42a8-8b8b-7d0d2bc61835 17d55b88b52948b9a9eb64abbef51142 de39e7f8 aeea4461813e90cdbd1fc064 - -
-] [instance: bdc8048c-646b-4df7-8780-6084b254d87a] Setting instance to ERROR state.
and
in compute node, /var/log/nova/nova-compute.log
it said: 2015-05-01 07:03:31.240 1909 INFO nova.compute.claims [-] [instance: bdc8048c-646b-4df7-8780-6084b254d87a] Total disk: 38 GB, used: 0.00 GB
2015-05-01 07:03:33.482 1909 TRACE nova.compute.manager [instance: bdc8048c-646b-4df7-8780-6084b254d87a] Traceback (most recent call last):
2015-05-01 07:03:31.240 1909 INFO nova.compute.claims [-] [instance: bdc8048c-646b-4df7-8780-6084b254d87a] Total disk: 38 GB, used: 0.00 GB
2015-05-01 07:03:31.240 1909 INFO nova.compute.claims [-] [instance: bdc8048c-646b-4df7-8780-6084b254d87a] disk limit not specified, defaulti
ng to unlimited
2015-05-01 07:03:31.317 1909 INFO nova.compute.claims [-] [instance: bdc8048c-646b-4df7-8780-6084b254d87a] Claim successful
2015-05-01 07:03:31.446 1909 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-05-01 07:03:31.647 1909 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-05-01 07:03:31.986 1909 INFO nova.virt.libvirt.driver [req-ed1023af-7702-453b-bfba-b2d5fde0029b - - - - -] [instance: bdc8048c-646b-4df7
-8780-6084b254d87a] Creating image
2015-05-01 07:03:32.404 1909 INFO nova.scheduler.client.report [-] Compute_service record updated for ('compute1', 'compute1')
2015-05-01 07:03:32.769 1909 INFO nova.virt.disk.vfs.api [req-ed1023af-7702-453b-bfba-b2d5fde0029b - - - - -] Unable to import guestfs, falli
ng back to VFSLocalFS
2015-05-01 07:03:33.482 1909 ERROR nova.compute.manager [req-ed1023af-7702-453b-bfba-b2d5fde0029b - - - - -] [instance: bdc8048c-646b-4df7-87
80-6084b254d87a] Instance failed to spawn
2015-05-01 07:03:33.482 1909 TRACE nova.compute.manager [instance: bdc8048c-646b-4df7-8780-6084b254d87a] Traceback (most recent call last):
2015-05-01 07:03:33.482 1909 TRACE nova.compute.manager [instance: bdc8048c-646b-4df7-8780-6084b254d87a] File "/usr/lib/python2.7/dist-pack
ages/nova/compute/manager.py", line 2438, in _build_resources
2015-05-01 07:03:33.482 1909 TRACE nova.compute.manager [instance: bdc8048c-646b-4df7-8780-6084b254d87a] yield resources
2015-05-01 07:03:33.482 1909 TRACE nova.compute.manager [instance: bdc8048c-646b-4df7-8780-6084b254d87a] File "/usr/lib/python2.7/dist-pack
ages/nova/compute/manager.py", line 2310, in _build_and_run_instance
2015-05-01 07:03:33.482 1909 TRACE nova.compute.manager [instance: bdc8048c-646b-4df7-8780-6084b254d87a] block_device_info=block_device_i
nfo)
2015-05-01 07:03:33.482 1909 TRACE nova.compute.manager [instance: bdc8048c-646b-4df7-8780-6084b254d87a] File "/usr/lib/python2.7/dist-pack
ages/nova/virt/libvirt/driver.py", line 2351, in spawn
2015-05-01 07:03:33.482 1909 TRACE nova.compute.manager [instance: bdc8048c-646b-4df7-8780-6084b254d87a] write_to_disk=True)
2015-05-01 07:03:33.482 1909 ...
(more) |
|
2015-04-15 05:41:51 -0600
| commented question | Error: Unable to connect to Neutron by the way, my version is git/horizon origin/stable/icehouse, thanks! |
|
2015-04-15 05:17:56 -0600
| commented question | Error: Unable to connect to Neutron and I follow the class under openstack_dashboard/neutron.py and openstack_dashboard/network_base.py and there's no method called "is_supported" under class FloatingIpManager in both neutron.py and network_base.py is it possible that is_supported method is removed by accident? |
|
2015-04-15 05:13:04 -0600
| commented question | Error: Unable to connect to Neutron it happend to me too! this error message comes up when there's instance in the instance list.
and I went to openstack_dashboard/neutron.py which is located under horizon folder and found
fips.is_supported():
triggerred the exception and
error_message = _('Unable to connect to Neutron.') shown up |
|
2015-04-14 16:53:37 -0600
| answered a question | Error: Unable to connect to Neutron it happend to me too! this error message comes up when there's instance in the instance list. |
