[Yahoo-eng-team] [Bug 1523031] Re: Neighbor table entry for router missing with Linux bridge + L3HA + L2 population
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1523031 Title: Neighbor table entry for router missing with Linux bridge + L3HA + L2 population Status in neutron: Expired Bug description: Using Linux bridge, L3HA, and L2 population on Liberty, the neighbor table (ip neigh show) on the compute node lacks an entry for the router IP address. For example, using a router with 172.16.1.1 and instance with 172.16.1.4: On the node with the L3 agent containing the router: # ip neigh show 169.254.192.1 dev vxlan-476 lladdr fa:16:3e:9b:d5:6f PERMANENT 10.4.30.11 dev eth1 lladdr bc:76:4e:04:3c:59 REACHABLE 10.4.11.11 dev eth0 lladdr bc:76:4e:04:d0:75 REACHABLE 172.16.1.4 dev vxlan-466 lladdr fa:16:3e:ad:44:df PERMANENT 10.4.30.31 dev eth1 lladdr bc:76:4e:05:1f:5f STALE 10.4.11.31 dev eth0 lladdr bc:76:4e:04:38:4c STALE 10.4.30.1 dev eth1 lladdr bc:76:4e:04:41:62 STALE 10.4.11.1 dev eth0 lladdr bc:76:4e:04:77:72 DELAY 172.16.1.2 dev vxlan-466 lladdr fa:16:3e:a0:83:a5 PERMANENT # ip netns exec qrouter-1521b4b1-7de9-4ed0-be19-69ac02ccf520 ping 172.16.1.4 PING 172.16.1.4 (172.16.1.4) 56(84) bytes of data. ... On the node with the instance: # ip neigh show 172.16.1.2 dev vxlan-466 lladdr fa:16:3e:a0:83:a5 PERMANENT 10.4.11.1 dev eth0 lladdr bc:76:4e:04:77:72 DELAY 172.16.1.3 dev vxlan-466 lladdr fa:16:3e:41:3b:de PERMANENT 10.4.30.1 dev eth1 lladdr bc:76:4e:04:41:62 STALE 10.4.11.12 dev eth0 lladdr bc:76:4e:05:e2:f8 STALE 10.4.30.12 dev eth1 lladdr bc:76:4e:05:76:d1 STALE 10.4.11.41 dev eth0 lladdr bc:76:4e:05:e3:6a STALE 10.4.11.11 dev eth0 lladdr bc:76:4e:04:d0:75 REACHABLE 10.4.30.11 dev eth1 lladdr bc:76:4e:04:3c:59 STALE 172.16.1.2 and 172.16.1.3 belong to DHCP agents. I can access the instance from within both DHCP agent namespaces. On the node with the instance, I manually add a neighbor entry for the router: # ip neigh replace 172.16.1.1 lladdr fa:16:3e:0a:d4:39 dev vxlan-466 nud permanent On the node with the L3 agent containing the router: # ip netns exec qrouter-1521b4b1-7de9-4ed0-be19-69ac02ccf520 ping 172.16.1.4 64 bytes from 172.16.1.4: icmp_seq=1 ttl=64 time=2.21 ms 64 bytes from 172.16.1.4: icmp_seq=2 ttl=64 time=45.9 ms 64 bytes from 172.16.1.4: icmp_seq=3 ttl=64 time=1.23 ms 64 bytes from 172.16.1.4: icmp_seq=4 ttl=64 time=0.975 ms To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1523031/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1533429] Re: doc update for "Add multi-node devstack support to VPNaaS"
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1533429 Title: doc update for "Add multi-node devstack support to VPNaaS" Status in neutron: Expired Bug description: https://review.openstack.org/257504 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit e544a4f669950e44bf80a56bd9acf089483979d9 Author: Ryan Moats Date: Mon Dec 14 11:28:00 2015 -0600 Add multi-node devstack support to VPNaaS Modify devstack plugin to support multi-node confgurations (i.e. where the network node is split from the controller node). DocImpact: Migrate HowTo wiki page to additional devref text Change-Id: Iac5756ffe75b2125faace54b74b296036905a9b0 Signed-off-by: Ryan Moats To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1533429/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1602006] Re: openvswitch firewall driver IPv6 drop
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1602006 Title: openvswitch firewall driver IPv6 drop Status in neutron: Expired Bug description: I was testing ovs firewall driver added in https://bugs.launchpad.net/neutron/+bug/1461000 . Versions: - OpenStack: Mitaka Neutron: 8.1.2 ovs 2.5 linux kernel 4.4 Environment: 2 Controllers (Neutron L3 Agent in dvr_snat) 1 Dual stacked neutron provider network (ie; with IPv4 + IPv6 subnets) Created security group to allow traffic ICMP, UDP, TCP traffic Two physical interfaces on Computes and controllers. Second interface is used for data traffic and OVS attached to that interface (see attachment for ovs details) Compute1 (Neutron L3 Agent in dvr mode, ML2 + firewall_driver as openvswitch) Compute2 (Neutron L3 Agent in dvr mode, ML2 + firewall_driver as iptables) Created an Instance1 on *Compute1* with port attached to provider network (not using Tenant network to avoid any DVR flow intervention). Able to ping/tcp connect IPv4 but unable to reach IPv6 (tried from Router and dhcp namespace on the controller) Created an Instance2 on *Compute2* with port attached to provider network (not using Tenant network to avoid any DVR flow intervention). Able to ping/tcp connect both IPv4 and IPv6. I have changed the firewall_driver on Compute1 to iptables and created instance3 and able to reach IPv4 and IPv6 packets from the router interface without issues. Attaching my environment details and OVS flow tables for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1602006/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1599343] Re: VPNaaS should have a fullstack job that actually tests itself, not neutron
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1599343 Title: VPNaaS should have a fullstack job that actually tests itself, not neutron Status in neutron: Expired Bug description: As per the comments on [1], the neutron-vpnaas check and gate pipelines include a fullstack job that tests the base Neutron L3 agent. This job should be replaced/augmented to actually deploy and test VPNaaS agent itself. [1] https://review.openstack.org/#/c/287801/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1599343/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1661189] Re: calls to cinder always in user context
[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.] ** Changed in: nova Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1661189 Title: calls to cinder always in user context Status in OpenStack Compute (nova): Expired Bug description: My user is not Admin in Cinder. On attaching a volume nova tries to update the volume admin metadata, but this fails: "Policy doesn't allow volume:update_volume_admin_metadata to be performed." I would have expected that this call from nova to cinder happens in context of an elevated service user, and not with the user's context/token. We are on mitaka. Here is the stacktrace: http://paste.openstack.org/show/59/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1661189/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1669528] Re: portbinding update fails with ObjectDeletedError
Reviewed: https://review.openstack.org/441231 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=fc563eaabec392281be90bd2472bed4f6506cb40 Submitter: Jenkins Branch:master commit fc563eaabec392281be90bd2472bed4f6506cb40 Author: Kevin Benton Date: Fri Mar 3 08:51:33 2017 -0800 deepcopy binding and binding levels avoid expiration Perform a deepcopy on the sqla objects passed into the PortContext so we get detached versions of them safe to reference forever. This is necessary because the PortContexts outlive the transaction context managers they are creating in which means an object can be expired and result in a query after a commit (e.g. in bind_port_if_needed) that will fail and result in an exception. This required a few additional explicit session.merge calls to deal with cases where touching the mech context was implicitly expected to modify the DB state on the next commit. Closes-Bug: #1669528 Change-Id: Ib5ba2daa80acba53c082bade1f61a3ee44ca41fc ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1669528 Title: portbinding update fails with ObjectDeletedError Status in neutron: Fix Released Bug description: The gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial gate failed in a recent neutron change [1]. Digging into the logs [2] it appears to be DB related:: -- 2017-03-01 15:47:17.800 1412 ERROR oslo_messaging.rpc.server ObjectDeletedError: Instance '' has been deleted, or its row is otherwise not present. -- Based on logstash [3], this appears to be a frequent error. It's not clear to me if neutron is really the issue here, or if something else is happening and causing the neutron error. [1] https://review.openstack.org/#/c/422210/ [2] http://logs.openstack.org/10/422210/9/check/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/f639199/logs/screen-q-svc.txt.gz? [3] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ObjectDeletedError%5C%22 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1669528/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680986] [NEW] Remove consistency group volumes form exception redict url error.
Public bug reported:
Env: devstack master branch
When submit remove consistency group volumes and execute exception,
it will throws an exception.
Exception info:
Internal Server Error:
/project/cgroups/aa1c9791-0878-4aa1-bd4a-52658ff909c5/remove_volumese/
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 132, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec
return view_func(request, *args, **kwargs)
File "/opt/stack/horizon/horizon/decorators.py", line 52, in dec
return view_func(request, *args, **kwargs)
File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec
return view_func(request, *args, **kwargs)
File "/opt/stack/horizon/horizon/decorators.py", line 84, in dec
return view_func(request, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py",
line 71, in view
return self.dispatch(request, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py",
line 89, in dispatch
return handler(request, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/django/views/generic/edit.py",
line 215, in post
return self.form_valid(form)
File "/opt/stack/horizon/horizon/forms/views.py", line 180, in form_valid
exceptions.handle(self.request)
File "/opt/stack/horizon/horizon/exceptions.py", line 352, in handle
six.reraise(exc_type, exc_value, exc_traceback)
File "/opt/stack/horizon/horizon/forms/views.py", line 177, in form_valid
handled = form.handle(self.request, form.cleaned_data)
File
"/opt/stack/horizon/openstack_dashboard/dashboards/project/cgroups/forms.py",
line 88, in handle
redirect = reverse("horizon:project:groups:index")
File "/usr/local/lib/python2.7/dist-packages/django/core/urlresolvers.py",
line 571, in reverse
(key, ':'.join(resolved_path)))
NoReverseMatch: u'groups' is not a registered namespace inside 'horizon:project'
** Affects: horizon
Importance: Undecided
Assignee: wei.ying (wei.yy)
Status: New
** Changed in: horizon
Assignee: (unassigned) => wei.ying (wei.yy)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1680986
Title:
Remove consistency group volumes form exception redict url error.
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Env: devstack master branch
When submit remove consistency group volumes and execute exception,
it will throws an exception.
Exception info:
Internal Server Error:
/project/cgroups/aa1c9791-0878-4aa1-bd4a-52658ff909c5/remove_volumese/
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 132, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec
return view_func(request, *args, **kwargs)
File "/opt/stack/horizon/horizon/decorators.py", line 52, in dec
return view_func(request, *args, **kwargs)
File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec
return view_func(request, *args, **kwargs)
File "/opt/stack/horizon/horizon/decorators.py", line 84, in dec
return view_func(request, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py",
line 71, in view
return self.dispatch(request, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py",
line 89, in dispatch
return handler(request, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/django/views/generic/edit.py",
line 215, in post
return self.form_valid(form)
File "/opt/stack/horizon/horizon/forms/views.py", line 180, in form_valid
exceptions.handle(self.request)
File "/opt/stack/horizon/horizon/exceptions.py", line 352, in handle
six.reraise(exc_type, exc_value, exc_traceback)
File "/opt/stack/horizon/horizon/forms/views.py", line 177, in form_valid
handled = form.handle(self.request, form.cleaned_data)
File
"/opt/stack/horizon/openstack_dashboard/dashboards/project/cgroups/forms.py",
line 88, in handle
redirect = reverse("horizon:project:groups:index")
File "/usr/local/lib/python2.7/dist-packages/django/core/urlresolvers.py",
line 571, in reverse
(key, ':'.join(resolved_path)))
NoReverseMatch: u'groups' is not a registered namespace inside
'horizon:project'
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1680986/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.
[Yahoo-eng-team] [Bug 1677742] Re: Missing Binary Commands don't log in a sane way
Reviewed: https://review.openstack.org/453278
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=0476ad641dffb4cdcb6fb72e9dd6579ffc21b754
Submitter: Jenkins
Branch:master
commit 0476ad641dffb4cdcb6fb72e9dd6579ffc21b754
Author: Brian Haley
Date: Tue Apr 4 13:54:42 2017 -0400
Print useful error on rootwrap daemon failure
If the rootwrap daemon fails to execute a command, it
generates a cryptic message:
Unserializable message: ('#ERROR', ValueError('I/O operation on closed
file',))
We should at least log the command that we were trying
to run, which will help users figure out why it failed.
Change-Id: I2c94e5a226630432028351f8287868f4fe5d2fa1
Closes-bug: #1677742
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1677742
Title:
Missing Binary Commands don't log in a sane way
Status in neutron:
Fix Released
Bug description:
When running neutron in an environment with a missing binary command
run by a linux agent the failure mode is far from clear. For example:
http://paste.openstack.org/show/604877/
Is what was logged on my system when I didn't have ipset installed. It's not
clear at all from this error message or stack trace that was the cause of
failure. The only way I was able to figure this out was to switch the default
rootwrap-daemon config file to DEBUG level and use syslog to actually see the
missing executable error message.
You shouldn't need to modify the default log levels to see the cause
of a fatal error like a missing binary command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1677742/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1604115] Re: test_cleanup_stale_devices functional test sporadic failures
It still happens: http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_status%3A%5C%22FAILURE%5C%22%20AND%20message%3A%5C%22%2C%20in%20test_cleanup_stale_devices%5C%22%20AND%20build_name%3A%5C %22gate-neutron-dsvm-functional-ubuntu-xenial%5C%22 3 hits in 7 days, both newton and master. ** Changed in: neutron Status: Fix Released => Confirmed ** Changed in: neutron Assignee: Armando Migliaccio (armando-migliaccio) => Ihar Hrachyshka (ihar-hrachyshka) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1604115 Title: test_cleanup_stale_devices functional test sporadic failures Status in neutron: Confirmed Bug description: 19 hits in the last 7 days build_status:"FAILURE" AND message:", in test_cleanup_stale_devices" AND build_name:"gate-neutron-dsvm-functional" Example TRACE failure: http://logs.openstack.org/55/342955/3/check/gate-neutron-dsvm-functional/0cd557d/console.html#_2016-07-18_16_42_45_219041 Example log from testrunner: http://logs.openstack.org/55/342955/3/check/gate-neutron-dsvm-functional/0cd557d/logs/dsvm-functional-logs/neutron.tests.functional.agent.linux.test_dhcp.TestDhcp.test_cleanup_stale_devices.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1604115/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1667447] Re: Missing unit tests for cinderclient in nova
** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1667447 Title: Missing unit tests for cinderclient in nova Status in OpenStack Compute (nova): Invalid Bug description: There were no unit tests in test_cinder.py for testing cinderclient https://github.com/openstack/nova/blob/master/nova/volume/cinder.py#L59 https://github.com/openstack/nova/blob/master/nova/tests/unit/volume/test_cinder.py To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1667447/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680614] Re: test_instance_get_all_by_host does not actually test instance_get_all_by_host
Reviewed: https://review.openstack.org/454360 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1521049dae51220ac47aeed40ed80aa13ad57036 Submitter: Jenkins Branch:master commit 1521049dae51220ac47aeed40ed80aa13ad57036 Author: Matt Riedemann Date: Thu Apr 6 17:47:11 2017 -0400 Fix test_instance_get_all_by_host This test was not testing instance_get_all_by_host, it was testing _instance_get_all_uuids_by_host, which is completely redundant with the same test that comes right after it. ¯\_(ツ)_/¯ Change-Id: Ia0331e3f622f17067bf5900f92b3f8ff2aff966e Closes-Bug: #1680614 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1680614 Title: test_instance_get_all_by_host does not actually test instance_get_all_by_host Status in OpenStack Compute (nova): Fix Released Bug description: This unit test: https://github.com/openstack/nova/blob/6103ec7c113121866344cdca2fbbbf7b80dfa975/nova/tests/unit/db/test_db_api.py#L1170 Is not actually testing the thing it's supposed to be testing, which is: https://github.com/openstack/nova/blob/6103ec7c113121866344cdca2fbbbf7b80dfa975/nova/db/sqlalchemy/api.py#L2528 It's basically testing the same method that's tested right after it: https://github.com/openstack/nova/blob/6103ec7c113121866344cdca2fbbbf7b80dfa975/nova/tests/unit/db/test_db_api.py#L1186 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1680614/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680918] [NEW] Nova upgrade fails if PCI devices of type-PF or type-PCI are present in the database
Public bug reported:
Description
===
If a Nova DB is upgraded (migrated) while containing PCI devices with device
type 'type-PF' or 'type-PCI',
a validation error similar to this will be thrown:
"ValidationError: There are still 2 unmigrated records in the
pci_devices table. Migration cannot continue until all records have been
migrated."
The error is generated by the 330_enforce_mitaka_online_migrations.py
upgrade script.
The PCI device migration validation will fail if any PCI device entries
without a populated parent_addr are found. However, the parent_addr
really only applies to PCI device entries of 'type-VF' (ie. SRIOV
virtual functions)
This is an example of what the pci_devices table looks like with SRIOV
enabled PCI devices if the appropriate entries are whitelisted in
nova.conf:
MariaDB [nova]> select * from pci_devices;
+-+-++-++-+--++---+--+--+-+---++---++---+--+
| created_at | updated_at | deleted_at | deleted | id |
compute_node_id | address | product_id | vendor_id | dev_type | dev_id
| label | status| extra_info | instance_uuid | request_id |
numa_node | parent_addr |
+-+-++-++-+--++---+--+--+-+---++---++---+--+
| 2017-04-06 21:01:21 | 2017-04-06 21:53:13 | NULL | 0 | 1 |
1 | :05:10.1 | 10ed | 8086 | type-VF | pci__05_10_1
| label_8086_10ed | available | {} | NULL | NULL |
0 | :05:00.1 |
| 2017-04-06 21:01:21 | 2017-04-06 21:53:13 | NULL | 0 | 2 |
1 | :05:10.3 | 10ed | 8086 | type-VF | pci__05_10_3
| label_8086_10ed | available | {} | NULL | NULL |
0 | :05:00.1 |
| 2017-04-06 21:01:21 | 2017-04-06 21:53:13 | NULL | 0 | 3 |
1 | :05:10.5 | 10ed | 8086 | type-VF | pci__05_10_5
| label_8086_10ed | available | {} | NULL | NULL |
0 | :05:00.1 |
| 2017-04-06 21:01:21 | 2017-04-06 21:53:13 | NULL | 0 | 4 |
1 | :05:10.7 | 10ed | 8086 | type-VF | pci__05_10_7
| label_8086_10ed | available | {} | NULL | NULL |
0 | :05:00.1 |
| 2017-04-06 21:53:13 | NULL| NULL | 0 | 5 |
1 | :05:00.0 | 10fb | 8086 | type-PF | pci__05_00_0
| label_8086_10fb | available | {} | NULL | NULL |
0 | NULL |
| 2017-04-06 21:53:13 | NULL| NULL | 0 | 6 |
1 | :05:00.1 | 10fb | 8086 | type-PF | pci__05_00_1
| label_8086_10fb | available | {} | NULL | NULL |
0 | NULL |
+-+-++-++-+--++---+--+--+-+---++---++---+--+
6 rows in set (0.00 sec)
I think the upgrade script should be checking the PciDevice dev_type field for
'type-VF' when validating the parent_addr.
Steps to reproduce
==
1. Install a Mitaka control node and edit the nova.conf file to include
1 or more PCI devices in the pci_passthrough_whitelist. ie:
pci_passthrough_whitelist = {"vendor_id": "8086", "product_id":"10fb"}
2. Install a second Newton or newer control node and edit the nova.conf
to point to the SQL database of the Mitaka node. ie:
[database]
connection = mysql+pymysql://root:supersecret@/nova?charset=utf8
[api_database]
connection = mysql+pymysql://root:supersecret@/nova_api?charset=utf8
3. From the new control node, issue the following command:
nova-manage db sync
Expected result
===
Database migration/upgrade should succeed
Actual result
=
A ValidationError, similar to:
"ValidationError: There are still unmigrated records in the
pci_devices table. Migration cannot continue until all records have been
migrated."
Environment
===
1. Exact version of OpenStack you are running. See the following
Mitaka (old node) Newton, Ocata (new node)
2. Which hypervisor did you use?
libvirt + kvm
2. Which storage type did you use?
lvm
3. Which networking type did you use?
Neutron, OVS
Logs & Configs
==
See attached
** Affects: nova
Importance: Undecided
Assignee: Steven Webster (swebster-wr)
Status: In Progress
** Tags: pci
[Yahoo-eng-team] [Bug 1680912] [NEW] Sometimes grenade job fails with NetworkNotFound because a network delete request took too long
Public bug reported:
http://logs.openstack.org/38/453838/2/gate/gate-grenade-dsvm-neutron-
ubuntu-xenial/84cf5aa/logs/grenade.sh.txt.gz#_2017-04-07_03_45_19_220
The DELETE request in question is:
2017-04-07 03:45:19.220 | 2017-04-07 03:41:31,143 18539 WARNING
[urllib3.connectionpool] Retrying (Retry(total=9, connect=None, read=None,
redirect=5)) after connection broken by
'ReadTimeoutError("HTTPConnectionPool(host='149.202.181.79', port=9696): Read
timed out. (read timeout=60)",)':
/v2.0/networks/46b0776a-3917-440d-9b90-4ab02a735188
2017-04-07 03:45:19.220 | 2017-04-07 03:41:34,053 18539 INFO
[tempest.lib.common.rest_client] Request (NetworksIpV6Test:_run_cleanups): 404
DELETE
http://149.202.181.79:9696/v2.0/networks/46b0776a-3917-440d-9b90-4ab02a735188
62.919s
2017-04-07 03:45:19.220 | 2017-04-07 03:41:34,053 18539 DEBUG
[tempest.lib.common.rest_client] Request - Headers: {'Content-Type':
'application/json', 'Accept': 'application/json', 'X-Auth-Token': ''}
2017-04-07 03:45:19.220 | Body: None
2017-04-07 03:45:19.221 | Response - Headers: {u'content-length':
'138', u'content-type': 'application/json', u'x-openstack-request-id':
'req-d1dfda92-9b9b-421f-b45f-7ef4746e43c6', u'date': 'Fri, 07 Apr 2017 03:41:34
GMT', u'connection': 'close', 'content-location':
'http://149.202.181.79:9696/v2.0/networks/46b0776a-3917-440d-9b90-4ab02a735188',
'status': '404'}
2017-04-07 03:45:19.221 | Body: {"NeutronError": {"message":
"Network 46b0776a-3917-440d-9b90-4ab02a735188 could not be found.", "type":
"NetworkNotFound", "detail": ""}}
What we see is first attempt to delete the network failed after 60
seconds, so we retry DELETE, at which point we see that the network is
no longer there.
In neutron-server log, we see that the first DELETE attempt was received
with req_id req-933bd8b3-cd8f-4d2f-8f0c-505f85347b9d at 03:40:31.344 but
completed at 03:41:33.951 only (probably because second DELETE attempt
triggered something that unblocked the first request).
In logs handling the first DELETE request, we see some looping de-
allocating ports:
2017-04-07 03:40:34.227 8785 DEBUG neutron.plugins.ml2.plugin
[req-933bd8b3-cd8f-4d2f-8f0c-505f85347b9d tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Ports to auto-deallocate:
set([u'b5ff06a6-4084-4961-b239-9f29aa42c68a']) delete_subnet
/opt/stack/old/neutron/neutron/plugins/ml2/plugin.py:1093
2017-04-07 03:40:34.231 8785 DEBUG neutron.callbacks.manager
[req-933bd8b3-cd8f-4d2f-8f0c-505f85347b9d tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Notify callbacks [] for subnet,
before_delete _notify_loop
/opt/stack/old/neutron/neutron/callbacks/manager.py:142
2017-04-07 03:40:34.338 8785 DEBUG neutron.plugins.ml2.plugin
[req-933bd8b3-cd8f-4d2f-8f0c-505f85347b9d tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Ports to auto-deallocate:
set([u'b5ff06a6-4084-4961-b239-9f29aa42c68a']) delete_subnet
/opt/stack/old/neutron/neutron/plugins/ml2/plugin.py:1093
2017-04-07 03:40:34.340 8785 DEBUG neutron.callbacks.manager
[req-933bd8b3-cd8f-4d2f-8f0c-505f85347b9d tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Notify callbacks [] for subnet,
before_delete _notify_loop
/opt/stack/old/neutron/neutron/callbacks/manager.py:142
It goes on like that on and on up until:
2017-04-07 03:41:32.644 8785 DEBUG neutron.plugins.ml2.plugin
[req-933bd8b3-cd8f-4d2f-8f0c-505f85347b9d tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Deleting subnet record delete_subnet
/opt/stack/old/neutron/neutron/plugins/ml2/plugin.py:1145
2017-04-07 03:41:32.644 8785 DEBUG neutron.ipam.driver
[req-933bd8b3-cd8f-4d2f-8f0c-505f85347b9d tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Loading ipam driver: internal get_instance
/opt/stack/old/neutron/neutron/ipam/driver.py:51
2017-04-07 03:41:32.698 8785 DEBUG neutron.plugins.ml2.plugin
[req-933bd8b3-cd8f-4d2f-8f0c-505f85347b9d tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Committing transaction delete_subnet
/opt/stack/old/neutron/neutron/plugins/ml2/plugin.py:1152
Right before the thread is unblocked and makes progress, we see there is
no longer a port to de-allocate:
2017-04-07 03:41:32.421 8785 DEBUG neutron.plugins.ml2.plugin [req-
933bd8b3-cd8f-4d2f-8f0c-505f85347b9d tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Ports to auto-deallocate: set([])
delete_subnet /opt/stack/old/neutron/neutron/plugins/ml2/plugin.py:1093
I think this was unblocked by another cleanup (DELETE) request for the
port that happened just before:
2017-04-07 03:41:31.994 8785 DEBUG neutron.plugins.ml2.plugin [req-
d1dfda92-9b9b-421f-b45f-7ef4746e43c6 tempest-NetworksIpV6Test-1590417059
tempest-NetworksIpV6Test-1590417059] Calling delete_port for
b5ff06a6-4084-4961-b239-9f29aa42c68a owned by network:dhcp delete_
[Yahoo-eng-team] [Bug 1677999] Re: api-ref: flavor information in server response can be empty
Reviewed: https://review.openstack.org/452078 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=af1734b0dd6000e85f765c0084c8c8718ecfc10d Submitter: Jenkins Branch:master commit af1734b0dd6000e85f765c0084c8c8718ecfc10d Author: ghanshyam Date: Fri Mar 31 07:35:17 2017 + Add empty flavor object info in server api-ref In case flavor information is not present in sysmeta then GET/PUT server response can have flavor as empty object. ref- http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/views/servers.py#n252 Having that mentioned in api-ref will be nice to understand it clearly. Closes-Bug: #1677999 Change-Id: I350dc33df0cb03eb86df1f142e58ae34b02a1334 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1677999 Title: api-ref: flavor information in server response can be empty Status in OpenStack Compute (nova): Fix Released Bug description: In case flavor information is not present in sysmeta then GET/PUT server response can have flavor as empty object. ref- http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/views/servers.py#n252 Having that mentioned in api-ref will be nice to understand it clearly. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1677999/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1676039] Re: code comment redundant
Reviewed: https://review.openstack.org/450520 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=5bb705bf7b82407792f81b9132ce82b3f26a7f54 Submitter: Jenkins Branch:master commit 5bb705bf7b82407792f81b9132ce82b3f26a7f54 Author: wanghongxu Date: Tue Mar 28 09:49:00 2017 +0800 code comment redundant Change-Id: I75808f30587c048d83d98cb61de12aaad99667a8 Closes-Bug: #1676039 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1676039 Title: code comment redundant Status in OpenStack Compute (nova): Fix Released Bug description: I am running OpenStack Mitaka on CentOS7.1 with Citrix XenServer 6.5. In function create_image() of nova/virt/xenapi/vm_utils.py file, the following function documentation string: """Creates VDI from the image stored in the local cache. If the image is not present in the cache, it streams it from glance. Returns: A list of dictionaries that describe VDIs """ According to context, I think 'it' word in 'it streams it from glance' sentence should be cancelled To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1676039/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680858] [NEW] test_floatingip_list_with_pagination fails on py3 Newton job
Public bug reported:
ft330.11:
neutron.tests.unit.extensions.test_l3.L3NatDBIntTestCase.test_floatingip_list_with_pagination_StringException:
Empty attachments:
pythonlogging:''
stdout
stderr: {{{
/home/jenkins/workspace/gate-neutron-python35/.tox/py35/lib/python3.5/site-packages/oslo_db/sqlalchemy/enginefacade.py:259:
OsloDBDeprecationWarning: EngineFacade is deprecated; please use
oslo_db.sqlalchemy.enginefacade
self._legacy_facade = LegacyEngineFacade(None, _factory=self)
/home/jenkins/workspace/gate-neutron-python35/.tox/py35/lib/python3.5/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
}}}
Traceback (most recent call last):
File
"/home/jenkins/workspace/gate-neutron-python35/neutron/tests/unit/extensions/test_l3.py",
line 2694, in test_floatingip_list_with_pagination
('floating_ip_address', 'asc'), 2, 2)
File
"/home/jenkins/workspace/gate-neutron-python35/neutron/tests/unit/db/test_db_base_plugin_v2.py",
line 712, in _test_list_with_pagination
self.assertThat(len(res[resources]),
KeyError: 'floatingips'
Example of failed test: http://logs.openstack.org/12/454612/1/check
/gate-neutron-python35/6d500b1/testr_results.html.gz
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22in%20_test_list_with_pagination%5C%22%20AND%20build_name
%3Agate-neutron-
python35%20AND%20build_branch%3A%5C%22stable%2Fnewton%5C%22
** Affects: neutron
Importance: Undecided
Status: New
** Tags: gate-failure
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1680858
Title:
test_floatingip_list_with_pagination fails on py3 Newton job
Status in neutron:
New
Bug description:
ft330.11:
neutron.tests.unit.extensions.test_l3.L3NatDBIntTestCase.test_floatingip_list_with_pagination_StringException:
Empty attachments:
pythonlogging:''
stdout
stderr: {{{
/home/jenkins/workspace/gate-neutron-python35/.tox/py35/lib/python3.5/site-packages/oslo_db/sqlalchemy/enginefacade.py:259:
OsloDBDeprecationWarning: EngineFacade is deprecated; please use
oslo_db.sqlalchemy.enginefacade
self._legacy_facade = LegacyEngineFacade(None, _factory=self)
/home/jenkins/workspace/gate-neutron-python35/.tox/py35/lib/python3.5/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
}}}
Traceback (most recent call last):
File
"/home/jenkins/workspace/gate-neutron-python35/neutron/tests/unit/extensions/test_l3.py",
line 2694, in test_floatingip_list_with_pagination
('floating_ip_address', 'asc'), 2, 2)
File
"/home/jenkins/workspace/gate-neutron-python35/neutron/tests/unit/db/test_db_base_plugin_v2.py",
line 712, in _test_list_with_pagination
self.assertThat(len(res[resources]),
KeyError: 'floatingips'
Example of failed test: http://logs.openstack.org/12/454612/1/check
/gate-neutron-python35/6d500b1/testr_results.html.gz
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22in%20_test_list_with_pagination%5C%22%20AND%20build_name
%3Agate-neutron-
python35%20AND%20build_branch%3A%5C%22stable%2Fnewton%5C%22
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1680858/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680840] [NEW] Some pages have no page title since used the wrong variable.
Public bug reported: Env: devstack master branch ** Affects: horizon Importance: Undecided Assignee: wei.ying (wei.yy) Status: New ** Changed in: horizon Assignee: (unassigned) => wei.ying (wei.yy) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1680840 Title: Some pages have no page title since used the wrong variable. Status in OpenStack Dashboard (Horizon): New Bug description: Env: devstack master branch To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1680840/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1675354] Re: Can't create instance
per above ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1675354 Title: Can't create instance Status in OpenStack Compute (nova): Invalid Bug description: Error trying to create an instance. openstack server create --flavor m1.tiny --image CirrOS_0.3.5_x64_test --nic net-id=716d6ba4-cbc0-4cc6-a86a-19d28306dda2 --security-group test_sg --key-name CirrOS_test provider-instance Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-9961d146-62bb-4ea0-9df2-8fd92d802b39) Initially I was trying to create instances using Horizon, the result was the message "Error: Unable to create the server". Using Mirantis OpenStack Mitaka 9.1 under VMWare with QEmu, LVM and Neutron. nova-api.log is not showing anything about this error or present day (March 23) operations, which I find odd. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1675354/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1678726] Re: vpnaas endpoint related UT failure
Reviewed: https://review.openstack.org/452691
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=9a0907dbb9eaf1dcf7f1ccfc22b0e6e4f775b046
Submitter: Jenkins
Branch:master
commit 9a0907dbb9eaf1dcf7f1ccfc22b0e6e4f775b046
Author: YAMAMOTO Takashi
Date: Mon Apr 3 19:31:32 2017 +0900
Flush objects by ourselves before processing before_commit event
During commit processing, sqla automatically flushes objects.
However, it does so after dispatching the before_commit event,
while Neutron expects it happens before the event. This
counter-intuitive behaviour might or might not be considered
a bug in sqla. Anyway, it's better to be safe in our side.
Closes-Bug: #1678726
Change-Id: Iceaf178be2885b0299d6d281983e9f7f8ae6def0
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1678726
Title:
vpnaas endpoint related UT failure
Status in neutron:
Fix Released
Bug description:
eg.
http://logs.openstack.org/14/445114/10/check/gate-neutron-vpnaas-python27-ubuntu-xenial/c87f6d6/testr_results.html.gz
ft2.11:
neutron_vpnaas.tests.unit.db.vpn.test_vpn_db.TestVpnaas.test_create_ipsec_site_connection_StringException:
Empty attachments:
stdout
pythonlogging:'': {{{ERROR [neutron.api.extensions] Extension path
'neutron/tests/unit/extensions' doesn't exist!}}}
stderr: {{{
/home/jenkins/workspace/gate-neutron-vpnaas-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/paste/deploy/loadwsgi.py:22:
DeprecationWarning: Parameters to load are deprecated. Call .resolve and
.require separately.
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
}}}
Traceback (most recent call last):
File
"/home/jenkins/workspace/gate-neutron-vpnaas-python27-ubuntu-xenial/.tmp/tmp.Q1k56Jlxhb/openstack/neutron/neutron/tests/base.py",
line 116, in func
return f(self, *args, **kwargs)
File "neutron_vpnaas/tests/unit/db/vpn/test_vpn_db.py", line 1214, in
test_create_ipsec_site_connection
self._test_create_ipsec_site_connection(key_overrides=extras)
File "neutron_vpnaas/tests/unit/db/vpn/test_vpn_db.py", line 1207, in
_test_create_ipsec_site_connection
dpd)
File "neutron_vpnaas/tests/unit/db/vpn/test_vpn_db.py", line 410, in
_check_ipsec_site_connection
in ipsec_site_connection.items()
File
"/home/jenkins/workspace/gate-neutron-vpnaas-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 411, in assertEqual
self.assertThat(observed, matcher, message)
File
"/home/jenkins/workspace/gate-neutron-vpnaas-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = {'admin_state_up': True,
'description': 'my-ipsec-connection',
'ikepolicy_id': u'c63f4e69-420b-4cba-9bc6-77dde7e22fd7',
'initiator': 'bi-directional',
'ipsecpolicy_id': u'57074a7b-a9b3-4735-969c-e1ed0a0e3b92',
'mtu': 1500,
'name': 'connection1',
'peer_address': '192.168.1.10',
'peer_cidrs': ['192.168.2.0/24', '192.168.3.0/24'],
'peer_id': '192.168.1.10',
'psk': 'abcd',
'status': 'PENDING_CREATE',
'tenant_id': '46f70361-ba71-4bd0-9769-3573fd227c4b',
'vpnservice_id': u'ac1c2e78-96a0-4f3b-a640-b92820675754'}
actual= {u'admin_state_up': True,
u'description': u'my-ipsec-connection',
u'ikepolicy_id': u'c63f4e69-420b-4cba-9bc6-77dde7e22fd7',
u'initiator': u'bi-directional',
u'ipsecpolicy_id': u'57074a7b-a9b3-4735-969c-e1ed0a0e3b92',
u'mtu': 1500,
u'name': u'connection1',
u'peer_address': u'192.168.1.10',
u'peer_cidrs': [],
u'peer_id': u'192.168.1.10',
u'psk': u'abcd',
u'status': u'PENDING_CREATE',
u'tenant_id': u'46f70361-ba71-4bd0-9769-3573fd227c4b',
u'vpnservice_id': u'ac1c2e78-96a0-4f3b-a640-b92820675754'}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1678726/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680810] [NEW] Error if admin logs in when identity dashboard is not registered.
Public bug reported: If the identity dashboard is not registered in Horizon and an admin user logs in they will get a 'Something went wrong' page and are not able to progress further. Relevant logs: http://paste.openstack.org/raw/605730/ The issue appears to have been introduced when fixing https://bugs.launchpad.net/horizon/+bug/1659818 ** Affects: horizon Importance: Undecided Assignee: Dale Smith (dalees) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Dale Smith (dalees) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1680810 Title: Error if admin logs in when identity dashboard is not registered. Status in OpenStack Dashboard (Horizon): In Progress Bug description: If the identity dashboard is not registered in Horizon and an admin user logs in they will get a 'Something went wrong' page and are not able to progress further. Relevant logs: http://paste.openstack.org/raw/605730/ The issue appears to have been introduced when fixing https://bugs.launchpad.net/horizon/+bug/1659818 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1680810/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680773] [NEW] Migration of a one VM deployed as part of group fails with NoValidHost
Public bug reported: Migrating one VM that got deployed as part of multi-deploy fails with NoValidHost error from scheduler. I'll update this with more info soon enough ** Affects: nova Importance: Undecided Assignee: Arun Mani (arun-mani) Status: New ** Changed in: nova Assignee: (unassigned) => Arun Mani (arun-mani) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1680773 Title: Migration of a one VM deployed as part of group fails with NoValidHost Status in OpenStack Compute (nova): New Bug description: Migrating one VM that got deployed as part of multi-deploy fails with NoValidHost error from scheduler. I'll update this with more info soon enough To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1680773/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680660] Re: empty string server tag can be created
hi Andrey,
try to put tags [""], and then put tags/abc.
Then you with get {"tags":["","abc"]}
And the doc link I mean is:
https://developer.openstack.org/api-ref/compute/?expanded=add-a-single-tag-detail,list-extra-specs-for-a-flavor-detail,list-keypairs-detail,id324-detail,show-console-output-os-getconsoleoutput-action-detail,delete-all-tags-detail,check-tag-existence-detail#server-tags-servers-tags
** Changed in: nova
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1680660
Title:
empty string server tag can be created
Status in OpenStack Compute (nova):
In Progress
Bug description:
Description
===
In compute api description "Server tags (servers, tags)¶
Tag is a non-empty string."
But actually we can create empty string server tags via api Replace Tags:
PUT /servers/{server_id}/tags
Steps to reproduce
==
PUT /servers/{server_id}/tags with empty string
Expected result
===
Fail to create, or we need to modify the api doc
Actual result
=
Update successfully, but api doc says it it not allowed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1680660/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680765] [NEW] (HTTP 500)
Public bug reported:
With Debian 8.6 jessie, and in Newton, when executing the following
command to create a test instance in Openstack (following the official
Openstack newton for debain guide):
openstack server create --flavor m1.nano --image cirros --security-group
default --key-name mykey provider-instance
I get the following error:
Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and
attach the Nova API log if possible.
(HTTP 500) (Request-ID:
req-64808b32-4971-4ab0-8a80-540b1f6cb527)
Here's the nova-api-log as suggested:
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions
[req-ba2fba0c-7800-4886-9837-5d5ab0381eff c70c1c93d7b940dfb4255d8421d12009
5caa95a73f114f0584c9cd8ed3b02d2f - - -] Unexpected exception in API method
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions Traceback
(most recent call last):
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/nova/api/openstack/extensions.py", line 478,
in wrapped
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions return
f(*args, **kwargs)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/images.py", line
87, in show
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions image =
self._image_api.get(context, id)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/nova/image/api.py", line 93, in get
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions
show_deleted=show_deleted)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/nova/image/glance.py", line 333, in show
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions
_reraise_translated_image_exception(image_id)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/nova/image/glance.py", line 682, in
_reraise_translated_image_exception
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions
six.reraise(new_exc, None, exc_trace)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/nova/image/glance.py", line 331, in show
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions image =
self._client.call(context, version, 'get', image_id)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/nova/image/glance.py", line 250, in call
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions result =
getattr(client.images, method)(*args, **kwargs)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/glanceclient/v1/images.py", line 132, in get
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions %
urlparse.quote(str(image_id)))
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line 284, in
head
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions return
self._request('HEAD', url, **kwargs)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line 279, in
_request
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions resp,
body_iter = self._handle_response(resp)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/dist-packages/glanceclient/common/http.py", line 107, in
_handle_response
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions raise
exc.from_response(resp, resp.content)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions
HTTPInternalServerError: HTTPInternalServerError (HTTP 500)
2017-04-07 11:08:06.195 30396 ERROR nova.api.openstack.extensions
2017-04-07 11:08:06.197 30396 INFO nova.api.openstack.wsgi
[req-ba2fba0c-7800-4886-9837-5d5ab0381eff c70c1c93d7b940dfb4255d8421d12009
5caa95a73f114f0584c9cd8ed3b02d2f - - -] HTTP exception thrown: Unexpected API
Error. Please report this at http://bugs.launchpad.net/nova/ and attach the
Nova API log if possible.
2017-04-07 11:08:06.199 30396 INFO nova.osapi_compute.wsgi.server
[req-ba2fba0c-7800-4886-9837-5d5ab0381eff c70c1c93d7b940dfb4255d8421d12009
5caa95a73f114f0584c9cd8ed3b02d2f - - -] 192.168.180.30 "GET
/v2.1/5caa95a73f114f0584c9cd8ed3b02d2f/images/cirros-0.3.4-x86_64-disk.img
HTTP/1.1" status: 500 len: 516 time: 0.3148861
2017-04-07 11:08:06.227 30396 ERROR nova.api.openstack.extensions
[req-1e1f6c53-5a99-4311-92e0-7699209307c3 c70c1c93d7b940dfb4255d8421d12009
5caa95a73f114f0584c9cd8ed3b02d2f - - -] Unexpected exception in API method
2017-04-07 11:08:06.227 30396 ERROR nova.api.openstack.extensi
[Yahoo-eng-team] [Bug 1680761] [NEW] Replace six.iteritems with dict.items
Public bug reported: according to https://wiki.openstack.org/wiki/Python3, now we should avoid using six.iteritems and replace it with dict.items. ** Affects: neutron Importance: Undecided Assignee: fupingxie (fpxie) Status: New ** Changed in: neutron Assignee: (unassigned) => fupingxie (fpxie) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1680761 Title: Replace six.iteritems with dict.items Status in neutron: New Bug description: according to https://wiki.openstack.org/wiki/Python3, now we should avoid using six.iteritems and replace it with dict.items. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1680761/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680660] Re: empty string server tag can be created
Thanks for the report.
What do you mean by empty string? My tests show the following:
put tags [] => no tags created
put tags [''] => u'' is too short
put tags [' '] => ok
Looks like it corresponds with docs. http://ix.io/pTo
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1680660
Title:
empty string server tag can be created
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===
In compute api description "Server tags (servers, tags)¶
Tag is a non-empty string."
But actually we can create empty string server tags via api Replace Tags:
PUT /servers/{server_id}/tags
Steps to reproduce
==
PUT /servers/{server_id}/tags with empty string
Expected result
===
Fail to create, or we need to modify the api doc
Actual result
=
Update successfully, but api doc says it it not allowed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1680660/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680742] [NEW] Replace six.iteritems with dict.items
Public bug reported: according to https://wiki.openstack.org/wiki/Python3, now we should avoid using six.iteritems and replace it with dict.items. ** Affects: glance Importance: Undecided Assignee: fupingxie (fpxie) Status: In Progress ** Changed in: glance Assignee: (unassigned) => fupingxie (fpxie) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1680742 Title: Replace six.iteritems with dict.items Status in Glance: In Progress Bug description: according to https://wiki.openstack.org/wiki/Python3, now we should avoid using six.iteritems and replace it with dict.items. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1680742/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1590049] Re: test_add_list_remove_router_on_l3_agent may fail on envs where there is >= two L3 agents and DVR enabled
Reviewed: https://review.openstack.org/421155
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=08d29e3c90093c508fb8ebc511ca5caca1716379
Submitter: Jenkins
Branch:master
commit 08d29e3c90093c508fb8ebc511ca5caca1716379
Author: Genadi Chereshnya
Date: Tue Jan 17 11:06:42 2017 +0200
Tempest: Fixing L3 agent hosting router for DVR setup
The tests for L3 agent hosting routers were failing in DVR setup
because the code was trying to add router to l3 agent when it was
already there.
Closes-bug: #1590049
Change-Id: I0087ad6f6df662579d557ab790de64e04ff22943
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1590049
Title:
test_add_list_remove_router_on_l3_agent may fail on envs where there
is >= two L3 agents and DVR enabled
Status in neutron:
Fix Released
Status in tempest:
Fix Released
Bug description:
Environment:
OpenStack (Mitaka release), where there is more than one L3 agent and DVR
enabled.
When DVR is disabled, the resource_setup method just creates a router.
When DVR is enabled, the resource_setup method creates a router and
then adds an internal network interface to the created router. After
we added the internal network interface to the router, the router is
automatically hosted by some L3 agent. Then the test starts and tries
to add the router to one of L3 agents and fails because the router is
already hosted by another L3 agent.
tempest.lib.exceptions.Conflict: An object with that identifier already exists
Details: {u'message': u'The router 8569d347-6db4-4e12-b033-60a867ba680f has
been already hosted by the L3 Agent 6250d031-d455-4afe-b993-5a7719815746.',
u'type': u'RouterHostedByL3Agent', u'detail': u''}
The full log can be found here http://paste.openstack.org/show/508686/
A DVR router can be bound to some L3 agent without adding an internal
network interface to the created router since the Mitaka release.
Liberty - http://paste.openstack.org/show/574456/
Mitaka - http://paste.openstack.org/show/574455/
In order to fix the test, we need to remove the code block where we
add the internal network interface to the router, but it will not work
with the Liberty release. So we can skip the test until Liberty is EOL
and after that fix the test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1590049/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1680506] Re: Edit consistency group form has an exception
Reviewed: https://review.openstack.org/454238 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=bfec68032237db3c50227da7a1121698a916b0c8 Submitter: Jenkins Branch:master commit bfec68032237db3c50227da7a1121698a916b0c8 Author: wei.ying Date: Thu Apr 6 23:28:12 2017 +0800 Fix edit consistency group form error If cgroup old description is empty and also judge its length, it will throw an error. We should first whether is empty. Change-Id: Ic89232b22a3d4673b14115e65dd670dded26f0a1 Closes-Bug: 1680506 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1680506 Title: Edit consistency group form has an exception Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Env: devstack master branch If old description is empty and submit edit consistency group form,it will throws an exception. Exception info: [06/Apr/2017 15:16:58] "GET /project/cgroups/671779c1-81de-4354-ac8c-db123f835afa/update/ HTTP/1.1" 200 2175 Internal Server Error: /project/cgroups/671779c1-81de-4354-ac8c-db123f835afa/update/ Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 52, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 36, in dec return view_func(request, *args, **kwargs) File "/opt/stack/horizon/horizon/decorators.py", line 84, in dec return view_func(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/django/views/generic/edit.py", line 214, in post if form.is_valid(): File "/usr/local/lib/python2.7/dist-packages/django/forms/forms.py", line 184, in is_valid return self.is_bound and not self.errors File "/usr/local/lib/python2.7/dist-packages/django/forms/forms.py", line 176, in errors self.full_clean() File "/usr/local/lib/python2.7/dist-packages/django/forms/forms.py", line 393, in full_clean self._clean_form() File "/usr/local/lib/python2.7/dist-packages/django/forms/forms.py", line 417, in _clean_form cleaned_data = self.clean() File "/opt/stack/horizon/openstack_dashboard/dashboards/project/cgroups/forms.py", line 35, in clean if len(old_desc): TypeError: object of type 'NoneType' has no len() To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1680506/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1641250] Re: NG details view route should have different name
Reviewed: https://review.openstack.org/447911 Committed: https://git.openstack.org/cgit/openstack/magnum-ui/commit/?id=cac8f9e0943ed6d529473cae178509e4a7d77af2 Submitter: Jenkins Branch:master commit cac8f9e0943ed6d529473cae178509e4a7d77af2 Author: Shu Muto Date: Tue Mar 21 16:19:56 2017 +0900 Use detailRoute constant for path of details view This patch replaces hard coded "project/ngdetails/" for path of details view to constant using "horizon.app.core.detailRoute". Change-Id: Ia0b0c1db3d2df6c3f459d1254deb974e71824bf7 Closes-Bug: #1641250 ** Changed in: magnum-ui Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1641250 Title: NG details view route should have different name Status in OpenStack Dashboard (Horizon): Fix Released Status in Magnum UI: Fix Released Status in senlin-dashboard: Fix Released Status in UI Cookiecutter: In Progress Status in Zun-UI: Fix Released Bug description: https://github.com/openstack/horizon/blob/master/openstack_dashboard/static/app/core/core.module.js#L56 path includes the name "project" but detail views can also come from "admin" and "identity". Change the name. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1641250/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
