[Yahoo-eng-team] [Bug 1467243] [NEW] Radware LBaaS v2 driver LB deletion fails when no members exist
Public bug reported: Radware defined as a LBaaS v2 provider. LB instance created with or without lister(s)/ pool(s) No members created for LB pool(s) LB is deleted. Radware driver tries to delete LB service on back-end system and fails because no LB is created on back-end system until at least one member is defined for the LB. ** Affects: neutron Importance: Undecided Assignee: Evgeny Fedoruk (evgenyf) Status: New ** Tags: lbaas radware ** Tags added: lbaas radware ** Changed in: neutron Assignee: (unassigned) = Evgeny Fedoruk (evgenyf) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1467243 Title: Radware LBaaS v2 driver LB deletion fails when no members exist Status in OpenStack Neutron (virtual network service): New Bug description: Radware defined as a LBaaS v2 provider. LB instance created with or without lister(s)/ pool(s) No members created for LB pool(s) LB is deleted. Radware driver tries to delete LB service on back-end system and fails because no LB is created on back-end system until at least one member is defined for the LB. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1467243/+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 1467275] [NEW] Full stack tests should run in their own job
Public bug reported: tox -e dsvm-functional currently runs both functional and fullstack tests, because of this piece of code: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/functional/__init__.py This means that functional and fullstack tests can run in parallel in different workers. This is causing bad interaction as evident from this run: http://logs.openstack.org/32/190832/6/check/check-neutron-dsvm-functional/b977f76/ I think that this sort of interaction is to be expected, and it's not worth trying to fix it. I think that fullstack tests should run in a separate job. ** Affects: neutron Importance: High Assignee: Assaf Muller (amuller) Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1467275 Title: Full stack tests should run in their own job Status in OpenStack Neutron (virtual network service): New Bug description: tox -e dsvm-functional currently runs both functional and fullstack tests, because of this piece of code: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/functional/__init__.py This means that functional and fullstack tests can run in parallel in different workers. This is causing bad interaction as evident from this run: http://logs.openstack.org/32/190832/6/check/check-neutron-dsvm-functional/b977f76/ I think that this sort of interaction is to be expected, and it's not worth trying to fix it. I think that fullstack tests should run in a separate job. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1467275/+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 1212581] Re: ec2 api doesn't respect reclaim_instance_interval from nova.conf
standalone ec2-api project doesn't have such bug because it works through piblic Nova API. ** No longer affects: ec2-api -- 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/1212581 Title: ec2 api doesn't respect reclaim_instance_interval from nova.conf Status in OpenStack Compute (Nova): Confirmed Bug description: When a user, uses the ec2 api to delete an instance the check whether the instance should be soft-deleted isn't done. This logic is current in api/nova/ and not in api/ec2. I expected the ec2 api to have the same behavior. We currently lost user data because of this. Would be nice to have compute/api.y only a contain a single delete function which does the checking whether to soft-delete or not instead of doing it in the api level. Impact: High To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1212581/+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 1445871] Re: Deleted port that was created manually by the user, when detach_interface
[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/1445871 Title: Deleted port that was created manually by the user, when detach_interface Status in OpenStack Compute (Nova): Expired Bug description: Deleted port that was created manually by the user, when detach_interface. If we need to add an attribute to the port, to show that it is created individually by the user or automatically created? To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1445871/+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
