Re: [openstack-dev] [Ironic] ironic-discoverd status update
tuskar-ui is supposed to enroll nodes into ironic. On Thu, Jan 8, 2015 at 4:36 AM, Zhou, Zhenzan wrote: > Sounds like we could add something new to automate the enrollment of new > nodes:-) > Collecting IPMI info into a csv file is still a trivial job... > > BR > Zhou Zhenzan > > -Original Message- > From: Dmitry Tantsur [mailto:dtant...@redhat.com] > Sent: Thursday, January 8, 2015 5:19 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Ironic] ironic-discoverd status update > > On 01/08/2015 06:48 AM, Kumar, Om (Cloud OS R&D) wrote: > > My understanding of discovery was to get all details for a node and then > register that node to ironic. i.e. Enrollment of the node to ironic. Pardon > me if it was out of line with your understanding of discovery. > That's why we agreed to use terms inspection/introspection :) sorry for > not being consistent here (name 'discoverd' is pretty old and hard to > change). > > discoverd does not enroll nodes. while possible, I'm somewhat resistant to > make it do enrolling, mostly because I want it to be user-controlled > process. > > > > > What I understand from the below mentioned spec is that the Node is > registered, but the spec will help ironic discover other properties of the > node. > that's what discoverd does currently. > > > > > -Om > > > > -Original Message- > > From: Dmitry Tantsur [mailto:dtant...@redhat.com] > > Sent: 07 January 2015 20:20 > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev] [Ironic] ironic-discoverd status update > > > > On 01/07/2015 03:44 PM, Matt Keenan wrote: > >> On 01/07/15 14:24, Kumar, Om (Cloud OS R&D) wrote: > >>> If it's a separate project, can it be extended to perform out of band > >>> discovery too..? That way there will be a single service to perform > >>> in-band as well as out of band discoveries.. May be it could follow > >>> driver framework for discovering nodes, where one driver could be > >>> native (in-band) and other could be iLO specific etc... > >>> > >> > >> I believe the following spec outlines plans for out-of-band discovery: > >> https://review.openstack.org/#/c/100951/ > > Right, so Ironic will have drivers, one of which (I hope) will be a > driver for discoverd. > > > >> > >> No idea what the progress is with regard to implementation within the > >> Kilo cycle though. > > For now we hope to get it merged in K. > > > >> > >> cheers > >> > >> Matt > >> > >>> Just a thought. > >>> > >>> -Om > >>> > >>> -Original Message- > >>> From: Dmitry Tantsur [mailto:dtant...@redhat.com] > >>> Sent: 07 January 2015 14:34 > >>> To: openstack-dev@lists.openstack.org > >>> Subject: Re: [openstack-dev] [Ironic] ironic-discoverd status update > >>> > >>> On 01/07/2015 09:58 AM, Zhou, Zhenzan wrote: > So is it possible to just integrate this project into ironic? I mean > when you create an ironic node, it will start discover in the > background. So we don't need two services? > >>> Well, the decision on the summit was that it's better to keep it > >>> separate. Please see https://review.openstack.org/#/c/135605/ for > >>> details on future interaction between discoverd and Ironic. > >>> > Just a thought, thanks. > > BR > Zhou Zhenzan > > -Original Message- > From: Dmitry Tantsur [mailto:dtant...@redhat.com] > Sent: Monday, January 5, 2015 4:49 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Ironic] ironic-discoverd status update > > On 01/05/2015 09:31 AM, Zhou, Zhenzan wrote: > > Hi, Dmitry > > > > I think this is a good project. > > I got one question: what is the relationship with > ironic-python-agent? > > Thanks. > Hi! > > No relationship right now, but I'm hoping to use IPA as a base for > introspection ramdisk in the (near?) future. > > > > BR > > Zhou Zhenzan > > > > -Original Message- > > From: Dmitry Tantsur [mailto:dtant...@redhat.com] > > Sent: Thursday, December 11, 2014 10:35 PM > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [Ironic] ironic-discoverd status update > > > > Hi all! > > > > As you know I actively promote ironic-discoverd project [1] as one > > of the means to do hardware inspection for Ironic (see e.g. spec > > [2]), so I decided it's worth to give some updates to the community > > from time to time. This email is purely informative, you may safely > > skip it, if you're not interested. > > > > Background > > == > > > > The discoverd project (I usually skip the "ironic-" part when > > talking about it) solves the problem of populating information > > about a node in Ironic database without help of any vendor-specific > > tool. This information usually includes Nova scheduling properties > > (CPU, RAM, disk > >
Re: [openstack-dev] [Neutron] vm can't get ipv6 address in ra mode:slaac + address mode: slaac
I also saw that bugzilla bug report. but my vm is ubuntu 14.04. and i also have tried to run rootwrap command manually with sudo but still no avail. On Thu, Dec 18, 2014 at 7:03 AM, Ihar Hrachyshka wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > I suspect that's some Red Hat distro, and radvd lacks SELinux context > set to allow neutron l3 agent to spawn it. > > On 18/12/14 15:50, Jerry Zhao wrote: > > It seems that radvd was not spawned successfully in l3-agent log: > > > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: Stderr: '/usr/bin/neutron-rootwrap: Unauthorized > > command: ip netns exec qrouter-6066faaa-0e35-4e7b-8988-7337c493bad7 > > radvd -C > > /var/run/neutron/ra/6066faaa-0e35-4e7b-8988-7337c493bad7.radvd.conf > > -p > > > /var/run/neutron/external/pids/6066faaa-0e35-4e7b-8988-7337c493bad7.pid.radvd > > > > > (no filter matched)\n' > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent Traceback (most recent call last): Dec 18 > > 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 neutron-l3-agent: > > 2014-12-18 11:23:34.611 18015 TRACE neutron.agent.l3_agent File > > > "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/common/utils.py", > > > > > line 341, in call > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent return func(*args, **kwargs) Dec 18 > > 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 neutron-l3-agent: > > 2014-12-18 11:23:34.611 18015 TRACE neutron.agent.l3_agent File > > > "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/l3_agent.py", > > > > > line 902, in process_router > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent self.root_helper) Dec 18 11:23:34 > > ci-overcloud-controller0-oxzkjphwfyw3 neutron-l3-agent: 2014-12-18 > > 11:23:34.611 18015 TRACE neutron.agent.l3_agent File > > > "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ra.py", > > > > > line 111, in enable_ipv6_ra > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent _spawn_radvd(router_id, radvd_conf, > > router_ns, root_helper) Dec 18 11:23:34 > > ci-overcloud-controller0-oxzkjphwfyw3 neutron-l3-agent: 2014-12-18 > > 11:23:34.611 18015 TRACE neutron.agent.l3_agent File > > > "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ra.py", > > > > > line 95, in _spawn_radvd > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent radvd.enable(callback, True) Dec 18 11:23:34 > > ci-overcloud-controller0-oxzkjphwfyw3 neutron-l3-agent: 2014-12-18 > > 11:23:34.611 18015 TRACE neutron.agent.l3_agent File > > > "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/external_process.py", > > > > > line 77, in enable > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent ip_wrapper.netns.execute(cmd, > > addl_env=self.cmd_addl_env) Dec 18 11:23:34 > > ci-overcloud-controller0-oxzkjphwfyw3 neutron-l3-agent: 2014-12-18 > > 11:23:34.611 18015 TRACE neutron.agent.l3_agent File > > > "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py", > > > > > line 554, in execute > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent check_exit_code=check_exit_code, > > extra_ok_codes=extra_ok_codes) Dec 18 11:23:34 > > ci-overcloud-controller0-oxzkjphwfyw3 neutron-l3-agent: 2014-12-18 > > 11:23:34.611 18015 TRACE neutron.agent.l3_agent File > > > "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/linux/utils.py", > > > > > line 82, in execute > > Dec 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent raise RuntimeError(m) Dec 18 11:23:34 > > ci-overcloud-controller0-oxzkjphwfyw3 neutron-l3-agent: 2014-12-18 > > 11:23:34.611 18015 TRACE neutron.agent.l3_agent RuntimeError: Dec > > 18 11:23:34 ci-overcloud-controller0-oxzkjphwfyw3 > > neutron-l3-agent: 2014-12-18 11:23:34.611 18015 TRACE > > neutron.agent.l3_agent Command: ['sudo', > > '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', > > 'netns', 'exec', 'qrouter-6066faaa-0e35-4e7b-8988-7337c493bad7', > > 'radvd', '-C', > > '/var/run/neutron/ra/6066faaa-0e35-4e7b-8988-7337c493bad7.radvd.conf', > > > > > '-p', > > > '/var/run/neutron/external/pids/6066faaa-0e35-4e7b-8988-7337c493bad7.pid.radvd'] > > > > Dec 18 11:23:34
Re: [openstack-dev] ipv6 and ipv4 dual stack for floating IP
Thanks for the pointer. On Thu, Oct 30, 2014 at 8:44 PM, Robert Li (baoli) wrote: > ipv6 floating Ip is currently not supported. > > Check out this review and the associated bug: > https://review.openstack.org/#/c/131145/ > > —Robert > > On 10/30/14, 6:47 AM, "Jerry Xinyu Zhao" wrote: > > Unfortunately, it seems to be the case. Just saw there is a summit talk > about it called IPv6 Feature in Openstack Juno. Dual stack floating ip > support is planned in K. > However, I couldn't even get single IPv6 floating IP to work. Even though > I configured only IPv6 subnet for the external network, I got those errors > from neutron-l3-agent when associating the floating IP to instance. > > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > Command: ['sudo', '/usr/bin/neutron-rootwrap', > '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', > 'qrouter-b243c786-4648-4d69-b749-ee5fad02069b', 'iptables-restore', '-c'] > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: Exit > code: 2 > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > Stdout: '' > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > Stderr: "iptables-restore v1.4.21: host/network `2001:470:1f0f:cb4::7' not > found\nError occurred at line: 39\nTry `iptables-restore -h' or > 'iptables-restore --help' for more information.\n" > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 2014-10-29 10:55:32.407 30286 ERROR neutron.agent.linux.iptables_manager > [-] IPTablesManager.apply failed to apply the following set of iptables > rules: > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 1. # Generated by iptables-save v1.4.21 on Wed Oct 29 10:55:32 2014 > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 2. *raw > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 3. :PREROUTING ACCEPT [148546:23091816] > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 4. :OUTPUT ACCEPT [219:20352] > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 5. :neutron-l3-agent-OUTPUT - [0:0] > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 6. :neutron-l3-agent-PREROUTING - [0:0] > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 7. [148546:23091816] -A PREROUTING -j neutron-l3-agent-PREROUTING > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 8. [219:20352] -A OUTPUT -j neutron-l3-agent-OUTPUT > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 9. COMMIT > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 10. # Completed on Wed Oct 29 10:55:32 2014 > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 11. # Generated by iptables-save v1.4.21 on Wed Oct 29 10:55:32 2014 > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 12. *mangle > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 13. :PREROUTING ACCEPT [148546:23091816] > Oct 29 10:55:32 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: > 14. :INPUT ACCEPT [55837:18978656] > > On Thu, Oct 30, 2014 at 6:32 PM, Harm Weites wrote: > >> I'm seeing the same error when trying to setup a whole new network >> through Horizon with external gateway and an ipv4 and ipv6 subnet. Eg, >> without floating ip. >> >> l3_agent.py is trying this: prefixlen = >> netaddr.IPNetwork(port['subnet']['cidr']).prefixlen >> >> Looking inside port[] lists the following items: >> >> 2014-10-30 10:26:05.834 21765 ERROR neutron.agent.l3_agent [-] Ignoring >> multiple IPs on router port b4d94d2a-0ba2-43f0-be5f-bb53e89abe32 >> 2014-10-30 10:26:05.836 21765 INFO neutron.agent.l3_agent [-] CHECK: >> port[status] = DOWN >> 2014-10-30 10:26:05.837 21765 INFO neutron.agent.l3_agent [-] CHECK: >> port[binding:host_id] = myhostname >> 2014-10-30 10:26:05.839 21765 INFO neutron.agent.l3_agent [-] CHECK: >> port[name] = >> 2014-10-30 10:26:05.840 21765 INFO neutron.agent.l3_agent [-] CHECK: >> port[allowed_address_pairs] = [] >> 2014-10-30 10:26:05.841 21765 INFO neutron.agent.l3_agent [-] CHECK: >> port[admin_state_up] = True >> 2014-10-30 10:26:05.843 21765 INFO neutron.agent.l3_agent [-] CHECK: >> port[network_id] = 00539791-0b2f-4628-9599-622fa00993b5 >> 2014-10-30 10:26:05.844 21765 INFO neutron.agent.l3_agent [-] CHECK: >> port[tenant_id] = >> 2014-10-30 10:26:05.846 217
Re: [openstack-dev] ipv6 and ipv4 dual stack for floating IP
_agent [-] CHECK:
> port[binding:vnic_type] = normal
> 2014-10-30 10:26:05.856 21765 INFO neutron.agent.l3_agent [-] CHECK:
> port[fixed_ips] = [{u'subnet_id': u'faaf9c91-19ce-4c14-8f86-c81949cdbac5',
> u'ip_address': u'192.168.64.30'}, {u'subnet_id':
> u'381d0c54-1a4e-4a27-9858-a81202e81487', u'ip_address':
> u'2001:470::64::'}]
> 2014-10-30 10:26:05.857 21765 INFO neutron.agent.l3_agent [-] CHECK:
> port[id] = b4d94d2a-0ba2-43f0-be5f-bb53e89abe32
> 2014-10-30 10:26:05.858 21765 INFO neutron.agent.l3_agent [-] CHECK:
> port[security_groups] = []
> 2014-10-30 10:26:05.860 21765 INFO neutron.agent.l3_agent [-] CHECK:
> port[device_id] = d3bbec5a-2075-4229-ba88-698f27cd0943
>
> _set_subnet_info() is set to log an ERROR when it encounters multiple
> addresses and then happily continues doing something:
>
> prefixlen = netaddr.IPNetwork(port['subnet']['cidr']).prefixlen
> port['ip_cidr'] = "%s/%s" % (ips[0]['ip_address'], prefixlen)
>
> Operations with just 1 (ipv6) ip go without any issues, the adress is
> added to a namespace and pongs just fine. Adding 2 subnets to this external
> net and creating a gateway to it on the l3 router causes a problem.
>
> Do we need to wait for K before we can fully go dual-stack?
>
> - Harm
>
> op 29-10-14 15:29, Jerry Xinyu Zhao schreef:
>
> Hi
> I want to use both ipv4 and ipv6 for floating ip at the same time.
> However, I have the following issue when setting router gateway or
> associate floating ip to an instance.
> Is it supported in the first place? What should I do to make it work?
> Thanks!
>
> neutron router-list
>
> +--++---+-+---+
> | id | name |
> external_gateway_info
>
>
> | distributed | ha|
>
> +--++---+-+---+
> | b243c786-4648-4d69-b749-ee5fad02069b | default-router | {"network_id":
> "02eca54a-420d-4d52-b045-1207e17994e5", "enable_snat": true,
> "external_fixed_ips": [{"subnet_id":
> "a188333f-77c3-40d9-9048-e733c4da30b1", "ip_address": "162.3.123.51"},
> {"subnet_id": "14d9dd91-b315-43bc-818d-ab21f62c1ebb", "ip_address":
> "2001:470:1f0f:cb4::7"}]} | False | False |
>
> +--++---+-+---+
>
>
> neutron-l3-agent log:
>
> Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
> 2014-10-29 14:10:08.941 30286 ERROR neutron.agent.l3_agent [-] Ignoring
> multiple IPs on router port 18c8874c-f9a0-4274-8f38-fab3da754c2b
> Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
> 2014-10-29 14:10:08.941 30286 ERROR neutron.agent.l3_agent [-] 'subnet'
> Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
> 2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent Traceback (most
> recent call last):
> Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
> 2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent File
> "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/common/utils.py",
> line 341, in call
> Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
> 2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent return
> func(*args, **kwargs)
> Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
> 2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent File
> "/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/l3_agent.py",
> line 948, in process_router
> Oct 29 14:10:08 overclo
[openstack-dev] ipv6 and ipv4 dual stack for floating IP
Hi
I want to use both ipv4 and ipv6 for floating ip at the same time. However,
I have the following issue when setting router gateway or associate
floating ip to an instance.
Is it supported in the first place? What should I do to make it work?
Thanks!
neutron router-list
+--++---+-+---+
| id | name |
external_gateway_info
| distributed | ha|
+--++---+-+---+
| b243c786-4648-4d69-b749-ee5fad02069b | default-router | {"network_id":
"02eca54a-420d-4d52-b045-1207e17994e5", "enable_snat": true,
"external_fixed_ips": [{"subnet_id":
"a188333f-77c3-40d9-9048-e733c4da30b1", "ip_address": "162.3.123.51"},
{"subnet_id": "14d9dd91-b315-43bc-818d-ab21f62c1ebb", "ip_address":
"2001:470:1f0f:cb4::7"}]} | False | False |
+--++---+-+---+
neutron-l3-agent log:
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 ERROR neutron.agent.l3_agent [-] Ignoring
multiple IPs on router port 18c8874c-f9a0-4274-8f38-fab3da754c2b
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 ERROR neutron.agent.l3_agent [-] 'subnet'
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent Traceback (most
recent call last):
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent File
"/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/common/utils.py",
line 341, in call
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent return
func(*args, **kwargs)
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent File
"/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/l3_agent.py",
line 948, in process_router
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent
self._set_subnet_info(ex_gw_port)
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent File
"/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/l3_agent.py",
line 864, in _set_subnet_info
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent prefixlen =
netaddr.IPNetwork(port['subnet']['cidr']).prefixlen
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent KeyError:
'subnet'
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
2014-10-29 14:10:08.941 30286 TRACE neutron.agent.l3_agent
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
Traceback (most recent call last):
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: File
"/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/eventlet/greenpool.py",
line 82, in _spawn_n_impl
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
func(*args, **kwargs)
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: File
"/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/l3_agent.py",
line 1837, in _process_router_update
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
self._process_router_if_compatible(router)
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent: File
"/opt/stack/venvs/openstack/local/lib/python2.7/site-packages/neutron/agent/l3_agent.py",
line 1812, in _process_router_if_compatible
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck neutron-l3-agent:
self.process_router(ri)
Oct 29 14:10:08 overcloud-controller0-ghqtsmsgjgck
Re: [openstack-dev] [infra] *urgent* Jenkins keeps verifying non-stop
Better send to infra's list too. On Mon, May 19, 2014 at 10:06 AM, Yi Sun wrote: > More info, I add a follow up comment on an old change set, and then it > happened. > Yi > > > On Mon, May 19, 2014 at 2:49 AM, Carlos Gonçalves wrote: > >> I was able to broke the loop by uploading a new patchset to Gerrit. >> Infra team, could you please clean the mess caused by Jenkins on Gerrit, >> please? >> >> Thanks, >> Carlos Goncalves >> >> On 19 May 2014, at 07:54, Carlos Gonçalves wrote: >> >> Hi, >> >> Could someone from the infra team check what's happening to Jenkins here >> https://review.openstack.org/#/c/92477/? It keeps re-verifying the >> change over and over for no apparent reason. >> >> Thanks, >> Carlos Goncalves >> >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > Android-x86 > http://www.android-x86.org > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
