To address this I had to manually resolve the dns hostname of network, controller and compute node. I placed it in /etc/hosts file.

Network Node

10.10.10.51 controlnode
10.10.10.53 computenode1

Controller Node

10.10.10.52 networknode
10.10.10.53 computenode1

Compute Node

10.10.10.52 networknode
10.10.10.51 controlnode

From: Mandalavandalz [mailto:[email protected]]
Sent: Wednesday, May 15, 2013 4:22 PM
To: mseknibilel/OpenStack-Grizzly-Install-Guide
Subject: [OpenStack-Grizzly-Install-Guide] Quantum server scheduler error (#53)

Every time when I run an instance I see this error once in the quantum server.log on the controller node:
WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'247039e6-5f7e-4d4a-a211-00c34f757c02'] ...........

Everything is running normal but the error is still present.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/53.

from openstack-grizzly-install-guide.

I have them in /etc/hosts but they are like my hostname. I was change them to something different from the hostname but nothing is change. I will try again after reboot nodes. Here is my /etc/hosts files right now.

#Controler
127.0.0.1 localhost
192.168.0.2 networknode
192.168.0.3 computenode1

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

#Network
127.0.0.1 localhost
192.168.0.1 controlnode
192.168.0.3 computenode1

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

#Compute
127.0.0.1 localhost
192.168.0.1 controlnode
192.168.0.2 networknode

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

On 16.05.2013, at 02:30, hrushig [email protected] wrote:

To address this I had to manually resolve the dns hostname of network, controller and compute node. I placed it in /etc/hosts file.

Network Node

10.10.10.51 controlnode
10.10.10.53 computenode1

Controller Node

10.10.10.52 networknode
10.10.10.53 computenode1

Compute Node

10.10.10.52 networknode
10.10.10.51 controlnode

From: Mandalavandalz [mailto:[email protected]]
Sent: Wednesday, May 15, 2013 4:22 PM
To: mseknibilel/OpenStack-Grizzly-Install-Guide
Subject: [OpenStack-Grizzly-Install-Guide] Quantum server scheduler error (#53)

Every time when I run an instance I see this error once in the quantum server.log on the controller node:
WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'247039e6-5f7e-4d4a-a211-00c34f757c02'] ...........

Everything is running normal but the error is still present.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/53.
—
Reply to this email directly or view it on GitHub.

from openstack-grizzly-install-guide.

After reboot with those hosts settings nothing change.
On 16.05.2013, at 03:27, Boyan Bonev [email protected] wrote:

I have them in /etc/hosts but they are like my hostname. I was change them to something different from the hostname but nothing is change. I will try again after reboot nodes. Here is my /etc/hosts files right now.

#Controler
127.0.0.1 localhost
192.168.0.2 networknode
192.168.0.3 computenode1

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

#Network
127.0.0.1 localhost
192.168.0.1 controlnode
192.168.0.3 computenode1

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

#Compute
127.0.0.1 localhost
192.168.0.1 controlnode
192.168.0.2 networknode

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

On 16.05.2013, at 02:30, hrushig [email protected] wrote:

To address this I had to manually resolve the dns hostname of network, controller and compute node. I placed it in /etc/hosts file.

Network Node

10.10.10.51 controlnode
10.10.10.53 computenode1

Controller Node

10.10.10.52 networknode
10.10.10.53 computenode1

Compute Node

10.10.10.52 networknode
10.10.10.51 controlnode

From: Mandalavandalz [mailto:[email protected]]
Sent: Wednesday, May 15, 2013 4:22 PM
To: mseknibilel/OpenStack-Grizzly-Install-Guide
Subject: [OpenStack-Grizzly-Install-Guide] Quantum server scheduler error (#53)

Every time when I run an instance I see this error once in the quantum server.log on the controller node:
WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'247039e6-5f7e-4d4a-a211-00c34f757c02'] ...........

Everything is running normal but the error is still present.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/53.
—
Reply to this email directly or view it on GitHub.

from openstack-grizzly-install-guide.

Verify that your OpenVSwitch agent is running fine in your compute node and network node.

quantum agent-list

from openstack-grizzly-install-guide.

Ok
I reinstall everything from the beginning and still same. I saw that when I add security group with ICMP type -1 I don;t have ping to instance when i add it again ping is a ok. First time when I start instance on compute node i have this error log in quantum server.log:

ERROR [keystoneclient.common.cms] Verify error: Error opening certificate file /var/lib/quantum/keystone-signing/signing_cert.pem
140715596957376:error:02001002:system library:fopen:No such file or directory:bss_file.c:169:fopen('/var/lib/quantum/keystone-signing/signing_cert.pem','r')
140715596957376:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:172:

but the file and directory exist? Next time after launch instance i have this error log once as I sayed:

WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'44edfc00-a250-4b50-8691-f436034232fa'], 'name': u'StudioWeb_INT', 'provider:physical_network': None, 'admin_state_up': True, 'tenant_id': u'8af319c25ab44777a19f5f98c0f0534e', 'provider:network_type': u'gre', 'router:external': False, 'shared': False, 'id': u'6b6bfbf5-3df1-4aec-98f8-01c7c251dad7', 'provider:segmentation_id': 1L}

StudioWeb_INT is a internal network added to router interface.

I use enable_isolated_metadata = True and enable_metadata_network = True in /etc/quantum/dhcp_agent.ini on network node to provide different root disk size flavors to images.

Here is quantum agent-list (command running from control node):

quantum agent-list
+--------------------------------------+--------------------+------------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+------------------+-------+----------------+
| 6cdeaab4-754c-440e-992a-54fedb4193a8 | Open vSwitch agent | grizzly-compute1 | :-) | True |
| 6e367d81-67cd-4d9d-8afd-b563a5fe6452 | Open vSwitch agent | grizzly-network | :-) | True |
| ca8f879f-5474-4b93-982a-abedcda46419 | L3 agent | grizzly-network | :-) | True |
| d1e9ba28-0227-48a0-8e59-aa80c0fd89e0 | DHCP agent | grizzly-network | :-) | True |
+--------------------------------------+--------------------+------------------+-------+----------------+

One more thing that i forgot i have also this error message in quantum server.log:

WARNING [quantum.scheduler.dhcp_agent_scheduler] DHCP agent d1e9ba28-0227-48a0-8e59-aa80c0fd89e0 is not active

before previous messages so I don't know what to think anymore. Also i have ping to instances from controller node after added route add -net 10.1.1.0/24 gw external router interface but I don't have ping to dhcp server. From network node via ip netns i have ping to all of them include dhcp server.

from openstack-grizzly-install-guide.

as a data point I have the same fail scheduling network message but everything works just fine.
I dont set either of the metadata options in the quantum/dhcp_agent.ini file. but I think the default is true.
I have metadata enabled and working fine from the VMs.

I have however lost track of what your underlying problem is :)

s

On 05/16/2013 03:00 PM, Mandalavandalz wrote:

Ok
I reinstall everything from the beginning and still same. I saw that when I add security group with ICMP type -1 I don;t have ping to instance when i add it again ping is a ok. First time when I start instance on compute node i have this error log in quantum server.log:

ERROR [keystoneclient.common.cms] Verify error: Error opening certificate file /var/lib/quantum/keystone-signing/signing_cert.pem
140715596957376:error:02001002:system library:fopen:No such file or directory:bss_file.c:169:fopen('/var/lib/quantum/keystone-signing/signing_cert.pem','r')
140715596957376:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:172:

but the file and directory exist? Next time after launch instance i have this error log once as I sayed:

WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'44edfc00-a250-4b50-8691-f436034232fa'], 'name': u'StudioWeb_INT', 'provider:physical_network': None, 'admin_state_up': True, 'tenant_id': u'8af319c25ab44777a19f5f98c0f0534e', 'provider:network_type': u'gre', 'router:external': False, 'shared': False, 'id': u'6b6bfbf5-3df1-4aec-98f8-01c7c251dad7', 'provider:segmentation_id': 1L}

StudioWeb_INT is a internal network added to router interface.

I use enable_isolated_metadata = True and enable_metadata_network = True in /etc/quantum/dhcp_agent.ini on network node to provide different root disk size flavors to images.

Here is quantum agent-list (command running from control node):

quantum agent-list
+--------------------------------------+--------------------+------------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+------------------+-------+----------------+
| 6cdeaab4-754c-440e-992a-54fedb4193a8 | Open vSwitch agent | grizzly-compute1 | :-) | True |
| 6e367d81-67cd-4d9d-8afd-b563a5fe6452 | Open vSwitch agent | grizzly-network | :-) | True |
| ca8f879f-5474-4b93-982a-abedcda46419 | L3 agent | grizzly-network | :-) | True |
| d1e9ba28-0227-48a0-8e59-aa80c0fd89e0 | DHCP agent | grizzly-network | :-) | True |
+--------------------------------------+--------------------+------------------+-------+----------------+

One more thing that i forgot i have also this error message in quantum server.log:

WARNING [quantum.scheduler.dhcp_agent_scheduler] DHCP agent d1e9ba28-0227-48a0-8e59-aa80c0fd89e0 is not active

before previous messages so I don't know what to think anymore. Also i have ping to instances from controller node after added route add -net 10.1.1.0/24 gw external router interface but I don't have ping to dhcp server. From network node via ip netns i have ping to all of them include dhcp server.

---

Reply to this email directly or view it on GitHub:
#53 (comment)

"Why is it so hot inside this handbasket?"

Steve Heistand [email protected]

from openstack-grizzly-install-guide.

The main problem of this error is that the guide on the controller node - qauntum is not assigned "manadgment - local
IP" I think.

from openstack-grizzly-install-guide.

I am having same error plus error from libvirtd:

2013-06-06 03:34:43.568+0000: 32334: warning : virAuditSend:135 : Failed to send audit message virt=kvm resrc=mem reason=start vm="instance-00000011" uuid=4a56ede7-bca3-4a80-a801-9e5f8e99be7e old-mem=0 new-mem=524288: Operation not permitted
2013-06-06 03:34:43.568+0000: 32334: warning : virAuditSend:135 : Failed to send audit message virt=kvm resrc=vcpu reason=start vm="instance-00000011" uuid=4a56ede7-bca3-4a80-a801-9e5f8e99be7e old-vcpu=0 new-vcpu=1: Operation not permitted
2013-06-06 03:34:43.568+0000: 32334: warning : virAuditSend:135 : Failed to send audit message virt=kvm op=start reason=booted vm="instance-00000011" uuid=4a56ede7-bca3-4a80-a801-9e5f8e99be7e vm-pid=7963: Operation not permitted

from openstack-grizzly-install-guide.

when i boot a new instance, i got a error message, and Everything is running normal but the error is still present

2013-06-20 02:41:39 WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'9a1c3be6-4678-4cf7-85e8-494b49fa40b7'], 'name': u'vlan3001', 'provider:physical_network': u'physnet1', 'admin_state_up': True, 'tenant_id': u'71eedd4d59384d13b7c80cdfb4999bf0', 'provider:network_type': u'vlan', 'router:external': False, 'shared': True, 'id': u'8717d0e0-d17e-4262-ab3e-2a423d71bae4', 'provider:segmentation_id': 3001L}
2013-06-20 02:41:40 WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'5c8ac388-972d-4599-a0f9-ad4cc7fa720f'], 'name': u'vlan3501', 'provider:physical_network': u'physnet2', 'admin_state_up': True, 'tenant_id': u'71eedd4d59384d13b7c80cdfb4999bf0', 'provider:network_type': u'vlan', 'router:external': False, 'shared': True, 'id': u'5b18231f-8a3a-4c5a-b6a8-a4773f45c695', 'provider:segmentation_id': 3501L}

if i check agent-list, the Open vSwitch agent on compute is up and down every several seconds.

date;quantum agent-list <<<

Thu Jun 20 02:40:02 UTC 2013
+--------------------------------------+--------------------+-------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+-------------+-------+----------------+
| 31e422a4-833c-47fd-8be2-aa71471999a0 | L3 agent | h172-16-0-2 | :-) | True |
| 4a26d0b7-23aa-4b84-96e2-295bd9aff9db | DHCP agent | h172-16-0-2 | :-) | True |
| 67f74ab1-f5b1-4944-8acf-f4b9eefa88ac | Open vSwitch agent | h172-16-0-2 | :-) | True |
| 99c9f8a2-587f-42ec-ac51-cc2bdc6cad5a | Open vSwitch agent | h172-16-0-3 | xxx | True |
+--------------------------------------+--------------------+-------------+-------+----------------+

date;quantum agent-list <<<

Thu Jun 20 02:40:04 UTC 2013
+--------------------------------------+--------------------+-------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+-------------+-------+----------------+
| 31e422a4-833c-47fd-8be2-aa71471999a0 | L3 agent | h172-16-0-2 | :-) | True |
| 4a26d0b7-23aa-4b84-96e2-295bd9aff9db | DHCP agent | h172-16-0-2 | :-) | True |
| 67f74ab1-f5b1-4944-8acf-f4b9eefa88ac | Open vSwitch agent | h172-16-0-2 | :-) | True |
| 99c9f8a2-587f-42ec-ac51-cc2bdc6cad5a | Open vSwitch agent | h172-16-0-3 | :-) | True |
+--------------------------------------+--------------------+-------------+-------+----------------+

date;quantum agent-list <<<

Thu Jun 20 02:40:09 UTC 2013
+--------------------------------------+--------------------+-------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+-------------+-------+----------------+
| 31e422a4-833c-47fd-8be2-aa71471999a0 | L3 agent | h172-16-0-2 | :-) | True |
| 4a26d0b7-23aa-4b84-96e2-295bd9aff9db | DHCP agent | h172-16-0-2 | :-) | True |
| 67f74ab1-f5b1-4944-8acf-f4b9eefa88ac | Open vSwitch agent | h172-16-0-2 | :-) | True |
| 99c9f8a2-587f-42ec-ac51-cc2bdc6cad5a | Open vSwitch agent | h172-16-0-3 | xxx | True |
+--------------------------------------+--------------------+-------------+-------+----------------+

from openstack-grizzly-install-guide.

i have set management ip and hosts file:

br-mgt Link encap:Ethernet HWaddr 2A:21:46:B1:A0:8F
inet addr:172.16.0.2 Bcast:172.16.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:40204036 errors:0 dropped:0 overruns:0 frame:0
TX packets:14536966 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28352824993 (26.4 GiB) TX bytes:26487904503 (24.6 GiB)

/etc/hosts
172.16.0.2 h172-16-0-2
172.16.0.3 h172-16-0-3

from openstack-grizzly-install-guide.

I have the same problem as pubyun. the Open vSwitch agent on compute is up and down every several seconds. Do you have done?

from openstack-grizzly-install-guide.