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
Re: [openstack-dev] Code Review (Jenkins-job-builder, BlameUpstreamCommitters plugin support)
Hi Peter, Could you explain more about the scenario this plugin fits in existing openstack jenkins jobs? I haven't seen any jobs with upstream , except devstack-gate related slave usage status transition jobs, which are already superseded by nodepool. IRC channel openstack-infra and mailing list openstack-infra are also better way to get infra core reviewers' attention, but you probably have to wait since most of them are in the summit right now. On Wed, Nov 6, 2013 at 1:47 AM, Peter Liljenberg wrote: > Hi, > > Could someone review this please: > > https://review.openstack.org/#/c/54085/ > > Regards, > Peter > > ___ > 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
Re: [openstack-dev] Introducing the NNFI scheduler for Zuul
++ \m/ On Thu, Sep 26, 2013 at 10:10 AM, James E. Blair wrote: > We recently made a change to Zuul's scheduling algorithm (how it > determines which changes to combine together and run tests). Now when a > change fails tests (or has a merge conflict), Zuul will move it out of > the series of changes that it is stacking together to be tested, but it > will still keep that change's position in the queue. Jobs for changes > behind it will be restarted without the failed change in their proposed > repo states. And if something later fails ahead of it, Zuul will once > again put it back into the stream of changes it's testing and give it > another chance. > > To visualize this, we've updated the status screen to include a tree > view: > > http://status.openstack.org/zuul/ > > (If you already have that loaded, be sure to hit reload.) > > In Zuul, this is called the Nearest Non-Failing Item (NNFI) algorithm > because in short, each item in a queue is at all times being tested > based on the nearest non-failing item ahead of it in the queue. > > On the infrastructure side, this is going to drive our use of cloud > resources even more, as Zuul will now try to run as many jobs as it can, > continuously. Every time a change fails, all of the jobs for changes > behind it will be aborted and restarted with a new proposed future > state. > > For developers, this means that changes should land faster, and more > throughput overall, as Zuul won't be waiting as long to re-test changes > after a job has failed. And that's what this is ultimately about -- > virtual machines are cheap compared to developer time, so the more > velocity our automated tests can sustain, the more velocity our project > can achieve. > > -Jim > > > (PS: There is a known problem with the status page not being able to > display the tree correctly while Zuul is in the middle of recalculating > the change graph. That should be fixed by next week, but in the mean > time, just enjoy the show.) > > ___ > 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
Re: [openstack-dev] [DevStack]
see if there is any pip install error before this failure. Search for Traceback. Copy and paste screen-g-api.txt and error_log here also helps. On Thu, Sep 12, 2013 at 8:46 AM, Shake Chen wrote: > > Now I try to install devstack in CentOS 6.4 and meet the error > > > 2013-09-12 23:26:06 + screen -S stack -p g-api -X stuff 'cd > /opt/stack/glance; /usr/bin/glance-api > --config-file=/etc/glance/glance-api.conf || echo "g-api 'ailed to start" | > tee "/opt/stack/status/stack/g-api.failure" > 2013-09-12 23:26:06 + echo 'Waiting for g-api (10.1.199.8:9292) to > start...' > 2013-09-12 23:26:06 Waiting for g-api (10.1.199.8:9292) to start... > 2013-09-12 23:26:06 + timeout 60 sh -c 'while ! http_proxy= wget -q -O- > http://10.1.199.8:9292; do sleep 1; done' > 2013-09-12 23:27:06 + die 195 'g-api did not start' > 2013-09-12 23:27:06 + local exitcode=0 > [root@node08 devstack]# 2013-09-12 23:27:06 + set +o xtrace > 2013-09-12 23:27:06 [Call Trace] > 2013-09-12 23:27:06 stack.sh:1159:start_glance > 2013-09-12 23:27:06 /opt/stack/devstack/lib/glance:195:die > 2013-09-12 23:27:06 [ERROR] /opt/stack/devstack/lib/glance:195 g-api did > not start > > > the other person in Ubuntu 12.04, also have same problem. > > > > -- > Shake Chen > > > ___ > 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
Re: [openstack-dev] [Openstack][keystone][LDAP] Error about "enable" and "desc" attribute type undefine.
Which release are you using? According to my experience last year when ldap backend was much more premature, i had to add those attributes in my ldap server's manually, because there is no such attribute in its schema. I don't know the status now. On Mon, Aug 19, 2013 at 11:42 PM, Qinglong.Meng wrote: > Hi all, > I configure keystone with ldap backend followed LDAP section of > http://docs.openstack.org/developer/keystone/configuration.html, > and when I create tenant in ldap, I got the error about "enable" and > "desc" attribute type undefined in keystone.log. > Here is keystone.conf: > http://paste.openstack.org/show/44574/ > > keystone.log > http://paste.openstack.org/show/44575/ > > the ldif of ldap server > http://paste.openstack.org/show/44578/ > > sample slapd.conf > http://paste.openstack.org/show/44579/ > > -- > > Lawrency Meng > mail: mengql112...@gmail.com > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openst...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ > 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
[openstack-dev] tempest test test_stack_crud_no_resources meets 400 bad request
Could anybody take a look at this failure. All projects are updated from trunk.
FAIL:
tempest.api.orchestration.stacks.test_stacks.StacksTestJSON.test_stack_crud_no_resources[gate,smoke]
tempest.api.orchestration.stacks.test_stacks.StacksTestJSON.test_stack_crud_no_resources[gate,smoke]
--
_StringException: Empty attachments:
stderr
stdout
Traceback (most recent call last):
File "tempest/api/orchestration/stacks/test_stacks.py", line 50, in
test_stack_crud_no_resources
stack_name, self.empty_template)
File "tempest/api/orchestration/base.py", line 70, in create_stack
parameters=parameters)
File "tempest/services/orchestration/json/orchestration_client.py",
line 57, in create_stack
resp, body = self.post(uri, headers=headers, body=body)
File "tempest/common/rest_client.py", line 259, in post
return self.request('POST', url, headers, body)
File "tempest/common/rest_client.py", line 387, in request
resp, resp_body)
File "tempest/common/rest_client.py", line 437, in _error_checker
raise exceptions.BadRequest(resp_body)
BadRequest: Bad request
Details: {u'title': u'Bad Request', u'explanation': u'The server could
not comply with the request since it is either malformed or otherwise
incorrect.', u'code': 400, u'error': {u'message': u"'module' object
has no attribute 'extract_args'", u'traceback': u'Traceback (most
recent call last):\n\n File
"/opt/stack/new/heat/heat/openstack/common/rpc/amqp.py", line 435, in
_process_data\n**args)\n\n File
"/opt/stack/new/heat/heat/openstack/common/rpc/dispatcher.py", line
172, in dispatch\nresult = getattr(proxyobj, method)(ctxt,
**kwargs)\n\n File "/opt/stack/new/heat/heat/engine/service.py", line
55, in wrapped\nreturn func(self, ctx, *args, **kwargs)\n\n File
"/opt/stack/new/heat/heat/engine/service.py", line 248, in
create_stack\ncommon_params =
api.extract_args(args)\n\nAttributeError: \'module\' object has no
attribute \'extract_args\'\n', u'type': u'AttributeError'}}
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] devstack exercise test failed at euca-register
without proxy , the test case is PASS. with proxy set in localrc,
euca-register will fail with a 400 code. it is weird that even 127.0.0.1 is
already included in no_proxy and it turned out that the api was never
through proxy.
Here I did a capture of both with and without proxy scenario, doing a
comparison will see that they are basically the same except the former
received 400 bad request code:
POST /services/Cloud/ HTTP/1.1
Host: 127.0.0.1:8773
Accept-Encoding: identity
Content-Length: 296
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
User-Agent: Boto/2.10.0 (linux2)
AWSAccessKeyId=3cfbdaae44a94dc59959d0d88bfc4f9c&Action=RegisterImage&Architecture=i386&ImageLocation=testbucket%2Fbundle.img.manifest.xml&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2013-08-17T01%3A24%3A51Z&Version=2009-11-30&Signature=jk8G7EpYn2mcjxQFT%2B53Lgg4usdxviKwpvXfLnxYrHI%3DHTTP/1.1
400 Bad Request
Content-Type: text/xml
Content-Length: 207
Date: Sat, 17 Aug 2013 01:24:51 GMT
S3ResponseErrorUnknown error
occured.req-d2138d8f-6363-4b65-b793-a2bb2d12baee
Without proxy:
POST /services/Cloud/ HTTP/1.1
Host: 127.0.0.1:8773
Accept-Encoding: identity
Content-Length: 296
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
User-Agent: Boto/2.10.0 (linux2)
AWSAccessKeyId=b8a07080b7394dfea0954dcd13a95aca&Action=RegisterImage&Architecture=i386&ImageLocation=testbucket%2Fbundle.img.manifest.xml&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2013-08-17T01%3A47%3A42Z&Version=2009-11-30&Signature=IV4heXI0GGp2a7gg90ZratX%2F2RxPbmqK6al26g72azM%3DHTTP/1.1
200 OK
Content-Type: text/xml
Content-Length: 198
Date: Sat, 17 Aug 2013 01:47:43 GMT
http://ec2.amazonaws.com/doc/2009-11-30/";>
req-6ea23353-5902-4ac3-b298-13bd841d9409
ami-0001
On Fri, Aug 16, 2013 at 9:38 AM, XINYU ZHAO wrote:
> bump.
> any input is appreciated.
>
>
> On Thu, Aug 15, 2013 at 5:04 PM, XINYU ZHAO wrote:
>
>> Updated every project to the latest. but each time i ran devstack, the
>> exercise test failed at the same place bundle.sh
>> Any hints?
>>
>> In console.log
>>
>> Uploaded image as testbucket/bundle.img.manifest.xml
>> ++ euca-register testbucket/bundle.img.manifest.xml
>> ++ cut -f2
>> + AMI='S3ResponseError: Unknown error occured.'
>> + die_if_not_set 57 AMI 'Failure registering testbucket/bundle.img'
>> + local exitcode=0
>> ++ set +o
>> ++ grep xtrace
>> + FXTRACE='set -o xtrace'
>> + set +o xtrace
>> + timeout 15 sh -c 'while euca-describe-images | grep S3ResponseError:
>> Unknown error occured. | grep -q available; do sleep 1; done'
>> grep: Unknown: No such file or directory
>> grep: error: No such file or directory
>> grep: occured.: No such file or directory
>> close failed in file object destructor:
>> sys.excepthook is missing
>> lost sys.stderr
>> + euca-deregister S3ResponseError: Unknown error occured.
>> Only 1 argument (image_id) permitted
>> + die 65 'Failure deregistering S3ResponseError: Unknown error occured.'
>> + local exitcode=1
>> + set +o xtrace
>> [Call Trace]
>> /opt/stack/new/devstack/exercises/bundle.sh:65:die
>> [ERROR] /opt/stack/new/devstack/exercises/bundle.sh:65 Failure deregistering
>> S3ResponseError: Unknown error occured.
>>
>>
>>
>> Here is what recorded in n-api log.
>>
>> 2013-08-15 15:44:20.331 27003 DEBUG nova.utils [-] Reloading cached file
>> /etc/nova/policy.json read_cached_file /opt/stack/new/nova/nova/utils.py:814
>> 2013-08-15 15:44:20.363 DEBUG nova.api.ec2
>> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] action: RegisterImage
>> __call__ /opt/stack/new/nova/nova/api/ec2/__init__.py:325
>> 2013-08-15 15:44:20.364 DEBUG nova.api.ec2
>> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] arg: Architecture
>> val: i386 __call__ /opt/stack/new/nova/nova/api/ec2/__init__.py:328
>> 2013-08-15 15:44:20.364 DEBUG nova.api.ec2
>> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] arg: ImageLocation
>> val: testbucket/bundle.img.manifest.xml __call__
>> /opt/stack/new/nova/nova/api/ec2/__init__.py:328
>> 2013-08-15 15:44:20.370 CRITICAL nova.api.ec2
>> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] Unexpected
>> S3ResponseError raised
>> 2013-08-15 15:44:20.370 CRITICAL nova.api.ec2
>> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] Environment:
>> {"CONTENT_TYPE": "application/x-www-form-urlencoded; charset=UTF-8",
>> "SCRIPT_NAME": "/services/Cloud", "REQU
Re: [openstack-dev] devstack exercise test failed at euca-register
bump.
any input is appreciated.
On Thu, Aug 15, 2013 at 5:04 PM, XINYU ZHAO wrote:
> Updated every project to the latest. but each time i ran devstack, the
> exercise test failed at the same place bundle.sh
> Any hints?
>
> In console.log
>
> Uploaded image as testbucket/bundle.img.manifest.xml
> ++ euca-register testbucket/bundle.img.manifest.xml
> ++ cut -f2
> + AMI='S3ResponseError: Unknown error occured.'
> + die_if_not_set 57 AMI 'Failure registering testbucket/bundle.img'
> + local exitcode=0
> ++ set +o
> ++ grep xtrace
> + FXTRACE='set -o xtrace'
> + set +o xtrace
> + timeout 15 sh -c 'while euca-describe-images | grep S3ResponseError:
> Unknown error occured. | grep -q available; do sleep 1; done'
> grep: Unknown: No such file or directory
> grep: error: No such file or directory
> grep: occured.: No such file or directory
> close failed in file object destructor:
> sys.excepthook is missing
> lost sys.stderr
> + euca-deregister S3ResponseError: Unknown error occured.
> Only 1 argument (image_id) permitted
> + die 65 'Failure deregistering S3ResponseError: Unknown error occured.'
> + local exitcode=1
> + set +o xtrace
> [Call Trace]
> /opt/stack/new/devstack/exercises/bundle.sh:65:die
> [ERROR] /opt/stack/new/devstack/exercises/bundle.sh:65 Failure deregistering
> S3ResponseError: Unknown error occured.
>
>
>
> Here is what recorded in n-api log.
>
> 2013-08-15 15:44:20.331 27003 DEBUG nova.utils [-] Reloading cached file
> /etc/nova/policy.json read_cached_file /opt/stack/new/nova/nova/utils.py:814
> 2013-08-15 15:44:20.363 DEBUG nova.api.ec2
> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] action: RegisterImage
> __call__ /opt/stack/new/nova/nova/api/ec2/__init__.py:325
> 2013-08-15 15:44:20.364 DEBUG nova.api.ec2
> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] arg: Architecture
> val: i386 __call__ /opt/stack/new/nova/nova/api/ec2/__init__.py:328
> 2013-08-15 15:44:20.364 DEBUG nova.api.ec2
> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] arg: ImageLocation
> val: testbucket/bundle.img.manifest.xml __call__
> /opt/stack/new/nova/nova/api/ec2/__init__.py:328
> 2013-08-15 15:44:20.370 CRITICAL nova.api.ec2
> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] Unexpected
> S3ResponseError raised
> 2013-08-15 15:44:20.370 CRITICAL nova.api.ec2
> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] Environment:
> {"CONTENT_TYPE": "application/x-www-form-urlencoded; charset=UTF-8",
> "SCRIPT_NAME": "/services/Cloud", "REQUEST_METHOD": "POST", "HTTP_HOST":
> "127.0.0.1:8773", "PATH_INFO": "/", "SERVER_PROTOCOL": "HTTP/1.0",
> "HTTP_USER_AGENT": "Boto/2.10.0 (linux2)", "RAW_PATH_INFO":
> "/services/Cloud/", "REMOTE_ADDR": "127.0.0.1", "REMOTE_PORT": "44294",
> "wsgi.url_scheme": "http", "SERVER_NAME": "127.0.0.1", "SERVER_PORT": "8773",
> "GATEWAY_INTERFACE": "CGI/1.1", "HTTP_ACCEPT_ENCODING": "identity"}
> 2013-08-15 15:44:20.371 DEBUG nova.api.ec2.faults
> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] EC2 error response:
> S3ResponseError: Unknown error occured. ec2_error_response
> /opt/stack/new/nova/nova/api/ec2/faults.py:31
> 2013-08-15 15:44:20.371 INFO nova.api.ec2
> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] 0.109800s 127.0.0.1 POST
> /services/Cloud/ CloudController:RegisterImage 400 [Boto/2.10.0 (linux2)]
> application/x-www-form-urlencoded text/xml
> 2013-08-15 15:44:20.379 INFO nova.ec2.wsgi.server
> [req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] 127.0.0.1 "POST
> /services/Cloud/ HTTP/1.1" status: 400 len: 317 time: 0.1177399
>
>
> execute manually on the machine:
>
> euca-register testbucket/bundle.img.manifest.xml --debug
> 2013-08-15 17:00:19,446 euca2ools [DEBUG]:Using access key provided by client.
> 2013-08-15 17:00:19,446 euca2ools [DEBUG]:Using secret key provided by client.
> 2013-08-15 17:00:19,446 euca2ools [DEBUG]:Method: POST
> 2013-08-15 17:00:19,447 euca2ools [DEBUG]:Path: /services/Cloud/
> 2013-08-15 17:00:19,447 euca2ools [DEBUG]:Data:
> 2013-08-15 17:00:19,447 euca2ools [DEBUG]:Headers: {}
> 2013-08-15 17:00:19,447 euca2ools [DEBUG]:Host: 127.0.0.1:8773
> 2013-08-15 17:00:19,447 euca2ools [DEBUG]:Params: {'Action': 'RegisterImage',
> 'Version': '2009-11-30', 'Architecture': 'i386', 'ImageLoc
[openstack-dev] devstack exercise test failed at euca-register
Updated every project to the latest. but each time i ran devstack, the
exercise test failed at the same place bundle.sh
Any hints?
In console.log
Uploaded image as testbucket/bundle.img.manifest.xml
++ euca-register testbucket/bundle.img.manifest.xml
++ cut -f2
+ AMI='S3ResponseError: Unknown error occured.'
+ die_if_not_set 57 AMI 'Failure registering testbucket/bundle.img'
+ local exitcode=0
++ set +o
++ grep xtrace
+ FXTRACE='set -o xtrace'
+ set +o xtrace
+ timeout 15 sh -c 'while euca-describe-images | grep S3ResponseError:
Unknown error occured. | grep -q available; do sleep 1; done'
grep: Unknown: No such file or directory
grep: error: No such file or directory
grep: occured.: No such file or directory
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr
+ euca-deregister S3ResponseError: Unknown error occured.
Only 1 argument (image_id) permitted
+ die 65 'Failure deregistering S3ResponseError: Unknown error occured.'
+ local exitcode=1
+ set +o xtrace
[Call Trace]
/opt/stack/new/devstack/exercises/bundle.sh:65:die
[ERROR] /opt/stack/new/devstack/exercises/bundle.sh:65 Failure
deregistering S3ResponseError: Unknown error occured.
Here is what recorded in n-api log.
2013-08-15 15:44:20.331 27003 DEBUG nova.utils [-] Reloading cached
file /etc/nova/policy.json read_cached_file
/opt/stack/new/nova/nova/utils.py:814
2013-08-15 15:44:20.363 DEBUG nova.api.ec2
[req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] action:
RegisterImage __call__
/opt/stack/new/nova/nova/api/ec2/__init__.py:325
2013-08-15 15:44:20.364 DEBUG nova.api.ec2
[req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] arg:
Architectureval: i386 __call__
/opt/stack/new/nova/nova/api/ec2/__init__.py:328
2013-08-15 15:44:20.364 DEBUG nova.api.ec2
[req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] arg:
ImageLocation val: testbucket/bundle.img.manifest.xml __call__
/opt/stack/new/nova/nova/api/ec2/__init__.py:328
2013-08-15 15:44:20.370 CRITICAL nova.api.ec2
[req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] Unexpected
S3ResponseError raised
2013-08-15 15:44:20.370 CRITICAL nova.api.ec2
[req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] Environment:
{"CONTENT_TYPE": "application/x-www-form-urlencoded; charset=UTF-8",
"SCRIPT_NAME": "/services/Cloud", "REQUEST_METHOD": "POST",
"HTTP_HOST": "127.0.0.1:8773", "PATH_INFO": "/", "SERVER_PROTOCOL":
"HTTP/1.0", "HTTP_USER_AGENT": "Boto/2.10.0 (linux2)",
"RAW_PATH_INFO": "/services/Cloud/", "REMOTE_ADDR": "127.0.0.1",
"REMOTE_PORT": "44294", "wsgi.url_scheme": "http", "SERVER_NAME":
"127.0.0.1", "SERVER_PORT": "8773", "GATEWAY_INTERFACE": "CGI/1.1",
"HTTP_ACCEPT_ENCODING": "identity"}
2013-08-15 15:44:20.371 DEBUG nova.api.ec2.faults
[req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] EC2 error
response: S3ResponseError: Unknown error occured. ec2_error_response
/opt/stack/new/nova/nova/api/ec2/faults.py:31
2013-08-15 15:44:20.371 INFO nova.api.ec2
[req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] 0.109800s
127.0.0.1 POST /services/Cloud/ CloudController:RegisterImage 400
[Boto/2.10.0 (linux2)] application/x-www-form-urlencoded text/xml
2013-08-15 15:44:20.379 INFO nova.ec2.wsgi.server
[req-5599cc0f-35b5-4451-9c96-88b48cc4600e demo demo] 127.0.0.1 "POST
/services/Cloud/ HTTP/1.1" status: 400 len: 317 time: 0.1177399
execute manually on the machine:
euca-register testbucket/bundle.img.manifest.xml --debug
2013-08-15 17:00:19,446 euca2ools [DEBUG]:Using access key provided by client.
2013-08-15 17:00:19,446 euca2ools [DEBUG]:Using secret key provided by client.
2013-08-15 17:00:19,446 euca2ools [DEBUG]:Method: POST
2013-08-15 17:00:19,447 euca2ools [DEBUG]:Path: /services/Cloud/
2013-08-15 17:00:19,447 euca2ools [DEBUG]:Data:
2013-08-15 17:00:19,447 euca2ools [DEBUG]:Headers: {}
2013-08-15 17:00:19,447 euca2ools [DEBUG]:Host: 127.0.0.1:8773
2013-08-15 17:00:19,447 euca2ools [DEBUG]:Params: {'Action':
'RegisterImage', 'Version': '2009-11-30', 'Architecture': 'i386',
'ImageLocation': 'testbucket/bundle.img.manifest.xml'}
2013-08-15 17:00:19,447 euca2ools [DEBUG]:establishing HTTP
connection: kwargs={'timeout': 70}
2013-08-15 17:00:19,447 euca2ools [DEBUG]:Token: None
2013-08-15 17:00:19,447 euca2ools [DEBUG]:using _calc_signature_2
2013-08-15 17:00:19,448 euca2ools [DEBUG]:query string:
AWSAccessKeyId=4b14f2d81b9045fdb3a0c989d283ebbe&Action=RegisterImage&Architecture=i386&ImageLocation=testbucket%2Fbundle.img.manifest.xml&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2013-08-16T00%3A00%3A19Z&Version=2009-11-30
2013-08-15 17:00:19,448 euca2ools [DEBUG]:string_to_sign: POST127.0.0.1:8773
/services/Cloud/
AWSAccessKeyId=4b14f2d81b9045fdb3a0c989d283ebbe&Action=RegisterImage&Architecture=i386&ImageLocation=testbucket%2Fbundle.img.manifest.xml&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2013-08-16T00%3A00%3A19Z&Version=2009-11-30
2013-08-15 17:00:19,448 euca2ools [DEBUG]:len(b64)=44
2013-08-15 17:00:19,448 euca2ools [DE
Re: [openstack-dev] can't install devstack - nova-api did not start
i updated mine but still no avail. still got this error. Did you just
update devstack or uninstall the oslo.config as well.
+ /opt/stack/new/keystone/bin/keystone-manage db_sync
2013-08-13 12:18:10 Traceback (most recent call last):
2013-08-13 12:18:10 File
"/opt/stack/new/keystone/bin/keystone-manage", line 16, in
2013-08-13 12:18:10 from keystone import cli
2013-08-13 12:18:10 File "/opt/stack/new/keystone/keystone/cli.py",
line 25, in
2013-08-13 12:18:10 from oslo.config import cfg
2013-08-13 12:18:10 ImportError: No module named config
On Mon, Aug 12, 2013 at 11:41 PM, Roman Gorodeckij wrote:
> Updating devstack to latest revision solves my problem.
>
> Sent from my iPhone
>
> On 2013 Rugp. 13, at 05:00, XINYU ZHAO wrote:
>
> Hi Sean
> I uninstalled the oslo.config 1.1.1 version and run devstack, but this
> time it stopped at
>
> 2013-08-09 18:55:16 + /opt/stack/new/keystone/bin/keystone-manage db_sync
> 2013-08-09 18:55:16 Traceback (most recent call last):
> 2013-08-09 18:55:16 File "/opt/stack/new/keystone/bin/keystone-manage",
> line 16, in
> 2013-08-09 18:55:16 from keystone import cli
> 2013-08-09 18:55:16 File "/opt/stack/new/keystone/keystone/cli.py", line
> 23, in
> 2013-08-09 18:55:16 from oslo.config import cfg
> 2013-08-09 18:55:16 ImportError: No module named config
> 2013-08-09 18:55:16 + [[ PKI == \P\K\I ]]
>
>
> An unexpected error prevented the server from fulfilling your request.
> (ProgrammingError) (1146, "Table 'keystone.service' doesn't exist") 'INSERT
> INTO service (id, type, extra) VALUES (%s, %s, %s)'
> ('32578395572b4cf2a70ba70b6031cd1d', 'identity', '{"name": "keystone",
> "description": "Keystone Identity Service"}') (HTTP 500)
> 2013-08-12 18:36:45 + KEYSTONE_SERVICE=
> 2013-08-12 18:36:45 + keystone endpoint-create --region RegionOne
> --service_id --publicurl http://127.0.0.1:5000/v2.0 --adminurl
> http://127.0.0.1:35357/v2.0 --internalurl http://127.0.0.1:5000/v2.0
>
> it seems that oslo.config was not properly imported after i re-installed
> it.
> but when i list the pip installations, it is there.
>
> /usr/local/bin/pip freeze |grep oslo.config
> -e git+
> http://10.145.81.234/openstackci/gerrit/p/oslo.config@c65d70c02494805ce50b88f343f8fafe7a521724#egg=oslo.config-master
> root@devstack-4:/# /usr/local/bin/pip search oslo.config
> oslo.config - Oslo configuration API
> INSTALLED: 1.2.0.a192.gc65d70c
> LATEST:1.1.1
>
>
>
> On Sat, Aug 10, 2013 at 7:07 AM, Sean Dague wrote:
>
>> Silly pip, trix are for kids.
>>
>> Ok, well:
>>
>> sudo pip install -I oslo.config==1.1.1
>>
>> then pip uninstall oslo.config
>>
>> On 08/09/2013 06:58 PM, Roman Gorodeckij wrote:
>>
>>> stack@hp:~/devstack$ sudo pip install oslo.config
>>> Requirement already satisfied (use --upgrade to upgrade): oslo.config in
>>> /opt/stack/oslo.config
>>> Requirement already satisfied (use --upgrade to upgrade): six in
>>> /usr/local/lib/python2.7/dist-**packages (from oslo.config)
>>> Cleaning up...
>>> stack@hp:~/devstack$ sudo pip uninstall oslo.config
>>> Can't uninstall 'oslo.config'. No files were found to uninstall.
>>> stack@hp:~/devstack$
>>>
>>> stack@hp:~/devstack$ cat /tmp/devstack/log//screen-n-**api.log
>>> | touch "/opt/stack/status/stack/n-**api.failure"nova &&
>>> /usr/local/bin/nova-api |
>>>
>>> Traceback (most recent call last):
>>>File "/usr/local/bin/nova-api", line 6, in
>>> from nova.cmd.api import main
>>>File "/opt/stack/nova/nova/cmd/api.**py", line 29, in
>>> from nova import config
>>>File "/opt/stack/nova/nova/config.**py", line 22, in
>>> from nova.openstack.common.db.**sqlalchemy import session as
>>> db_session
>>>File
>>> "/opt/stack/nova/nova/**openstack/common/db/**sqlalchemy/session.py",
>>> line 279, in
>>> deprecated_opts=[cfg.**DeprecatedOpt('sql_connection'**,
>>> AttributeError: 'module' object has no attribute 'DeprecatedOpt'
>>>
>>> nothing changed.
>>>
>>> On Aug 9, 2013, at 6:11 PM, Sean Dague wrote:
>>>
>>> This should be addressed by the latest devstack, however because we
>>>> moved to oslo.config out of git, some install environments might still have
>>>> oslo.config 1.1.0 somewh
Re: [openstack-dev] can't install devstack - nova-api did not start
Name: oslo.config
Version: 1.2.0.a192.gc65d70c
Location: /opt/stack/new/oslo.config
Requires: six
On Mon, Aug 12, 2013 at 7:59 PM, Noorul Islam K M wrote:
> XINYU ZHAO writes:
>
> > Hi Sean
> > I uninstalled the oslo.config 1.1.1 version and run devstack, but this
> time
> > it stopped at
> >
> > 2013-08-09 18:55:16 + /opt/stack/new/keystone/bin/keystone-manage db_sync
> > 2013-08-09 18:55:16 Traceback (most recent call last):
> > 2013-08-09 18:55:16 File
> > "/opt/stack/new/keystone/bin/keystone-manage", line 16, in
> > 2013-08-09 18:55:16 from keystone import cli
> > 2013-08-09 18:55:16 File "/opt/stack/new/keystone/keystone/cli.py",
> > line 23, in
> > 2013-08-09 18:55:16 from oslo.config import cfg
> > 2013-08-09 18:55:16 ImportError: No module named config
> > 2013-08-09 18:55:16 + [[ PKI == \P\K\I ]]
> >
> >
> > An unexpected error prevented the server from fulfilling your request.
> > (ProgrammingError) (1146, "Table 'keystone.service' doesn't exist")
> 'INSERT
> > INTO service (id, type, extra) VALUES (%s, %s, %s)'
> > ('32578395572b4cf2a70ba70b6031cd1d', 'identity', '{"name": "keystone",
> > "description": "Keystone Identity Service"}') (HTTP 500)
> > 2013-08-12 18:36:45 + KEYSTONE_SERVICE=
> > 2013-08-12 18:36:45 + keystone endpoint-create --region RegionOne
> > --service_id --publicurl http://127.0.0.1:5000/v2.0 --adminurl
> > http://127.0.0.1:35357/v2.0 --internalurl http://127.0.0.1:5000/v2.0
> >
> > it seems that oslo.config was not properly imported after i re-installed
> > it.
> > but when i list the pip installations, it is there.
> >
> > /usr/local/bin/pip freeze |grep oslo.config
> > -e git+
> >
> http://10.145.81.234/openstackci/gerrit/p/oslo.config@c65d70c02494805ce50b88f343f8fafe7a521724#egg=oslo.config-master
> > root@devstack-4:/# /usr/local/bin/pip search oslo.config
> > oslo.config - Oslo configuration API
> > INSTALLED: 1.2.0.a192.gc65d70c
> > LATEST:1.1.1
> >
> >
> >
>
> Please paste the output of
>
> pip show oslo.config
>
> Thanks and Regards
> Noorul
>
> >
> > On Sat, Aug 10, 2013 at 7:07 AM, Sean Dague wrote:
> >
> >> Silly pip, trix are for kids.
> >>
> >> Ok, well:
> >>
> >> sudo pip install -I oslo.config==1.1.1
> >>
> >> then pip uninstall oslo.config
> >>
> >> On 08/09/2013 06:58 PM, Roman Gorodeckij wrote:
> >>
> >>> stack@hp:~/devstack$ sudo pip install oslo.config
> >>> Requirement already satisfied (use --upgrade to upgrade): oslo.config
> in
> >>> /opt/stack/oslo.config
> >>> Requirement already satisfied (use --upgrade to upgrade): six in
> >>> /usr/local/lib/python2.7/dist-**packages (from oslo.config)
> >>> Cleaning up...
> >>> stack@hp:~/devstack$ sudo pip uninstall oslo.config
> >>> Can't uninstall 'oslo.config'. No files were found to uninstall.
> >>> stack@hp:~/devstack$
> >>>
> >>> stack@hp:~/devstack$ cat /tmp/devstack/log//screen-n-**api.log
> >>> | touch "/opt/stack/status/stack/n-**api.failure"nova &&
> >>> /usr/local/bin/nova-api |
> >>>
> >>> Traceback (most recent call last):
> >>>File "/usr/local/bin/nova-api", line 6, in
> >>> from nova.cmd.api import main
> >>>File "/opt/stack/nova/nova/cmd/api.**py", line 29, in
> >>> from nova import config
> >>>File "/opt/stack/nova/nova/config.**py", line 22, in
> >>> from nova.openstack.common.db.**sqlalchemy import session as
> >>> db_session
> >>>File
> "/opt/stack/nova/nova/**openstack/common/db/**sqlalchemy/session.py",
> >>> line 279, in
> >>> deprecated_opts=[cfg.**DeprecatedOpt('sql_connection'**,
> >>> AttributeError: 'module' object has no attribute 'DeprecatedOpt'
> >>>
> >>> nothing changed.
> >>>
> >>> On Aug 9, 2013, at 6:11 PM, Sean Dague wrote:
> >>>
> >>> This should be addressed by the latest devstack, however because we
> >>>> moved to oslo.config out of git, some install environments might
> still have
> >>>> oslo.config 1.1.0 somewhere, that pip no longer sees (so can't
> unins
Re: [openstack-dev] can't install devstack - nova-api did not start
Hi Sean
I uninstalled the oslo.config 1.1.1 version and run devstack, but this time
it stopped at
2013-08-09 18:55:16 + /opt/stack/new/keystone/bin/keystone-manage db_sync
2013-08-09 18:55:16 Traceback (most recent call last):
2013-08-09 18:55:16 File
"/opt/stack/new/keystone/bin/keystone-manage", line 16, in
2013-08-09 18:55:16 from keystone import cli
2013-08-09 18:55:16 File "/opt/stack/new/keystone/keystone/cli.py",
line 23, in
2013-08-09 18:55:16 from oslo.config import cfg
2013-08-09 18:55:16 ImportError: No module named config
2013-08-09 18:55:16 + [[ PKI == \P\K\I ]]
An unexpected error prevented the server from fulfilling your request.
(ProgrammingError) (1146, "Table 'keystone.service' doesn't exist") 'INSERT
INTO service (id, type, extra) VALUES (%s, %s, %s)'
('32578395572b4cf2a70ba70b6031cd1d', 'identity', '{"name": "keystone",
"description": "Keystone Identity Service"}') (HTTP 500)
2013-08-12 18:36:45 + KEYSTONE_SERVICE=
2013-08-12 18:36:45 + keystone endpoint-create --region RegionOne
--service_id --publicurl http://127.0.0.1:5000/v2.0 --adminurl
http://127.0.0.1:35357/v2.0 --internalurl http://127.0.0.1:5000/v2.0
it seems that oslo.config was not properly imported after i re-installed
it.
but when i list the pip installations, it is there.
/usr/local/bin/pip freeze |grep oslo.config
-e git+
http://10.145.81.234/openstackci/gerrit/p/oslo.config@c65d70c02494805ce50b88f343f8fafe7a521724#egg=oslo.config-master
root@devstack-4:/# /usr/local/bin/pip search oslo.config
oslo.config - Oslo configuration API
INSTALLED: 1.2.0.a192.gc65d70c
LATEST:1.1.1
On Sat, Aug 10, 2013 at 7:07 AM, Sean Dague wrote:
> Silly pip, trix are for kids.
>
> Ok, well:
>
> sudo pip install -I oslo.config==1.1.1
>
> then pip uninstall oslo.config
>
> On 08/09/2013 06:58 PM, Roman Gorodeckij wrote:
>
>> stack@hp:~/devstack$ sudo pip install oslo.config
>> Requirement already satisfied (use --upgrade to upgrade): oslo.config in
>> /opt/stack/oslo.config
>> Requirement already satisfied (use --upgrade to upgrade): six in
>> /usr/local/lib/python2.7/dist-**packages (from oslo.config)
>> Cleaning up...
>> stack@hp:~/devstack$ sudo pip uninstall oslo.config
>> Can't uninstall 'oslo.config'. No files were found to uninstall.
>> stack@hp:~/devstack$
>>
>> stack@hp:~/devstack$ cat /tmp/devstack/log//screen-n-**api.log
>> | touch "/opt/stack/status/stack/n-**api.failure"nova &&
>> /usr/local/bin/nova-api |
>>
>> Traceback (most recent call last):
>>File "/usr/local/bin/nova-api", line 6, in
>> from nova.cmd.api import main
>>File "/opt/stack/nova/nova/cmd/api.**py", line 29, in
>> from nova import config
>>File "/opt/stack/nova/nova/config.**py", line 22, in
>> from nova.openstack.common.db.**sqlalchemy import session as
>> db_session
>>File "/opt/stack/nova/nova/**openstack/common/db/**sqlalchemy/session.py",
>> line 279, in
>> deprecated_opts=[cfg.**DeprecatedOpt('sql_connection'**,
>> AttributeError: 'module' object has no attribute 'DeprecatedOpt'
>>
>> nothing changed.
>>
>> On Aug 9, 2013, at 6:11 PM, Sean Dague wrote:
>>
>> This should be addressed by the latest devstack, however because we
>>> moved to oslo.config out of git, some install environments might still have
>>> oslo.config 1.1.0 somewhere, that pip no longer sees (so can't uninstall)
>>>
>>> sudo pip install oslo.config
>>> sudo pip uninstall oslo.config
>>>
>>> rerun devstack, see if it works.
>>>
>>> -Sean
>>>
>>> On 08/09/2013 09:14 AM, Roman Gorodeckij wrote:
>>>
Tried to install devstack to dedicated server, ip's are defined.
Here's the output:
13-08-09 09:06:28 ++ echo -ne '\015'
2013-08-09 09:06:28 + NL=$'\r'
2013-08-09 09:06:28 + screen -S stack -p n-api -X stuff 'cd
/opt/stack/nova && /'sr/local/bin/nova-api || touch
"/opt/stack/status/stack/n-**api.failure"
2013-08-09 09:06:28 + echo 'Waiting for nova-api to start...'
2013-08-09 09:06:28 Waiting for nova-api to start...
2013-08-09 09:06:28 + wait_for_service 60http://192.168.1.6:8774
2013-08-09 09:06:28 + local timeout=60
2013-08-09 09:06:28 + local url=http://192.168.1.6:8774
2013-08-09 09:06:28 + timeout 60 sh -c 'while ! http_proxy=
https_proxy= curl -shttp://192.168.1.6:8774 >/dev/null; do sleep 1;
done'
2013-08-09 09:07:28 + die 698 'nova-api did not start'
2013-08-09 09:07:28 + local exitcode=0
stack@hp:~/devstack$ 2013-08-09 09:07:28 + set +o xtrace
Here's the log:
2013-08-09 09:07:28 [ERROR] ./stack.sh:698 nova-api did not start
stack@hp:~/devstack$ cat /tmp/devstack/log//screen-n-**api.log
t/stack/status/stack/n-api.**failure"nova && /usr/local/bin/nova-api
|| touch "/op
Traceback (most recent call last):
File "/usr/local/bin/nova-api", line 6, in
from nova.cmd.api import main
File "/opt/stack/nova/nova/cmd/api.**py", line 29
Re: [openstack-dev] can't install devstack - nova-api did not start
Hi Sean
I uninstalled the oslo.config 1.1.1 version and run devstack, but this time
it stopped at
2013-08-09 18:55:16 + /opt/stack/new/keystone/bin/keystone-manage db_sync
2013-08-09 18:55:16 Traceback (most recent call last):
2013-08-09 18:55:16 File
"/opt/stack/new/keystone/bin/keystone-manage", line 16, in
2013-08-09 18:55:16 from keystone import cli
2013-08-09 18:55:16 File "/opt/stack/new/keystone/keystone/cli.py",
line 23, in
2013-08-09 18:55:16 from oslo.config import cfg
2013-08-09 18:55:16 ImportError: No module named config
2013-08-09 18:55:16 + [[ PKI == \P\K\I ]]
An unexpected error prevented the server from fulfilling your request.
(ProgrammingError) (1146, "Table 'keystone.service' doesn't exist") 'INSERT
INTO service (id, type, extra) VALUES (%s, %s, %s)'
('32578395572b4cf2a70ba70b6031cd1d', 'identity', '{"name": "keystone",
"description": "Keystone Identity Service"}') (HTTP 500)
2013-08-12 18:36:45 + KEYSTONE_SERVICE=
2013-08-12 18:36:45 + keystone endpoint-create --region RegionOne
--service_id --publicurl http://127.0.0.1:5000/v2.0 --adminurl
http://127.0.0.1:35357/v2.0 --internalurl http://127.0.0.1:5000/v2.0
it seems that oslo.config was not properly imported after i re-installed
it.
but when i list the pip installations, it is there.
/usr/local/bin/pip freeze |grep oslo.config
-e git+
http://10.145.81.234/openstackci/gerrit/p/oslo.config@c65d70c02494805ce50b88f343f8fafe7a521724#egg=oslo.config-master
root@devstack-4:/# /usr/local/bin/pip search oslo.config
oslo.config - Oslo configuration API
INSTALLED: 1.2.0.a192.gc65d70c
LATEST:1.1.1
On Sat, Aug 10, 2013 at 7:07 AM, Sean Dague wrote:
> Silly pip, trix are for kids.
>
> Ok, well:
>
> sudo pip install -I oslo.config==1.1.1
>
> then pip uninstall oslo.config
>
> On 08/09/2013 06:58 PM, Roman Gorodeckij wrote:
>
>> stack@hp:~/devstack$ sudo pip install oslo.config
>> Requirement already satisfied (use --upgrade to upgrade): oslo.config in
>> /opt/stack/oslo.config
>> Requirement already satisfied (use --upgrade to upgrade): six in
>> /usr/local/lib/python2.7/dist-**packages (from oslo.config)
>> Cleaning up...
>> stack@hp:~/devstack$ sudo pip uninstall oslo.config
>> Can't uninstall 'oslo.config'. No files were found to uninstall.
>> stack@hp:~/devstack$
>>
>> stack@hp:~/devstack$ cat /tmp/devstack/log//screen-n-**api.log
>> | touch "/opt/stack/status/stack/n-**api.failure"nova &&
>> /usr/local/bin/nova-api |
>>
>> Traceback (most recent call last):
>>File "/usr/local/bin/nova-api", line 6, in
>> from nova.cmd.api import main
>>File "/opt/stack/nova/nova/cmd/api.**py", line 29, in
>> from nova import config
>>File "/opt/stack/nova/nova/config.**py", line 22, in
>> from nova.openstack.common.db.**sqlalchemy import session as
>> db_session
>>File "/opt/stack/nova/nova/**openstack/common/db/**sqlalchemy/session.py",
>> line 279, in
>> deprecated_opts=[cfg.**DeprecatedOpt('sql_connection'**,
>> AttributeError: 'module' object has no attribute 'DeprecatedOpt'
>>
>> nothing changed.
>>
>> On Aug 9, 2013, at 6:11 PM, Sean Dague wrote:
>>
>> This should be addressed by the latest devstack, however because we
>>> moved to oslo.config out of git, some install environments might still have
>>> oslo.config 1.1.0 somewhere, that pip no longer sees (so can't uninstall)
>>>
>>> sudo pip install oslo.config
>>> sudo pip uninstall oslo.config
>>>
>>> rerun devstack, see if it works.
>>>
>>> -Sean
>>>
>>> On 08/09/2013 09:14 AM, Roman Gorodeckij wrote:
>>>
Tried to install devstack to dedicated server, ip's are defined.
Here's the output:
13-08-09 09:06:28 ++ echo -ne '\015'
2013-08-09 09:06:28 + NL=$'\r'
2013-08-09 09:06:28 + screen -S stack -p n-api -X stuff 'cd
/opt/stack/nova && /'sr/local/bin/nova-api || touch
"/opt/stack/status/stack/n-**api.failure"
2013-08-09 09:06:28 + echo 'Waiting for nova-api to start...'
2013-08-09 09:06:28 Waiting for nova-api to start...
2013-08-09 09:06:28 + wait_for_service 60http://192.168.1.6:8774
2013-08-09 09:06:28 + local timeout=60
2013-08-09 09:06:28 + local url=http://192.168.1.6:8774
2013-08-09 09:06:28 + timeout 60 sh -c 'while ! http_proxy=
https_proxy= curl -shttp://192.168.1.6:8774 >/dev/null; do sleep 1;
done'
2013-08-09 09:07:28 + die 698 'nova-api did not start'
2013-08-09 09:07:28 + local exitcode=0
stack@hp:~/devstack$ 2013-08-09 09:07:28 + set +o xtrace
Here's the log:
2013-08-09 09:07:28 [ERROR] ./stack.sh:698 nova-api did not start
stack@hp:~/devstack$ cat /tmp/devstack/log//screen-n-**api.log
t/stack/status/stack/n-api.**failure"nova && /usr/local/bin/nova-api
|| touch "/op
Traceback (most recent call last):
File "/usr/local/bin/nova-api", line 6, in
from nova.cmd.api import main
File "/opt/stack/nova/nova/cmd/api.**py", line 29,
[openstack-dev] Fwd: can't install devstack - nova-api did not start
I have been experiencing the same issue. my oslo.config version is 1.1.1 when pip search oslo.config. I also tried pip uninstall oslo.config, rerun devstack but it ended up breaking here: 2013-08-09 18:55:16 + /opt/stack/new/keystone/bin/keystone-manage db_sync 2013-08-09 18:55:16 Traceback (most recent call last): 2013-08-09 18:55:16 File "/opt/stack/new/keystone/bin/keystone-manage", line 16, in 2013-08-09 18:55:16 from keystone import cli 2013-08-09 18:55:16 File "/opt/stack/new/keystone/keystone/cli.py", line 23, in 2013-08-09 18:55:16 from oslo.config import cfg 2013-08-09 18:55:16 ImportError: No module named config 2013-08-09 18:55:16 + [[ PKI == \P\K\I ]] ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
