[Yahoo-eng-team] [Bug 1988542] Re: [RFE] OVN support for vnic type virtio-forwarder
Reviewed: https://review.opendev.org/c/openstack/neutron/+/856441 Committed: https://opendev.org/openstack/neutron/commit/3cf4899cf0d6a4868f7ac6ac86451b06360abcef Submitter: "Zuul (22348)" Branch:master commit 3cf4899cf0d6a4868f7ac6ac86451b06360abcef Author: Yifan Li Date: Thu Sep 8 16:45:46 2022 +0800 [OVN] Adding support for VNIC type virtio-forwarder. The virtio-forwarder related code has already been written in other neutron components except OVN. Added logic solving virtio-forwarder in OVN plugin.Add unit tests of virtio-forwarder VNIC type. Test cases include test_create_port_with_vnic_virtio_forwarder, test_bind_virtio_forwarder_port_geneve, test_bind_virtio_forwarder_port_vxlan. Closes-Bug: #1988542 Change-Id: I80f32db761f5813409c6f789177b2fdebf643305 ** 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/1988542 Title: [RFE] OVN support for vnic type virtio-forwarder Status in neutron: Fix Released Bug description: Problem Description The current neutron OVN plugin does not supports vnic type virtio-forwarder, which is supported by Nova. Reference: https://specs.openstack.org/openstack/nova-specs/specs/pike/implemented/netronome-smartnic-enablement.html Proposed Change Implement the functionality of supporting vnic type virtio-forwarder in neutron OVN mech driver. The neutron will generate a detailed vif and send it to nova when a virtio-forwarder vnic is requested. The existing vnic types support in OVN plugin will not be impacted. Other network plugins also will not be impacted. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1988542/+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 1856364] Re: docs: multistore no longer experimental
** Changed in: glance Status: Triaged => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1856364 Title: docs: multistore no longer experimental Status in Glance: Fix Released Bug description: As of today (13 Dec 2019) the api-ref contains a note that the Glance multistore feature is experimental. It became fully supported in Train. Need to fix this in the api-ref and also look through the administration guide and configuration guide to make sure multistore is no longer described as experimental. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1856364/+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 2017698] [NEW] Description of Image in metadata is overwritten by description of Image in Image Details
Public bug reported: We have two places to edit image definition: one in Edit Image -> Image Detail section, and another is in Edit Image -> Metadata. If the definition is empty, it doesn't appear in Metadata section, but if it is not, we have two places to edit it, and the one from Image Detail overwrites the one from Metadata (even if you delete it from Metadata). ** Affects: horizon Importance: Low Assignee: Tatiana Ovchinnikova (tmazur) Status: New ** Changed in: horizon Importance: Undecided => Low ** Changed in: horizon Assignee: (unassigned) => Tatiana Ovchinnikova (tmazur) -- 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/2017698 Title: Description of Image in metadata is overwritten by description of Image in Image Details Status in OpenStack Dashboard (Horizon): New Bug description: We have two places to edit image definition: one in Edit Image -> Image Detail section, and another is in Edit Image -> Metadata. If the definition is empty, it doesn't appear in Metadata section, but if it is not, we have two places to edit it, and the one from Image Detail overwrites the one from Metadata (even if you delete it from Metadata). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/2017698/+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 2017695] Re: User assigned admin role gets 403 when querying various object types.
Re-assigning to the keystone identity package. ** Also affects: keystone Importance: Undecided Status: New ** Changed in: keystone (Juju Charms Collection) Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/2017695 Title: User assigned admin role gets 403 when querying various object types. Status in OpenStack Identity (keystone): Incomplete Status in keystone package in Juju Charms Collection: Invalid Bug description: Our users, having been assigned admin role on domain and projects in that domain we're unable to query certain things via the openstack CLI. Ex: $ openstack user list You are not authorized to perform the requested action: identity:list_users. (HTTP 403) (Request-ID: req-0c479c91-636d-4b74-b4d1-d18bd1ca4761) $ openstack group list You are not authorized to perform the requested action: identity:list_groups. (HTTP 403) (Request-ID: req-c10c217b-a730-4b8c-90f2-daad2d9dc4cb) $ openstack domain list You are not authorized to perform the requested action: identity:list_domains. (HTTP 403) (Request-ID: req-5b1d5007-f9dd-4149-bc1c-182f7a0c88b2) $ openstack role assignment list You are not authorized to perform the requested action: identity:list_role_assignments. (HTTP 403) (Request-ID: req-a10ff2cb-cb24-4447-b962-6e8b6bd8afd9) I can view projects however... which is interesting. Our users are granted admin on the domain and projects via group membership. We're running keystone 17.0.1 in Ussuri. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/2017695/+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 2017680] [NEW] Tenant user cannot delete a port associated with an FIP belonging to the admin tenant
Public bug reported: When a tenant A creates a port but an admin associated a FIP to that port. At this point, tenant A cannot delete the port, because a foreign key relation with the FIP (500 server error). 2023-04-14 10:01:49.116 277 ERROR neutron.pecan_wsgi.hooks.translation pymysql.err.IntegrityError: (1451, 'Cannot delete or update a parent row: a foreign key constraint fails (`ovs_neutron`.`floatingips`, CONSTRAINT `floatingips_ibfk_1` FOREIGN KEY (`fixed_port_id`) REFERENCES `ports` (`id`))') Basically the issue is the user is not allowed to disassociate the port from the FIP, ** Affects: neutron Importance: Undecided Assignee: Fernando Royo (froyoredhat) Status: New ** Changed in: neutron Assignee: (unassigned) => Fernando Royo (froyoredhat) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2017680 Title: Tenant user cannot delete a port associated with an FIP belonging to the admin tenant Status in neutron: New Bug description: When a tenant A creates a port but an admin associated a FIP to that port. At this point, tenant A cannot delete the port, because a foreign key relation with the FIP (500 server error). 2023-04-14 10:01:49.116 277 ERROR neutron.pecan_wsgi.hooks.translation pymysql.err.IntegrityError: (1451, 'Cannot delete or update a parent row: a foreign key constraint fails (`ovs_neutron`.`floatingips`, CONSTRAINT `floatingips_ibfk_1` FOREIGN KEY (`fixed_port_id`) REFERENCES `ports` (`id`))') Basically the issue is the user is not allowed to disassociate the port from the FIP, To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2017680/+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 2016504] Re: [rfe]Support specify fixed_ip_address for DHCP or Metadata port
Hello Liu: In ML2/OVN, you can modify the metadata port IP addresses, if needed. The metadata port is created when the network is; the IP address is assigned when the first subnet is created. Only after this second action, you can assign a new IP address. How do you plan to define a IP address for the metadata port before creating the network or the subnet? Regards. ** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2016504 Title: [rfe]Support specify fixed_ip_address for DHCP or Metadata port Status in neutron: Opinion Bug description: Currently, the IP address of the DHCP port is automatically assigned the first available IP and cannot be specified when creating a subnet. Therefore, can we provide an API that supports specifying the DHCP address when creating a subnet? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2016504/+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 1749574] Re: [tracking] removal and migration of pycrypto
Closing out bugs created before migration to StoryBoard. Please re-open if you are of the opinion it is still current. ** Changed in: barbican 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/1749574 Title: [tracking] removal and migration of pycrypto Status in Barbican: Fix Released Status in Compass: New Status in daisycloud: New Status in OpenStack Backup/Restore and DR (Freezer): New Status in Fuel for OpenStack: New Status in OpenStack Compute (nova): Triaged Status in openstack-ansible: Fix Released Status in OpenStack Global Requirements: Fix Released Status in pyghmi: Fix Committed Status in Solum: Fix Released Status in Tatu: New Status in OpenStack DBaaS (Trove): Fix Released Bug description: trove tatu barbican compass daisycloud freezer fuel nova openstack-ansible - https://review.openstack.org/544516 pyghmi - https://review.openstack.org/569073 solum To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1749574/+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 1818649] Re: [pike] neutron-lbaasv2 with barbican error: LookupError: Container XXXXX could not be found
Closing out bugs created before migration to StoryBoard. Please re-open if you are of the opinion it is still current. ** Changed in: barbican Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1818649 Title: [pike] neutron-lbaasv2 with barbican error: LookupError: Container X could not be found Status in Barbican: Won't Fix Status in neutron: Invalid Bug description: Is there any configuration method about neutron_lbaasv2?. this problem troubled me a long time, the doc is not very well. my lbaas'es config file has been changed many times, but it didn't work. my openstack version is pike. It was relate to https://bugs.launchpad.net/barbican/+bug/1689846, but my environment is lbaasv2, not octavia. I tried create tls listener throuth through lbaasv2, there will be a right response on CLI. And neutron-server.log was all right, but there will be an ERROR in lbaas-agent.log, the log is bellow. 2019-03-05 18:47:52.427 14045 INFO neutron_lbaas.common.cert_manager.barbican_cert_manager [req-6e0b798e-b10c-4132-8665-dfe1122133bb cdb0fbe60ff84eaf932ba6a90dd030b2 502990c9fd4d442693e8d818b01051b5 - - -] Loading certificate container http://192.168.10.10:9311/v1/containers/25670926-0f89-42b6-9fe6-05083d59736a from Barbican. 2019-03-05 18:47:52.428 14045 DEBUG barbicanclient.v1.containers [req-6e0b798e-b10c-4132-8665-dfe1122133bb cdb0fbe60ff84eaf932ba6a90dd030b2 502990c9fd4d442693e8d818b01051b5 - - -] Getting container - Container href: http://192.168.10.10:9311/v1/containers/25670926-0f89-42b6-9fe6-05083d59736a get /usr/lib/python2.7/site-packages/barbicanclient/v1/containers.py:537 2019-03-05 18:47:52.429 14045 ERROR neutron_lbaas.common.cert_manager.barbican_cert_manager [req-6e0b798e-b10c-4132-8665-dfe1122133bb cdb0fbe60ff84eaf932ba6a90dd030b2 502990c9fd4d442693e8d818b01051b5 - - -] Error getting http://192.168.10.10:9311/v1/containers/25670926-0f89-42b6-9fe6-05083d59736a: LookupError: Container http://192.168.10.10:9311/v1/containers/25670926-0f89-42b6-9fe6-05083d59736a could not be found. 2019-03-05 18:47:52.429 14045 ERROR neutron_lbaas.common.cert_manager.barbican_cert_manager Traceback (most recent call last): 2019-03-05 18:47:52.429 14045 ERROR neutron_lbaas.common.cert_manager.barbican_cert_manager File "/usr/lib/python2.7/site-packages/neutron_lbaas/common/cert_manager/barbican_cert_manager.py", line 174, in get_cert 2019-03-05 18:47:52.429 14045 ERROR neutron_lbaas.common.cert_manager.barbican_cert_manager container_ref=cert_ref 2019-03-05 18:47:52.429 14045 ERROR neutron_lbaas.common.cert_manager.barbican_cert_manager File "/usr/lib/python2.7/site-packages/barbicanclient/v1/containers.py", line 543, in get 2019-03-05 18:47:52.429 14045 ERROR neutron_lbaas.common.cert_manager.barbican_cert_manager .format(container_ref)) 2019-03-05 18:47:52.429 14045 ERROR neutron_lbaas.common.cert_manager.barbican_cert_manager LookupError: Container http://192.168.10.10:9311/v1/containers/25670926-0f89-42b6-9fe6-05083d59736a could not be found. 2019-03-05 18:47:52.429 14045 ERROR neutron_lbaas.common.cert_manager.barbican_cert_manager 2019-03-05 18:47:52.430 14045 DEBUG oslo_concurrency.lockutils [req-6e0b798e-b10c-4132-8665-dfe1122133bb cdb0fbe60ff84eaf932ba6a90dd030b2 502990c9fd4d442693e8d818b01051b5 - - -] Lock "haproxy-driver" released by "neutron_lbaas.drivers.haproxy.namespace_driver.deploy_instance" :: held 2.682s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:282 2019-03-05 18:47:52.430 14045 ERROR neutron_lbaas.agent.agent_manager [req-6e0b798e-b10c-4132-8665-dfe1122133bb cdb0fbe60ff84eaf932ba6a90dd030b2 502990c9fd4d442693e8d818b01051b5 - - -] Create listener 73a3aacc-3e81-4cee-aec9-1f0fa9cb61ca failed on device driver haproxy_ns: LookupError: Container http://192.168.10.10:9311/v1/containers/25670926-0f89-42b6-9fe6-05083d59736a could not be found. 2019-03-05 18:47:52.430 14045 ERROR neutron_lbaas.agent.agent_manager Traceback (most recent call last): 2019-03-05 18:47:52.430 14045 ERROR neutron_lbaas.agent.agent_manager File "/usr/lib/python2.7/site-packages/neutron_lbaas/agent/agent_manager.py", line 303, in create_listener 2019-03-05 18:47:52.430 14045 ERROR neutron_lbaas.agent.agent_manager driver.listener.create(listener) 2019-03-05 18:47:52.430 14045 ERROR neutron_lbaas.agent.agent_manager File "/usr/lib/python2.7/site-packages/neutron_lbaas/drivers/haproxy/namespace_driver.py", line 480, in create 2019-03-05 18:47:52.430 14045 ERROR neutron_lbaas.agent.agent_manager self.driver.loadbalancer.refresh(listener.loadbalancer) 2019-03-05 18:47:52.430 14045 ERROR
[Yahoo-eng-team] [Bug 2016414] Re: Message when creating new neutron bugs has outdated links
** Changed in: neutron Status: Fix Committed => Confirmed ** Changed in: neutron Status: Confirmed => 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/2016414 Title: Message when creating new neutron bugs has outdated links Status in neutron: Fix Released Bug description: When creating a new neutron bug, this info message is shown: -+-+-+- Thanks for reporting a bug, the Neutron team loves you! Please check our defect management process, to see what to expect next: http://docs.openstack.org/developer/neutron/policies/bugs.html#bug-triage-process http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements -+-+-+- Both of these links are outdated, they simply redirect to the top- level neutron docs. These would seem to be the matching current links: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#bug-triage-process https://docs.openstack.org/neutron/latest/contributor/policies/blueprints.html#neutron-request-for-feature-enhancements To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2016414/+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
