[Yahoo-eng-team] [Bug 1719183] [NEW] [API] Creating router with external_gateway_info creates security group with empty tenant_id field
Public bug reported:
1) Run a test from test_security_groups.py in tempest neutron plugin git (For
example use neutron/tests/tempest/scenario/test_security_groups.py path and run
test_protocol_number_rule)
2) After network creation the first security group is created (for test tenant)
3) After router creation for some reason another security group is created when
the tenant_id field is empty.
4) The following is sent when this behavior occurs:
uri:
'v2.0/routers'
body:
'{"router": {"external_gateway_info": {"network_id":
"efa041d4-eed7-46e9-8373-714a1bc9175a"}, "name": "tempest-router-1046611578",
"admin_state_up": true}}'
Removing "external_gateway_info" filed from body solves the problem and
no new security group is created (as expected)
** Affects: neutron
Importance: Undecided
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/1719183
Title:
[API] Creating router with external_gateway_info creates security
group with empty tenant_id field
Status in neutron:
New
Bug description:
1) Run a test from test_security_groups.py in tempest neutron plugin git (For
example use neutron/tests/tempest/scenario/test_security_groups.py path and run
test_protocol_number_rule)
2) After network creation the first security group is created (for test
tenant)
3) After router creation for some reason another security group is created
when the tenant_id field is empty.
4) The following is sent when this behavior occurs:
uri:
'v2.0/routers'
body:
'{"router": {"external_gateway_info": {"network_id":
"efa041d4-eed7-46e9-8373-714a1bc9175a"}, "name": "tempest-router-1046611578",
"admin_state_up": true}}'
Removing "external_gateway_info" filed from body solves the problem
and no new security group is created (as expected)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1719183/+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 1662462] [NEW] The automation tests for L3 agent hosting routers fail in DVR setup
Public bug reported:
The failing test is "test_add_list_remove_router_on_l3_agent" in
neutron/tests/tempest/api/admin/test_l3_agent_scheduler.py
The test suite's setUp creates a router and if it's a dvr router (which
it is in this case) it also uses 'router-gateway-set' to ensure it's
scheduled. Then, the test itself tries to schedule the router to an
agent. This will fail if the agent that was scheduled to during setUp is
different than the one that's attempted to be scheduled to during the
test itself.
In other words, the test is faulty in that it should know that the
router is already scheduled.
The failure happens in Mitaka and Neuton version when running on DVR
setup
** Affects: neutron
Importance: Undecided
Assignee: Gena (gcheresh)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1662462
Title:
The automation tests for L3 agent hosting routers fail in DVR setup
Status in neutron:
In Progress
Bug description:
The failing test is "test_add_list_remove_router_on_l3_agent" in
neutron/tests/tempest/api/admin/test_l3_agent_scheduler.py
The test suite's setUp creates a router and if it's a dvr router
(which it is in this case) it also uses 'router-gateway-set' to ensure
it's scheduled. Then, the test itself tries to schedule the router to
an agent. This will fail if the agent that was scheduled to during
setUp is different than the one that's attempted to be scheduled to
during the test itself.
In other words, the test is faulty in that it should know that the
router is already scheduled.
The failure happens in Mitaka and Neuton version when running on DVR
setup
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1662462/+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 1655917] Re: Revision is not increased when updating "network router:external"
** Changed in: neutron Status: Invalid => 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/1655917 Title: Revision is not increased when updating "network router:external" Status in neutron: New Bug description: Try to update the network field router:external we expect the revision number to be increased, but it doesn't. Run "neutron net-update moshe --router:external=True" command for new network. The field router-external is updated but the revision number is not increased. Tested on Newton version (10) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1655917/+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 1655917] [NEW] Revision is not increased when updating "network router:external"
Public bug reported: Try to update the network field router:external we expect the revision number to be increased, but it doesn't. Run "neutron net-update moshe --router:external=True" command for new network. The field router-external is updated but the revision number is not increased. Tested on Newton version (10) ** Affects: neutron Importance: Undecided 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/1655917 Title: Revision is not increased when updating "network router:external" Status in neutron: New Bug description: Try to update the network field router:external we expect the revision number to be increased, but it doesn't. Run "neutron net-update moshe --router:external=True" command for new network. The field router-external is updated but the revision number is not increased. Tested on Newton version (10) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1655917/+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 1654991] [NEW] Update of DVR router to be HA fails with 'HAmodeUpdateOfDvrNotSupported'
Public bug reported:
Though the creation of DVR HA router succeeds, it's impossible to "update"
router to be DVR and HA
Trying to update DVR router to be HA you get:
501-{u'NotImplementedError': {u'message': u'', u'type':
u'HAmodeUpdateOfDvrNotSupported', u'detail': u''}}
Neutron server returns request_ids: ['req-d0727fec-3112-4d2b-9f67-d23cf78e4c5f']
** Affects: neutron
Importance: Undecided
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/1654991
Title:
Update of DVR router to be HA fails with
'HAmodeUpdateOfDvrNotSupported'
Status in neutron:
New
Bug description:
Though the creation of DVR HA router succeeds, it's impossible to "update"
router to be DVR and HA
Trying to update DVR router to be HA you get:
501-{u'NotImplementedError': {u'message': u'', u'type':
u'HAmodeUpdateOfDvrNotSupported', u'detail': u''}}
Neutron server returns request_ids:
['req-d0727fec-3112-4d2b-9f67-d23cf78e4c5f']
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1654991/+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 1640174] Re: Incorrect error message when creating port with DNS in Neuton and the extension is not configured
Got it, maybe I'll upload a patch later on with the fix to the message that the extension is missing, for now closing this bug ** Changed in: neutron Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1640174 Title: Incorrect error message when creating port with DNS in Neuton and the extension is not configured Status in neutron: Invalid Bug description: Trying to create a port with dns-name in neutron using the following command: 'neutron port-create --dns-name="moshe"' creates a port for that network with empty dns-name Testing with neutron port-show shows empty dns-name To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1640174/+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 1640174] [NEW] Providing dns_name as a port-create parameter creates a port with empty dns-name parameter
Public bug reported: Trying to create a port with dns-name in neutron using the following command: 'neutron port-create --dns-name="moshe"' creates a port for that network with empty dns-name Testing with neutron port-show shows empty dns-name ** Affects: neutron Importance: Undecided 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/1640174 Title: Providing dns_name as a port-create parameter creates a port with empty dns-name parameter Status in neutron: New Bug description: Trying to create a port with dns-name in neutron using the following command: 'neutron port-create --dns-name="moshe"' creates a port for that network with empty dns-name Testing with neutron port-show shows empty dns-name To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1640174/+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
