Bug 1446054
| Summary: | neutron-openvswitch-agent.service running with db_ctl_base|ERR|transaction error | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eran Kuris <ekuris> | ||||||||
| Component: | openstack-neutron | Assignee: | Assaf Muller <amuller> | ||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Toni Freger <tfreger> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 11.0 (Ocata) | CC: | amuller, chrisw, nyechiel, srevivo, twilson | ||||||||
| Target Milestone: | Upstream M2 | ||||||||||
| Target Release: | 12.0 (Pike) | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-04-27 21:38:46 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1274518 [details]
SOS-report controller
Created attachment 1274524 [details]
SOS-report compute
This is a logging level error only. Creating the manager is supposed to fail if it already exists. This issue is also fixed in master by the ovsdbapp switch here: https://review.openstack.org/#/c/453014/ Eran thank you for the bug report. The error is harmless, you can see that the manager was indeed set because without it the agent would not be operational. The issue as I see it with this bug is that we log something that isn't an error at ERROR level. Fortunately this was already fixed on the master branch in this patch: 453014. I don't think it's worth backporting to stable branches, so closing this with 'next release' (OSP 12) as the resolution. |
Created attachment 1274516 [details] config_files Description of problem: After fresh deployment with OSP-11 neutron-openvswitch-agent.service is running with error : [root@compute-0 ~]# systemctl status neutron-openvswitch-agent.service -l ● neutron-openvswitch-agent.service - OpenStack Neutron Open vSwitch Agent Loaded: loaded (/usr/lib/systemd/system/neutron-openvswitch-agent.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2017-04-27 06:33:11 UTC; 29min ago Main PID: 19055 (neutron-openvsw) CGroup: /system.slice/neutron-openvswitch-agent.service ├─19055 /usr/bin/python2 /usr/bin/neutron-openvswitch-agent --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-openvswitch-agent --log-file /var/log/neutron/openvswitch-agent.log ├─19126 sudo neutron-rootwrap-daemon /etc/neutron/rootwrap.conf ├─19127 /usr/bin/python2 /usr/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf └─19452 ovsdb-client monitor tcp:127.0.0.1:6640 Interface name,ofport,external_ids --format=json Apr 27 06:33:12 compute-0.localdomain neutron-openvswitch-agent[19055]: Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future. Apr 27 06:33:12 compute-0.localdomain neutron-openvswitch-agent[19055]: Option "rpc_backend" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future. Apr 27 06:33:12 compute-0.localdomain neutron-openvswitch-agent[19055]: Option "notification_driver" from group "DEFAULT" is deprecated. Use option "driver" from group "oslo_messaging_notifications". Apr 27 06:33:12 compute-0.localdomain neutron-openvswitch-agent[19055]: Could not load neutron.openstack.common.notifier.rpc_notifier Apr 27 06:33:13 compute-0.localdomain sudo[19126]: neutron : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf Apr 27 06:33:14 compute-0.localdomain ovs-vsctl[19134]: ovs|00001|vsctl|INFO|Called as /bin/ovs-vsctl --timeout=10 --oneline --format=json -- --id=@manager create Manager "target=\"ptcp:6640:127.0.0.1\"" -- add Open_vSwitch . manager_options @manager -- set Manager ptcp:6640:127.0.0.1 inactivity_probe=10000 Apr 27 06:33:14 compute-0.localdomain neutron-openvswitch-agent[19055]: /usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py:200: FutureWarning: The access_policy argument is changing its default value to <class 'oslo_messaging.rpc.dispatcher.DefaultRPCAccessPolicy'> in version '?', please update the code to explicitly set None as the value: access_policy defaults to LegacyRPCAccessPolicy which exposes private methods. Explicitly set access_policy to DefaultRPCAccessPolicy or ExplicitRPCAccessPolicy. Apr 27 06:33:14 compute-0.localdomain neutron-openvswitch-agent[19055]: access_policy) Apr 27 06:33:17 compute-0.localdomain ovs-vsctl[19451]: ovs|00001|vsctl|INFO|Called as /bin/ovs-vsctl --timeout=10 --oneline --format=json -- --id=@manager create Manager "target=\"ptcp:6640:127.0.0.1\"" -- add Open_vSwitch . manager_options @manager Apr 27 06:33:17 compute-0.localdomain ovs-vsctl[19451]: ovs|00002|db_ctl_base|ERR|transaction error: {"details":"Transaction causes multiple rows in \"Manager\" table to have identical values (\"ptcp:6640:127.0.0.1\") for index on column \"target\". First row, with UUID 7d2a1b1b-9061-482c-9d60-6febbc1f0d9b, was inserted by this transaction. Second row, with UUID c7cf9ec5-b542-45d6-8975-07e44ce14865, existed in the database before this transaction and was not modified by the transaction.","error":"constraint violation"} the error exists on Compute & controller node. Version-Release number of selected component (if applicable): [root@compute-0 /]# rpm -qa |grep neutron python-neutron-10.0.1-1.el7ost.noarch python-neutron-lbaas-10.0.0-8.el7ost.noarch openstack-neutron-openvswitch-10.0.1-1.el7ost.noarch python-neutronclient-6.1.0-1.el7ost.noarch puppet-neutron-10.3.0-2.el7ost.noarch openstack-neutron-ml2-10.0.1-1.el7ost.noarch openstack-neutron-lbaas-10.0.0-8.el7ost.noarch openstack-neutron-metering-agent-10.0.1-1.el7ost.noarch openstack-neutron-common-10.0.1-1.el7ost.noarch openstack-neutron-10.0.1-1.el7ost.noarch openstack-neutron-sriov-nic-agent-10.0.1-1.el7ost.noarch python-neutron-lib-1.1.0-1.el7ost.noarch [root@compute-0 /]# rpm -qa |grep openvs openvswitch-ovn-central-2.6.1-10.git20161206.el7fdp.x86_64 openstack-neutron-openvswitch-10.0.1-1.el7ost.noarch openvswitch-ovn-common-2.6.1-10.git20161206.el7fdp.x86_64 openvswitch-2.6.1-10.git20161206.el7fdp.x86_64 python-openvswitch-2.6.1-10.git20161206.el7fdp.noarch openvswitch-ovn-host-2.6.1-10.git20161206.el7fdp.x86_64 How reproducible: always Steps to Reproduce: 1.Run deployment with infraredV2 use the configuration that attached. 2. 3. Actual results: errors Expected results: no errors Additional info: attached SOS-report I saw the bug on DPDK setup & regular setup.