Ask Your Question

lohg001's profile - activity

2018-09-04 00:52:26 -0500 received badge  Famous Question (source)
2017-08-22 09:34:52 -0500 received badge  Notable Question (source)
2017-08-22 09:34:52 -0500 received badge  Popular Question (source)
2017-04-03 08:46:47 -0500 received badge  Famous Question (source)
2017-03-09 08:03:34 -0500 received badge  Notable Question (source)
2017-03-09 08:03:34 -0500 received badge  Popular Question (source)
2017-01-09 01:19:00 -0500 received badge  Enthusiast
2017-01-05 03:20:19 -0500 asked a question Openstack Controller Mitaka and HyperV Compute node

Hi All,

I have a setup 1. Centos 7.3 with Openstack Mitaka as a (Controller) 2. Windows Server 2012 R2 with Cloudbase HyperVNovaComputeMitaka as a (Compute Node)

When I run instance into the compute node the creation is ok but after spawning the new instance I got this error (Instance failed network setup after 1 attempt(s)).

Here's the sample nova-compute log

2017-01-05 16:56:19.539 3924 INFO oslo_service.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2017-01-05 16:56:19.555 3924 INFO nova.virt.driver [-] Loading compute driver 'nova.virt.hyperv.driver.HyperVDriver'
2017-01-05 16:56:19.946 3924 INFO nova.service [-] Starting compute node (version 13.0.0)
2017-01-05 16:56:20.414 3924 WARNING nova.compute.monitors [req-394f6878-b577-4986-8f71-e9d04d97b516 - - - - -] Excluding nova.compute.monitors.cpu monitor virt_driver. Not in the list of enabled monitors (CONF.compute_monitors).
2017-01-05 16:56:20.430 3924 INFO nova.compute.resource_tracker [req-394f6878-b577-4986-8f71-e9d04d97b516 - - - - -] Auditing locally available compute resources for node HYPERV-M16
2017-01-05 16:56:20.617 3924 INFO nova.compute.resource_tracker [req-394f6878-b577-4986-8f71-e9d04d97b516 - - - - -] Total usable vcpus: 8, total allocated vcpus: 0
2017-01-05 16:56:20.617 3924 INFO nova.compute.resource_tracker [req-394f6878-b577-4986-8f71-e9d04d97b516 - - - - -] Final resource view: name=HYPERV-M16 phys_ram=32765MB used_ram=512MB phys_disk=546GB used_disk=0GB total_vcpus=8 used_vcpus=0 pci_stats=[]
2017-01-05 16:56:20.648 3924 INFO nova.compute.resource_tracker [req-394f6878-b577-4986-8f71-e9d04d97b516 - - - - -] Compute_service record updated for HYPERV-M16:HYPERV-M16
2017-01-05 16:56:50.792 3924 WARNING nova.compute.manager [req-b81baed6-31f5-458b-8401-4cee9509403d - - - - -] While synchronizing instance power states, found 0 instances in the database and 3 instances on the hypervisor.
2017-01-05 16:57:04.786 3924 INFO nova.compute.claims [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] Attempting claim: memory 2024 MB, disk 10 GB, vcpus 3 CPU
2017-01-05 16:57:04.801 3924 INFO nova.compute.claims [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] Total memory: 32765 MB, used: 512.00 MB
2017-01-05 16:57:04.816 3924 INFO nova.compute.claims [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] memory limit: 49147.50 MB, free: 48635.50 MB
2017-01-05 16:57:04.816 3924 INFO nova.compute.claims [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] Total disk: 546 GB, used: 0.00 GB
2017-01-05 16:57:04.816 3924 INFO nova.compute.claims [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] disk limit not specified, defaulting to unlimited
2017-01-05 16:57:04.816 3924 INFO nova.compute.claims [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] Total vcpu: 8 VCPU, used: 0.00 VCPU
2017-01-05 16:57:04.816 3924 INFO nova.compute.claims [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] vcpu limit: 128.00 VCPU, free: 128.00 VCPU
2017-01-05 16:57:04.848 3924 INFO nova.compute.claims [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] Claim successful
2017-01-05 16:57:05.489 3924 INFO nova.virt.hyperv.vmops [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] [instance: f1b4292c-acd9-4158-8852-b61e4c5650a1] Spawning new instance
2017-01-05 16:57:06.431 3924 ERROR nova.compute.manager [req-c3d00da0-0f9c-409d-9b22-022228a4c7f9 a133f23d27604a4781acbaad108882b2 4c118ae015e84365b28786efbe85a9db - - -] Instance failed network setup after 1 attempt(s)
2017-01-05 16:57:06.431 3924 ERROR nova.compute.manager Traceback (most recent call last):
2017-01-05 16:57:06.431 3924 ERROR nova ...
(more)
2017-01-05 02:11:58 -0500 answered a question Windows Instance - Instance failed network setup after 1 attempt(s)”.

Any update into this. I got a same problem

BR, Daniel

2016-11-29 03:21:30 -0500 asked a question RDO mitaka release has support for OVM 3.x

Hello,

I'm curious if there is some way to configure compute node(OVM Server 3.x) on my control node(Centos 7)

Thanks in advance for help!