[Yahoo-eng-team] [Bug 1577987] [NEW] neutron-lbaas v2 - update pool's session_persistence to None fails
Public bug reported:
When updating a pool's session_persistence to None, I get the following
error: Invalid input for session_persistence
1. Create a loadbalancer, listener
2. Create a pool with default args:
using postman:
{
"pool": {
"name": "pool1",
"description": "simple pool",
"listener_id": "39de4d56-d663-46e5-85a1-5b9d5fa17829",
"lb_algorithm": "ROUND_ROBIN",
"protocol": "HTTP",
"session_persistence": {
"type": "APP_COOKIE",
"cookie_name": "my_cookie"
},
"admin_state_up": true
}
}
Update pool with below data:
{
"pool": {
"session_persistence": {"type": ""}
}
}
neutron-server logs:
2016-05-03 16:39:54.698 DEBUG neutron.wsgi [-] (66382) accepted
('192.168.109.128', 58400) from (pid=66382) server
/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py:867
2016-05-03 16:39:55.025 DEBUG neutron.api.v2.base
[req-78bc175f-374d-403c-b5a5-845d4bc79632 admin
be81e9163d074036913aa52b1b9785a7] Request body: {u'pool':
{u'session_persistence': {u'type': u''}}} from (pid=66382) prepare_request_body
/opt/stack/neutron/neutron/api/v2/base.py:658
2016-05-03 16:39:55.025 DEBUG neutron_lib.api.validators
[req-78bc175f-374d-403c-b5a5-845d4bc79632 admin
be81e9163d074036913aa52b1b9785a7] ' ' is not in ('SOURCE_IP', 'HTTP_COOKIE',
'APP_COOKIE') from (pid=66382) validate_values
/usr/local/lib/python2.7/dist-packages/neutron_lib/api/validators.py:91
2016-05-03 16:39:55.026 INFO neutron.api.v2.resource
[req-78bc175f-374d-403c-b5a5-845d4bc79632 admin
be81e9163d074036913aa52b1b9785a7] update failed (client error): Invalid input
for session_persistence. Reason: '' is not in ('SOURCE_IP', 'HTTP_COOKIE',
'APP_COOKIE').
2016-05-03 16:39:55.027 INFO neutron.wsgi
[req-78bc175f-374d-403c-b5a5-845d4bc79632 admin
be81e9163d074036913aa52b1b9785a7] 192.168.109.128 - - [03/May/2016 16:39:55]
"PUT /v2.0/lbaas/pools/aa341feb-ff6f-4d87-a613-52812c665bc0 HTTP/1.1" 400 400
0.327893
using CLI:
neutron lbaas-pool-update pool1 --session_persistence type=dict type=none
Invalid input for session_persistence. Reason: 'none' is not in ('SOURCE_IP',
'HTTP_COOKIE', 'APP_COOKIE').
Neutron server returns request_ids: ['req-93cc8a21-4243-4498-899c-fc9646cddb71']
neutron-server logs:
2016-05-03 16:41:31.834 DEBUG
neutron_lbaas.drivers.octavia.octavia_messaging_consumer [-] Received event
from stream {u'info_type': u'listener_stats', u'info_id':
u'04c16cac-b748-47a6-975f-b109bd80a419', u'info_payload': {u'bytes_in': 0,
u'total_connections': 0, u'active_connections': 0, u'bytes_out': 0}} from
(pid=66202) update_info
/opt/stack/neutron-lbaas/neutron_lbaas/drivers/octavia/octavia_messaging_consumer.py:74
2016-05-03 16:41:34.571 DEBUG neutron.wsgi [-] (66383) accepted
('192.168.109.128', 59130) from (pid=66383) server
/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py:867
2016-05-03 16:41:35.079 INFO neutron.wsgi
[req-695f0831-c84d-43b3-ae37-764cd4a4fd9c admin
be81e9163d074036913aa52b1b9785a7] 192.168.109.128 - - [03/May/2016 16:41:35]
"GET /v2.0/lbaas/pools.json?fields=id=pool1 HTTP/1.1" 200 607 0.506676
2016-05-03 16:41:35.333 DEBUG neutron.api.v2.base
[req-93cc8a21-4243-4498-899c-fc9646cddb71 admin
be81e9163d074036913aa52b1b9785a7] Request body: {u'pool':
{u'session_persistence': {u'type': u'none'}}} from (pid=66383)
prepare_request_body /opt/stack/neutron/neutron/api/v2/base.py:658
2016-05-03 16:41:35.335 DEBUG neutron_lib.api.validators
[req-93cc8a21-4243-4498-899c-fc9646cddb71 admin
be81e9163d074036913aa52b1b9785a7] 'none' is not in ('SOURCE_IP', 'HTTP_COOKIE',
'APP_COOKIE') from (pid=66383) validate_values
/usr/local/lib/python2.7/dist-packages/neutron_lib/api/validators.py:91
2016-05-03 16:41:35.336 INFO neutron.api.v2.resource
[req-93cc8a21-4243-4498-899c-fc9646cddb71 admin
be81e9163d074036913aa52b1b9785a7] update failed (client error): Invalid input
for session_persistence. Reason: 'none' is not in ('SOURCE_IP', 'HTTP_COOKIE',
'APP_COOKIE').
2016-05-03 16:41:35.342 INFO neutron.wsgi
[req-93cc8a21-4243-4498-899c-fc9646cddb71 admin
be81e9163d074036913aa52b1b9785a7] 192.168.109.128 - - [03/May/2016 16:41:35]
"PUT /v2.0/lbaas/pools/aa341feb-ff6f-4d87-a613-52812c665bc0.json HTTP/1.1" 400
403 0.258400
2016-05-03 16:41:36.258 DEBUG oslo_messaging._drivers.amqpdriver [-] received
message msg_id: None reply to None from (pid=66384) __call__
/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:201
** Affects: neutron
Importance: Undecided
Status: New
** Tags: lbaas
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1577987
Title:
neutron-lbaas v2 - update pool's session_persistence to None fails
Status in neutron:
New
Bug description:
When updating a pool's session_persistence to None, I get the
following error: Invalid
[Yahoo-eng-team] [Bug 1558289] [NEW] Installing neutron_lbaas plugin via devstack fails because of incorrect image/package. Change devstack-trusty to ubuntu-trusty to support infra migration
Public bug reported: devstack-trusty image is replaced by ubuntu-trusty as in [1]. However the same is reflected in [2] Change the plugin [3] in neutron-lbaas, to reflect the change. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/088832.html [2] https://review.openstack.org/#/c/292573/ [3] https://github.com/openstack/neutron-lbaas/blob/master/devstack/plugin.sh ** Affects: neutron Importance: Undecided Assignee: Madhusudhan Kandadai (madhusudhan-kandadai) Status: In Progress ** Tags: lbaas ** Changed in: neutron Assignee: (unassigned) => Madhusudhan Kandadai (madhusudhan-kandadai) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1558289 Title: Installing neutron_lbaas plugin via devstack fails because of incorrect image/package. Change devstack-trusty to ubuntu-trusty to support infra migration Status in neutron: In Progress Bug description: devstack-trusty image is replaced by ubuntu-trusty as in [1]. However the same is reflected in [2] Change the plugin [3] in neutron-lbaas, to reflect the change. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/088832.html [2] https://review.openstack.org/#/c/292573/ [3] https://github.com/openstack/neutron-lbaas/blob/master/devstack/plugin.sh To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1558289/+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 1548520] [NEW] FWaaS: .tox/dsvm-functional/bin/subunit-1to2: No such file or directory
Public bug reported: when running dsvm-functional tests at gate, it throws an error with the following: 2016-02-20 01:24:16.504 | 2016-02-20 01:24:16.485 | -- --- 2016-02-20 01:24:16.539 | 2016-02-20 01:24:16.519 | neutron_fwaas.tests.functional.test_fwaas_driver.TestFWaaSDriver.test_status_reporting 0.170 2016-02-20 01:24:16.547 | 2016-02-20 01:24:16.522 | ___ summary 2016-02-20 01:24:16.549 | 2016-02-20 01:24:16.530 | dsvm-functional: commands succeeded 2016-02-20 01:24:16.555 | 2016-02-20 01:24:16.537 | congratulations :) 2016-02-20 01:24:16.562 | 2016-02-20 01:24:16.543 | + testr_exit_code=0 2016-02-20 01:24:16.565 | 2016-02-20 01:24:16.546 | + set -e 2016-02-20 01:24:16.566 | 2016-02-20 01:24:16.548 | + generate_testr_results 2016-02-20 01:24:16.596 | 2016-02-20 01:24:16.550 | + sudo -H -u stack chmod o+rw . 2016-02-20 01:24:16.596 | 2016-02-20 01:24:16.551 | + sudo -H -u stack chmod o+rw -R .testrepository 2016-02-20 01:24:16.597 | 2016-02-20 01:24:16.553 | + '[' -f .testrepository/0 ']' 2016-02-20 01:24:16.597 | 2016-02-20 01:24:16.560 | + .tox/dsvm-functional/bin/subunit-1to2 2016-02-20 01:24:16.597 | + return 1 2016-02-20 01:24:16.597 | 2016-02-20 01:24:16.563 | /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/post_test_hook.sh: line 14: .tox/dsvm-functional/bin/subunit-1to2: No such file or directory 2016-02-20 01:24:16.597 | + local ret_val=1 2016-02-20 01:24:16.597 | + sudo mv /home/jenkins/workspace/gate-neutron-fwaas-dsvm-api/devstack-gate-post_test_hook.txt /opt/stack/logs/ Set the 'env' correctly in tox.ini to make it work. ** Affects: neutron Importance: Undecided Assignee: Madhusudhan Kandadai (madhusudhan-kandadai) Status: In Progress ** Tags: fwaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1548520 Title: FWaaS: .tox/dsvm-functional/bin/subunit-1to2: No such file or directory Status in neutron: In Progress Bug description: when running dsvm-functional tests at gate, it throws an error with the following: 2016-02-20 01:24:16.504 | 2016-02-20 01:24:16.485 | -- --- 2016-02-20 01:24:16.539 | 2016-02-20 01:24:16.519 | neutron_fwaas.tests.functional.test_fwaas_driver.TestFWaaSDriver.test_status_reporting 0.170 2016-02-20 01:24:16.547 | 2016-02-20 01:24:16.522 | ___ summary 2016-02-20 01:24:16.549 | 2016-02-20 01:24:16.530 | dsvm-functional: commands succeeded 2016-02-20 01:24:16.555 | 2016-02-20 01:24:16.537 | congratulations :) 2016-02-20 01:24:16.562 | 2016-02-20 01:24:16.543 | + testr_exit_code=0 2016-02-20 01:24:16.565 | 2016-02-20 01:24:16.546 | + set -e 2016-02-20 01:24:16.566 | 2016-02-20 01:24:16.548 | + generate_testr_results 2016-02-20 01:24:16.596 | 2016-02-20 01:24:16.550 | + sudo -H -u stack chmod o+rw . 2016-02-20 01:24:16.596 | 2016-02-20 01:24:16.551 | + sudo -H -u stack chmod o+rw -R .testrepository 2016-02-20 01:24:16.597 | 2016-02-20 01:24:16.553 | + '[' -f .testrepository/0 ']' 2016-02-20 01:24:16.597 | 2016-02-20 01:24:16.560 | + .tox/dsvm-functional/bin/subunit-1to2 2016-02-20 01:24:16.597 | + return 1 2016-02-20 01:24:16.597 | 2016-02-20 01:24:16.563 | /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/post_test_hook.sh: line 14: .tox/dsvm-functional/bin/subunit-1to2: No such file or directory 2016-02-20 01:24:16.597 | + local ret_val=1 2016-02-20 01:24:16.597 | + sudo mv /home/jenkins/workspace/gate-neutron-fwaas-dsvm-api/devstack-gate-post_test_hook.txt /opt/stack/logs/ Set the 'env' correctly in tox.ini to make it work. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1548520/+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 1544799] [NEW] FWaaS: Pick/install the right sql database to store user and data in each backend
Public bug reported: This is odd when looking at https://github.com/openstack/neutron- fwaas/blob/master/neutron_fwaas/tests/contrib/gate_hook.sh. https://jenkins05.openstack.org/job/gate-neutron-fwaas-dsvm- api/2/consoleFull 2016-02-11 23:04:01.253 | ++ /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L35: mktemp -d 2016-02-11 23:04:01.254 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L35: tmp_dir=/tmp/tmp.Hlllt3DxyO 2016-02-11 23:04:01.254 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L37: cat 2016-02-11 23:04:01.256 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L45: /usr/bin/mysql -u root 2016-02-11 23:04:01.268 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L47: cat 2016-02-11 23:04:01.270 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L52: setfacl -m g:postgres:rwx /tmp/tmp.Hlllt3DxyO 2016-02-11 23:04:01.274 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L53: sudo -u postgres /usr/bin/psql --file=/tmp/tmp.Hlllt3DxyO/postgresql.sql 2016-02-11 23:04:01.364 | Error: You must install at least one postgresql-client- package. Either install postgresql client to access the psql database OR prefer mysql to store relevant user and data in each backend. ** Affects: neutron Importance: Undecided Assignee: Madhusudhan Kandadai (madhusudhan-kandadai) Status: In Progress ** Tags: fwaas ** Changed in: neutron Assignee: (unassigned) => Madhusudhan Kandadai (madhusudhan-kandadai) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1544799 Title: FWaaS: Pick/install the right sql database to store user and data in each backend Status in neutron: In Progress Bug description: This is odd when looking at https://github.com/openstack/neutron- fwaas/blob/master/neutron_fwaas/tests/contrib/gate_hook.sh. https://jenkins05.openstack.org/job/gate-neutron-fwaas-dsvm- api/2/consoleFull 2016-02-11 23:04:01.253 | ++ /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L35: mktemp -d 2016-02-11 23:04:01.254 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L35: tmp_dir=/tmp/tmp.Hlllt3DxyO 2016-02-11 23:04:01.254 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L37: cat 2016-02-11 23:04:01.256 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L45: /usr/bin/mysql -u root 2016-02-11 23:04:01.268 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L47: cat 2016-02-11 23:04:01.270 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L52: setfacl -m g:postgres:rwx /tmp/tmp.Hlllt3DxyO 2016-02-11 23:04:01.274 | + /opt/stack/new/neutron-fwaas/neutron_fwaas/tests/contrib/gate_hook.sh:main:L53: sudo -u postgres /usr/bin/psql --file=/tmp/tmp.Hlllt3DxyO/postgresql.sql 2016-02-11 23:04:01.364 | Error: You must install at least one postgresql-client- package. Either install postgresql client to access the psql database OR prefer mysql to store relevant user and data in each backend. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1544799/+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 1538746] [NEW] tempest v2 scenario tests not passing config to serviceclient and support netcat using cirros 0.3.3 image
Public bug reported: 1. neutron-lbaas tempest v2 scenario tests doesn't pick config values from standard tempest.conf. Instead, the config values are hardcoded in the scenario/base.py. For example, self.client_args = [auth_provider, 'network', 'regionOne'] The above values doesn't work on non-devstack environment. Setting and pick the config values from tempest.conf works both devstack and non- devstack environment. 2. netcat doesnt support persistent listening 'll' option on cirros 0.3.3. image. hence change it to 'l' listening option, so the cloud can use any cirros image either 3.3/3.4. Also, change the behavior of the netcat script to make it work against 3.3. ** Affects: neutron Importance: Undecided Assignee: Madhusudhan Kandadai (madhusudhan-kandadai) Status: New ** Tags: lbaas ** Changed in: neutron Assignee: (unassigned) => Madhusudhan Kandadai (madhusudhan-kandadai) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1538746 Title: tempest v2 scenario tests not passing config to serviceclient and support netcat using cirros 0.3.3 image Status in neutron: New Bug description: 1. neutron-lbaas tempest v2 scenario tests doesn't pick config values from standard tempest.conf. Instead, the config values are hardcoded in the scenario/base.py. For example, self.client_args = [auth_provider, 'network', 'regionOne'] The above values doesn't work on non-devstack environment. Setting and pick the config values from tempest.conf works both devstack and non- devstack environment. 2. netcat doesnt support persistent listening 'll' option on cirros 0.3.3. image. hence change it to 'l' listening option, so the cloud can use any cirros image either 3.3/3.4. Also, change the behavior of the netcat script to make it work against 3.3. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1538746/+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 1498656] [NEW] router's status is not in DOWN when setting its admin-state-up as false
Public bug reported:
when updating the status of router's admin-state-up as false, its status
is not in DOWN state. However, its namespace cannot be seen under 'sudo
ip netns', but the status of that router is misleading.
steps to reproduce:
devstack@ubuntu:/opt/stack/neutron-vpnaas$ neutron router-show routerB
+---++
| Field | Value
|
+---++
| admin_state_up| False
|
| external_gateway_info | {"network_id":
"d8996aff-7a44-452d-8e94-705d4983f3e0", "enable_snat": true,
"external_fixed_ips": [{"subnet_id": "9d39b49a-539d-493e-89cc-8efd7fc6e640",
"ip_address": "172.24.4.4"}, {"subnet_id":
"c966139b-8fcb-4c5f-b6dc-c1e43545dabc", "ip_address": "2001:db8::4"}]} |
| id| e27f3a24-c8c4-4db1-ac0f-e35d56ebdeff
|
| name | routerB
|
| routes|
|
| status| ACTIVE
|
| tenant_id | ac1ff23dbb2e41babc3a1d6f69c0de9c
|
+---++
devstack@ubuntu:/opt/stack/neutron-vpnaas$
devstack@ubuntu:/opt/stack/neutron-vpnaas$
devstack@ubuntu:/opt/stack/neutron-vpnaas$
devstack@ubuntu:/opt/stack/neutron-vpnaas$
devstack@ubuntu:/opt/stack/neutron-vpnaas$
devstack@ubuntu:/opt/stack/neutron-vpnaas$
devstack@ubuntu:/opt/stack/neutron-vpnaas$
devstack@ubuntu:/opt/stack/neutron-vpnaas$
devstack@ubuntu:/opt/stack/neutron-vpnaas$ neutron router-show routerA
+---++
| Field | Value
|
+---++
| admin_state_up| True
[Yahoo-eng-team] [Bug 1492451] [NEW] installing devstack with rally plugin fails
Public bug reported: installing devstack with rally plugin fails. How to reproduce? 1. git clone https://github.com/openstack-dev/devstack.git 2. copy the local.conf into devstack directory and add the below line in local.conf enable_service rally 3. ./stack.sh 2015-09-04 19:08:47.749 | 2015-09-04 12:08:47.748 INFO migrate.versioning.api [-] done 2015-09-04 19:08:47.896 | + create_nova_cache_dir 2015-09-04 19:08:47.896 | + sudo install -d -o devstack /var/cache/nova 2015-09-04 19:08:47.912 | + rm -f '/var/cache/nova/*' 2015-09-04 19:08:47.913 | + create_nova_keys_dir 2015-09-04 19:08:47.914 | + sudo install -d -o devstack /opt/stack/data/nova /opt/stack/data/nova/keys 2015-09-04 19:08:47.928 | + [[ '' == \L\V\M ]] 2015-09-04 19:08:47.929 | + is_service_enabled neutron 2015-09-04 19:08:47.936 | + return 0 2015-09-04 19:08:47.936 | + create_nova_conf_neutron 2015-09-04 19:08:47.936 | + iniset /etc/nova/nova.conf DEFAULT network_api_class nova.network.neutronv2.api.API 2015-09-04 19:08:47.959 | + '[' True == False ']' 2015-09-04 19:08:47.959 | + iniset /etc/nova/nova.conf neutron admin_username neutron 2015-09-04 19:08:47.980 | + iniset /etc/nova/nova.conf neutron admin_password password 2015-09-04 19:08:47.996 | + iniset /etc/nova/nova.conf neutron admin_auth_url http://192.168.29.130:35357/v2.0 2015-09-04 19:08:48.021 | + iniset /etc/nova/nova.conf neutron admin_tenant_name service 2015-09-04 19:08:48.070 | + iniset /etc/nova/nova.conf neutron auth_strategy keystone 2015-09-04 19:08:48.096 | + iniset /etc/nova/nova.conf neutron region_name RegionOne 2015-09-04 19:08:48.113 | + iniset /etc/nova/nova.conf neutron url http://192.168.29.130:9696 2015-09-04 19:08:48.139 | + [[ True == \T\r\u\e ]] 2015-09-04 19:08:48.140 | + LIBVIRT_FIREWALL_DRIVER=nova.virt.firewall.NoopFirewallDriver 2015-09-04 19:08:48.140 | + iniset /etc/nova/nova.conf DEFAULT firewall_driver nova.virt.firewall.NoopFirewallDriver 2015-09-04 19:08:48.163 | + iniset /etc/nova/nova.conf DEFAULT security_group_api neutron 2015-09-04 19:08:48.183 | + neutron_plugin_create_nova_conf 2015-09-04 19:08:48.183 | + _neutron_ovs_base_configure_nova_vif_driver 2015-09-04 19:08:48.183 | + : 2015-09-04 19:08:48.183 | + '[' libvirt == xenserver ']' 2015-09-04 19:08:48.183 | + iniset /etc/nova/nova.conf DEFAULT linuxnet_interface_driver '' 2015-09-04 19:08:48.206 | + is_service_enabled q-meta 2015-09-04 19:08:48.214 | + return 0 2015-09-04 19:08:48.215 | + iniset /etc/nova/nova.conf neutron service_metadata_proxy True 2015-09-04 19:08:48.233 | + iniset /etc/nova/nova.conf DEFAULT vif_plugging_is_fatal True 2015-09-04 19:08:48.254 | + iniset /etc/nova/nova.conf DEFAULT vif_plugging_timeout 300 2015-09-04 19:08:48.273 | + init_nova_cells 2015-09-04 19:08:48.273 | + is_service_enabled n-cell 2015-09-04 19:08:48.281 | + return 1 2015-09-04 19:08:48.281 | + run_phase stack post-config 2015-09-04 19:08:48.281 | + local mode=stack 2015-09-04 19:08:48.281 | + local phase=post-config 2015-09-04 19:08:48.281 | + [[ -d /home/devstack/devstack/extras.d ]] 2015-09-04 19:08:48.281 | + for i in '$TOP_DIR/extras.d/*.sh' 2015-09-04 19:08:48.281 | + [[ -r /home/devstack/devstack/extras.d/50-ironic.sh ]] 2015-09-04 19:08:48.281 | + source /home/devstack/devstack/extras.d/50-ironic.sh stack post-config 2015-09-04 19:08:48.281 | ++ is_service_enabled ir-api ir-cond 2015-09-04 19:08:48.287 | ++ return 1 2015-09-04 19:08:48.287 | + for i in '$TOP_DIR/extras.d/*.sh' 2015-09-04 19:08:48.287 | + [[ -r /home/devstack/devstack/extras.d/60-ceph.sh ]] 2015-09-04 19:08:48.288 | + source /home/devstack/devstack/extras.d/60-ceph.sh stack post-config 2015-09-04 19:08:48.288 | ++ is_service_enabled ceph 2015-09-04 19:08:48.297 | ++ return 1 2015-09-04 19:08:48.297 | + for i in '$TOP_DIR/extras.d/*.sh' 2015-09-04 19:08:48.297 | + [[ -r /home/devstack/devstack/extras.d/70-rally.sh ]] 2015-09-04 19:08:48.297 | + source /home/devstack/devstack/extras.d/70-rally.sh stack post-config 2015-09-04 19:08:48.298 | ++ is_service_enabled rally 2015-09-04 19:08:48.305 | ++ return 0 2015-09-04 19:08:48.305 | ++ [[ stack == \s\o\u\r\c\e ]] 2015-09-04 19:08:48.305 | ++ [[ stack == \s\t\a\c\k ]] 2015-09-04 19:08:48.305 | ++ [[ post-config == \i\n\s\t\a\l\l ]] 2015-09-04 19:08:48.305 | ++ [[ stack == \s\t\a\c\k ]] 2015-09-04 19:08:48.305 | ++ [[ post-config == \p\o\s\t\-\c\o\n\f\i\g ]] 2015-09-04 19:08:48.305 | ++ echo_summary 'Configuring Rally' 2015-09-04 19:08:48.305 | ++ [[ -t 3 ]] 2015-09-04 19:08:48.305 | ++ [[ True != \T\r\u\e ]] 2015-09-04 19:08:48.306 | ++ echo -e Configuring Rally 2015-09-04 19:08:48.306 | ++ configure_rally 2015-09-04 19:08:48.306 | ++ [[ ! -d /etc/rally ]] 2015-09-04 19:08:48.306 | ++ sudo chown devstack /etc/rally 2015-09-04 19:08:48.318 | ++ cp /opt/stack/rally/etc/rally/rally.conf.sample /etc/rally/rally.conf 2015-09-04 19:08:48.321 | ++ iniset /etc/rally/rally.conf DEFAULT debug False 2015-09-04 19:08:48.348 | +++ database_connection_url rally
[Yahoo-eng-team] [Bug 1491662] [NEW] upon creating vpn-service-create, the status is hung in 'pending_create' even after waiting for 40-50 sec or so
Public bug reported: Clone master branch of vpnaas repo. Create necessary two networks, routers, subnets, boot up two vms. Create ipkepolicy, ipsecpolicy and vpn-service. neutron vpn-service-create --name myvpnA --description "My vpn serviceA" It is created, but the status is still shown as 'Pending_create'. Try checking the status again for about 40-sec, but no luck. docker@ubuntu:~/devstack$ neutron vpn-service-show myvpnA ++--+ | Field | Value| ++--+ | admin_state_up | True | | description| My vpnA service | | external_v4_ip | 172.24.4.3 | | external_v6_ip | 2001:db8::3 | | id | 2077e692-ceee-4ae0-8564-80a114a95e2d | | name | myvpnA | | router_id | 5686f412-6dcd-4ff9-9f03-e559c00ed0f5 | | status | PENDING_CREATE | | subnet_id | eae807fe-21a7-41eb-bbaa-ae229e4a271c | | tenant_id | 166bec794e52459589aa1749d195238e | ++--+ This worked fine about 6-7 hours back, looks like the latest patch-set broken it. ** Affects: neutron Importance: Undecided Status: New ** Tags: vpnaas ** Summary changed: - upon creating vpn-service-create, the status is hung in 'pending_create' status + upon creating vpn-service-create, the status is hung in 'pending_create' even after waiting for 40-50 sec or so -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1491662 Title: upon creating vpn-service-create, the status is hung in 'pending_create' even after waiting for 40-50 sec or so Status in neutron: New Bug description: Clone master branch of vpnaas repo. Create necessary two networks, routers, subnets, boot up two vms. Create ipkepolicy, ipsecpolicy and vpn-service. neutron vpn-service-create --name myvpnA --description "My vpn serviceA" It is created, but the status is still shown as 'Pending_create'. Try checking the status again for about 40-sec, but no luck. docker@ubuntu:~/devstack$ neutron vpn-service-show myvpnA ++--+ | Field | Value| ++--+ | admin_state_up | True | | description| My vpnA service | | external_v4_ip | 172.24.4.3 | | external_v6_ip | 2001:db8::3 | | id | 2077e692-ceee-4ae0-8564-80a114a95e2d | | name | myvpnA | | router_id | 5686f412-6dcd-4ff9-9f03-e559c00ed0f5 | | status | PENDING_CREATE | | subnet_id | eae807fe-21a7-41eb-bbaa-ae229e4a271c | | tenant_id | 166bec794e52459589aa1749d195238e | ++--+ This worked fine about 6-7 hours back, looks like the latest patch-set broken it. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1491662/+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 1491662] Re: upon creating vpn-service-create, the status is hung in 'pending_create' even after waiting for 40-50 sec or so
** Changed in: neutron Status: New => 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/1491662 Title: upon creating vpn-service-create, the status is hung in 'pending_create' even after waiting for 40-50 sec or so Status in neutron: Invalid Bug description: Clone master branch of vpnaas repo. Create necessary two networks, routers, subnets, boot up two vms. Create ipkepolicy, ipsecpolicy and vpn-service. neutron vpn-service-create --name myvpnA --description "My vpn serviceA" It is created, but the status is still shown as 'Pending_create'. Try checking the status again for about 40-sec, but no luck. docker@ubuntu:~/devstack$ neutron vpn-service-show myvpnA ++--+ | Field | Value| ++--+ | admin_state_up | True | | description| My vpnA service | | external_v4_ip | 172.24.4.3 | | external_v6_ip | 2001:db8::3 | | id | 2077e692-ceee-4ae0-8564-80a114a95e2d | | name | myvpnA | | router_id | 5686f412-6dcd-4ff9-9f03-e559c00ed0f5 | | status | PENDING_CREATE | | subnet_id | eae807fe-21a7-41eb-bbaa-ae229e4a271c | | tenant_id | 166bec794e52459589aa1749d195238e | ++--+ This worked fine about 6-7 hours back, looks like the latest patch-set broken it. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1491662/+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 1491679] [NEW] ipsec-site-connection-create is not back to ACTIVE state after updating admin_state_up as True -> False -> True
Public bug reported:
neutron vpn-service-create --name myvpnA --description "My vpnA service"
routerA subA
neutron vpn-service-create --name myvpnB --description "My vpnB service"
routerB subB
neutron ipsec-site-connection-create --name vpnconnectionA --vpnservice-id
myvpnA \
--ikepolicy-id ikepolicy --ipsecpolicy-id ipsecpolicy --peer-address
172.24.4.102 \
--peer-id 172.24.4.102 --peer-cidr 10.2.0.0/24 --psk secret
neutron ipsec-site-connection-create --name vpnconnectionB --vpnservice-id
myvpnB \
--ikepolicy-id ikepolicy --ipsecpolicy-id ipsecpolicy --peer-address
172.24.4.101 \
--peer-id 172.24.4.101 --peer-cidr 10.1.0.0/24 --psk secret
docker@ubuntu:~/devstack$ neutron ipsec-site-connection-list
+--++--+---++---++
| id | name | peer_address |
peer_cidrs| route_mode | auth_mode | status |
+--++--+---++---++
| 4ca689a5-180a-4661-bd5b-6182d9dad5e4 | vpnconnectionA | 172.24.4.102 |
"10.2.0.0/24" | static | psk | ACTIVE |
| f65263bd-b5cf-46c5-a809-a376bec461d9 | vpnconnectionB | 172.24.4.101 |
"10.1.0.0/24" | static | psk | ACTIVE |
+--++--+---++---++
Now, change the admin_state_up as false for ipsec-site-connection -
vpnconnectionA.
docker@ubuntu:~/devstack$ neutron ipsec-site-connection-list
+--++--+---++---++
| id | name | peer_address |
peer_cidrs| route_mode | auth_mode | status |
+--++--+---++---++
| 4ca689a5-180a-4661-bd5b-6182d9dad5e4 | vpnconnectionA | 172.24.4.102 |
"10.2.0.0/24" | static | psk | DOWN |
| f65263bd-b5cf-46c5-a809-a376bec461d9 | vpnconnectionB | 172.24.4.101 |
"10.1.0.0/24" | static | psk | ACTIVE |
+--++--+---++---++
ping vm1 to vm2 does not work and ping vm2 and vm1 does not work ( this
is expected)
Change back the admin_state_up as True, the status is still shown as
DOWN, even the vpn-service for myvpnA is at DOWN
docker@ubuntu:~/devstack$ neutron ipsec-site-connection-show vpnconnectionA
+++
| Field | Value |
+++
| admin_state_up | True |
| auth_mode | psk|
| description||
| dpd| {"action": "hold", "interval": 30, "timeout": 120} |
| id | 4ca689a5-180a-4661-bd5b-6182d9dad5e4 |
| ikepolicy_id | d5112709-8909-4ce3-a7aa-99569474c812 |
| initiator | bi-directional |
| ipsecpolicy_id | 430ece29-8cf5-488a-b77d-798f0e7d455e |
| mtu| 1500 |
| name | vpnconnectionA |
| peer_address | 172.24.4.102 |
| peer_cidrs | 10.2.0.0/24|
| peer_id| 172.24.4.102 |
| psk| secret |
| route_mode | static |
| status | DOWN |
| tenant_id | 7d0f12937859462bb7c1d5d012111dec |
| vpnservice_id | 33311333-a6be-4b59-bedc-d3f1583459e7 |
+++
docker@ubuntu:~/devstack$ neutron vpn-service-show myvpnA
++--+
| Field | Value|
++--+
| admin_state_up | True |
| description| My vpnA service |
| external_v4_ip | 172.24.4.101 |
| external_v6_ip | |
| id | 33311333-a6be-4b59-bedc-d3f1583459e7 |
| name | myvpnA |
| router_id | 3b4fab84-6bac-4a29-8bf2-65378e342dc4 |
| status | DOWN |
| subnet_id | 63d99342-c9e0-41a9-993d-3c2a6e0256ad |
| tenant_id |
[Yahoo-eng-team] [Bug 1479346] Re: LBaaS: test_healthmonitor_basic scenario fails
** Changed in: neutron
Status: Fix Committed => 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/1479346
Title:
LBaaS: test_healthmonitor_basic scenario fails
Status in neutron:
Fix Released
Bug description:
test_healthmonitor_basic fails in Jenkins as well as when it is run
locally using tox -e scenario
Captured traceback:
~~~
Traceback (most recent call last):
File "neutron_lbaas/tests/tempest/lib/test.py", line 310, in
tearDownClass
six.reraise(etype, value, trace)
File "neutron_lbaas/tests/tempest/lib/test.py", line 293, in
tearDownClass
teardown()
File "neutron_lbaas/tests/tempest/lib/test.py", line 502, in
clear_isolated_creds
cls._creds_provider.clear_isolated_creds()
File "neutron_lbaas/tests/tempest/lib/common/isolated_creds.py", line
415, in clear_isolated_creds
self._clear_isolated_net_resources()
File "neutron_lbaas/tests/tempest/lib/common/isolated_creds.py", line
406, in _clear_isolated_net_resources
creds.subnet['name'])
File "neutron_lbaas/tests/tempest/lib/common/isolated_creds.py", line
357, in _clear_isolated_subnet
net_client.delete_subnet(subnet_id)
File
"neutron_lbaas/tests/tempest/lib/services/network/json/network_client.py", line
113, in _delete
resp, body = self.delete(uri)
File
"/opt/stack/neutron-lbaas/.tox/scenario/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 287, in delete
return self.request('DELETE', url, extra_headers, headers, body)
File
"/opt/stack/neutron-lbaas/.tox/scenario/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 643, in request
resp, resp_body)
File
"/opt/stack/neutron-lbaas/.tox/scenario/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py",
line 705, in _error_checker
raise exceptions.Conflict(resp_body)
tempest_lib.exceptions.Conflict: An object with that identifier already
exists
Details: {u'message': u'Unable to complete operation on subnet
8a98d02b-13c5-4d68-8908-18cc2ba868a3. One or more ports have an IP allocation
from this subnet.', u'detail': u'', u'type': u'SubnetInUse'}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1479346/+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 1479346] Re: LBaaS: test_healthmonitor_basic scenario fails
** Changed in: neutron
Status: New = 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/1479346
Title:
LBaaS: test_healthmonitor_basic scenario fails
Status in neutron:
Fix Released
Bug description:
test_healthmonitor_basic fails in Jenkins as well as when it is run
locally using tox -e scenario
Captured traceback:
~~~
Traceback (most recent call last):
File neutron_lbaas/tests/tempest/lib/test.py, line 310, in
tearDownClass
six.reraise(etype, value, trace)
File neutron_lbaas/tests/tempest/lib/test.py, line 293, in
tearDownClass
teardown()
File neutron_lbaas/tests/tempest/lib/test.py, line 502, in
clear_isolated_creds
cls._creds_provider.clear_isolated_creds()
File neutron_lbaas/tests/tempest/lib/common/isolated_creds.py, line
415, in clear_isolated_creds
self._clear_isolated_net_resources()
File neutron_lbaas/tests/tempest/lib/common/isolated_creds.py, line
406, in _clear_isolated_net_resources
creds.subnet['name'])
File neutron_lbaas/tests/tempest/lib/common/isolated_creds.py, line
357, in _clear_isolated_subnet
net_client.delete_subnet(subnet_id)
File
neutron_lbaas/tests/tempest/lib/services/network/json/network_client.py, line
113, in _delete
resp, body = self.delete(uri)
File
/opt/stack/neutron-lbaas/.tox/scenario/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py,
line 287, in delete
return self.request('DELETE', url, extra_headers, headers, body)
File
/opt/stack/neutron-lbaas/.tox/scenario/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py,
line 643, in request
resp, resp_body)
File
/opt/stack/neutron-lbaas/.tox/scenario/local/lib/python2.7/site-packages/tempest_lib/common/rest_client.py,
line 705, in _error_checker
raise exceptions.Conflict(resp_body)
tempest_lib.exceptions.Conflict: An object with that identifier already
exists
Details: {u'message': u'Unable to complete operation on subnet
8a98d02b-13c5-4d68-8908-18cc2ba868a3. One or more ports have an IP allocation
from this subnet.', u'detail': u'', u'type': u'SubnetInUse'}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1479346/+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 1481491] [NEW] unable to connect servers using their IPv6 for loadbalancer scenario tests
Public bug reported: There is a following scenario when testing ipv6 neutron-loadbalancer 1. Create two servers using ipv6 subnet and take a note of its ipv6 address 2. Create IPv6 load balancer associated with the above 2 nodes 3. Use Round Robin/Least_Connection Algorithm 4. Pass traffic to load balancer 5. Verify initial location of node hit 6. Pass traffic to load balancer 7. Verify next location of node hit 8. Pass Traffic to load balancer 9. Verify next location of node hit In this case, SSH to ipv6 server using floatingips cannot be done (point 4) because of Unlike IPv4 there is no current embedded support for floating IPs with IPv6. Could not make it working and keeping these IPv6 scenario tests on HOLD ** Affects: neutron Importance: Undecided Status: New ** Tags: lbaas -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1481491 Title: unable to connect servers using their IPv6 for loadbalancer scenario tests Status in neutron: New Bug description: There is a following scenario when testing ipv6 neutron-loadbalancer 1. Create two servers using ipv6 subnet and take a note of its ipv6 address 2. Create IPv6 load balancer associated with the above 2 nodes 3. Use Round Robin/Least_Connection Algorithm 4. Pass traffic to load balancer 5. Verify initial location of node hit 6. Pass traffic to load balancer 7. Verify next location of node hit 8. Pass Traffic to load balancer 9. Verify next location of node hit In this case, SSH to ipv6 server using floatingips cannot be done (point 4) because of Unlike IPv4 there is no current embedded support for floating IPs with IPv6. Could not make it working and keeping these IPv6 scenario tests on HOLD To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1481491/+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 1478169] Re: Could not setup simple webserver successfully when creating lb with session persistence type:HTTP_COOKIE
** 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/1478169
Title:
Could not setup simple webserver successfully when creating lb with
session persistence type:HTTP_COOKIE
Status in neutron:
Invalid
Bug description:
I am not sure whether this bug is duplicate of this one:
https://bugs.launchpad.net/neutron/+bug/1477348 If it is so, feel free
to mark it as duplicate. Thanks. (However the errors reported are
different though)
(1) neutron lbaas-loadbalancer-create --name lb1 private-subnet
neutron lbaas-listener-create --loadbalancer lb1 --protocol HTTP
--protocol-port 80 --name listener1
neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener listener1
--protocol HTTP --session-persistence type=HTTP_COOKIE --name pool1
# Set up two backend servers with their right IPs:
neutron lbaas-member-create --subnet private-subnet --address 10.0.0.4
--protocol-port 80 pool1
neutron lbaas-member-create --subnet private-subnet --address 10.0.0.5
--protocol-port 80 pool1
# setup simple webserver in each of the backend server:
MYIP=$(ifconfig eth0|grep 'inet addr'|awk -F: '{print $2}'| awk '{print $1}')
while true; do echo -e HTTP/1.0 200 OK\r\n\r\nWelcome to $MYIP | sudo nc -l
-p 80 ; done
curl http://lb_ip
curl: (7) Failed to connect to 10.0.0.5 port 80: Connection refused
(2) when I create pool without session_persistence, I am able to get
200 OK when I curl http://lb-ip
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1478169/+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 1478169] [NEW] Could not setup simple webserver successfully when creating lb with session persistence type:HTTP_COOKIE
Public bug reported:
I am not sure whether this bug is duplicate of this one:
https://bugs.launchpad.net/neutron/+bug/1477348 If it is so, feel free
to mark it as duplicate. Thanks. (However the errors reported are
different though)
(1) neutron lbaas-loadbalancer-create --name lb1 private-subnet
neutron lbaas-listener-create --loadbalancer lb1 --protocol HTTP
--protocol-port 80 --name listener1
neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener listener1
--protocol HTTP --session-persistence type=HTTP_COOKIE --name pool1
# Set up two backend servers with their right IPs:
neutron lbaas-member-create --subnet private-subnet --address 10.0.0.4
--protocol-port 80 pool1
neutron lbaas-member-create --subnet private-subnet --address 10.0.0.5
--protocol-port 80 pool1
# setup simple webserver in each of the backend server:
MYIP=$(ifconfig eth0|grep 'inet addr'|awk -F: '{print $2}'| awk '{print $1}')
while true; do echo -e HTTP/1.0 200 OK\r\n\r\nWelcome to $MYIP | sudo nc -l
-p 80 ; done
curl http://lb_ip
curl: (7) Failed to connect to 10.0.0.5 port 80: Connection refused
(2) when I create pool without session_persistence, I am able to get 200
OK when I curl http://lb-ip
** Affects: neutron
Importance: Undecided
Status: New
** Tags: lbaas
** Description changed:
I am not sure whether this bug is duplicate of this one:
https://bugs.launchpad.net/neutron/+bug/1477348 If it is so, feel free
- to mar it as duplicate. Thanks. (However the errors reported are
+ to mark it as duplicate. Thanks. (However the errors reported are
different though)
(1) neutron lbaas-loadbalancer-create --name lb1 private-subnet
neutron lbaas-listener-create --loadbalancer lb1 --protocol HTTP
--protocol-port 80 --name listener1
neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener listener1
--protocol HTTP --session-persistence type=HTTP_COOKIE --name pool1
# Set up two backend servers with their right IPs:
neutron lbaas-member-create --subnet private-subnet --address 10.0.0.4
--protocol-port 80 pool1
neutron lbaas-member-create --subnet private-subnet --address 10.0.0.5
--protocol-port 80 pool1
# setup simple webserver in each of the backend server:
MYIP=$(ifconfig eth0|grep 'inet addr'|awk -F: '{print $2}'| awk '{print $1}')
while true; do echo -e HTTP/1.0 200 OK\r\n\r\nWelcome to $MYIP | sudo nc -l
-p 80 ; done
curl http://lb_ip
curl: (7) Failed to connect to 10.0.0.5 port 80: Connection refused
(2) when I create pool without session_persistence, I am able to get 200
OK when I curl http://lb-ip
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1478169
Title:
Could not setup simple webserver successfully when creating lb with
session persistence type:HTTP_COOKIE
Status in neutron:
New
Bug description:
I am not sure whether this bug is duplicate of this one:
https://bugs.launchpad.net/neutron/+bug/1477348 If it is so, feel free
to mark it as duplicate. Thanks. (However the errors reported are
different though)
(1) neutron lbaas-loadbalancer-create --name lb1 private-subnet
neutron lbaas-listener-create --loadbalancer lb1 --protocol HTTP
--protocol-port 80 --name listener1
neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener listener1
--protocol HTTP --session-persistence type=HTTP_COOKIE --name pool1
# Set up two backend servers with their right IPs:
neutron lbaas-member-create --subnet private-subnet --address 10.0.0.4
--protocol-port 80 pool1
neutron lbaas-member-create --subnet private-subnet --address 10.0.0.5
--protocol-port 80 pool1
# setup simple webserver in each of the backend server:
MYIP=$(ifconfig eth0|grep 'inet addr'|awk -F: '{print $2}'| awk '{print $1}')
while true; do echo -e HTTP/1.0 200 OK\r\n\r\nWelcome to $MYIP | sudo nc -l
-p 80 ; done
curl http://lb_ip
curl: (7) Failed to connect to 10.0.0.5 port 80: Connection refused
(2) when I create pool without session_persistence, I am able to get
200 OK when I curl http://lb-ip
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1478169/+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 1449286] [NEW] lb's operating_status is not in DISABLED state when an user creates a loadbalancer with admin_state_up field as 'False'
Public bug reported:
when I create a loadbalancer with the following body, I could see the
'operating_status' is still showing 'ONLINE', it should be 'DISABLED'. I
also believe 'provisioning_status' should be shown as 'OFFLINE' , but I
could see as 'ONLINE'
Steps can be reproduced:
POST http://ip:9696/v2.0/lbaas/loadbalancers with the required
headers:
Body:
{
loadbalancer: {
vip_subnet_id: subnet_id,
admin_state_up: false
}
}
Response:
{
loadbalancers: [
{
description: ,
admin_state_up: false,
tenant_id: aad7bae2df174c1291bf994a8b8fac89,
provisioning_status: ACTIVE,
listeners: [],
vip_address: 10.0.0.5,
vip_port_id: 59104203-e503-4d67-93ff-70a8df3c53c4,
provider: haproxy,
vip_subnet_id: 94672fbb-0f7e-4c54-a538-a9826bd616d1,
id: e1976562-b1f6-45cd-8e32-5b961f80fa24,
operating_status: ONLINE,
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/1449286
Title:
lb's operating_status is not in DISABLED state when an user creates a
loadbalancer with admin_state_up field as 'False'
Status in OpenStack Neutron (virtual network service):
New
Bug description:
when I create a loadbalancer with the following body, I could see the
'operating_status' is still showing 'ONLINE', it should be 'DISABLED'.
I also believe 'provisioning_status' should be shown as 'OFFLINE' ,
but I could see as 'ONLINE'
Steps can be reproduced:
POST http://ip:9696/v2.0/lbaas/loadbalancers with the required
headers:
Body:
{
loadbalancer: {
vip_subnet_id: subnet_id,
admin_state_up: false
}
}
Response:
{
loadbalancers: [
{
description: ,
admin_state_up: false,
tenant_id: aad7bae2df174c1291bf994a8b8fac89,
provisioning_status: ACTIVE,
listeners: [],
vip_address: 10.0.0.5,
vip_port_id: 59104203-e503-4d67-93ff-70a8df3c53c4,
provider: haproxy,
vip_subnet_id: 94672fbb-0f7e-4c54-a538-a9826bd616d1,
id: e1976562-b1f6-45cd-8e32-5b961f80fa24,
operating_status: ONLINE,
name:
}
]
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1449286/+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 1444765] Re: admin's tenant_id is not the same with load_balancer's tenant_id in tempest tests
** Changed in: neutron
Status: New = 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/1444765
Title:
admin's tenant_id is not the same with load_balancer's tenant_id in
tempest tests
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
Here is the following scenario:
This is happening only WITH tempest tests by inheriting the necessary
class from 'tempest/api/neutron':
(a) When creating a loadbalancer for non_admin user, I could see the
'tenant_id' is equal to loadbalancer.get('tenant_id'). This sounds
good to me and requires no attention.
i.e.,
credentials = cls.isolated_creds.get_primary_creds()
mgr = tempest_clients.Manager(credentials=credentials)
auth_provider = mgr.get_auth_provider(credentials)
client_args = [auth_provider, 'network', 'regionOne']
(b) whereas, when I create a loadbalancer using admin credentials,
the tenant_id NOT equals loadbalancer.get('tenant_id'). In general it
SHOULD be equal.
i.e,.
credentials_admin = cls.isolated_creds.get_admin_creds()
mgr_admin = tempest_clients.Manager(credentials=credentials_admin)
auth_provider_admin = mgr_admin.get_auth_provider(credentials_admin)
client_args = [auth_provider_admin, 'network', 'regionOne']
Not sure why this is happening, the expected behavior should be An
user(either admin/non-admin) should be able to create a loadbalancer
for the default tenant and that 'tenant_id' should be equal to the
admin's 'tenant_id'. There are other test cases too specially for
'admin' role got succeeded and behaving properly.
Details about the code can be found at
https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/base.py
For the exact testcase:
(a) For admin_testcase: see line 55 - 61:
https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/test_load_balancers_admin.py
(b) For non_admin testcase: see line 259 -266:
https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/test_load_balancers_non_admin.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1444765/+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 1444765] Re: admin's tenant_id is not the same with load_balancer's tenant_id in tempest tests
** Package changed: ifupdown (Ubuntu) = neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1444765
Title:
admin's tenant_id is not the same with load_balancer's tenant_id in
tempest tests
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Here is the following scenario:
This is happening only WITH tempest tests by inheriting the necessary
class from 'tempest/api/neutron':
(a) When creating a loadbalancer for non_admin user, I could see the
'tenant_id' is equal to loadbalancer.get('tenant_id'). This sounds
good to me and requires no attention.
i.e.,
credentials = cls.isolated_creds.get_primary_creds()
mgr = tempest_clients.Manager(credentials=credentials)
auth_provider = mgr.get_auth_provider(credentials)
client_args = [auth_provider, 'network', 'regionOne']
(b) whereas, when I create a loadbalancer using admin credentials,
the tenant_id NOT equals loadbalancer.get('tenant_id'). In general it
SHOULD be equal.
i.e,.
credentials_admin = cls.isolated_creds.get_admin_creds()
mgr_admin = tempest_clients.Manager(credentials=credentials_admin)
auth_provider_admin = mgr_admin.get_auth_provider(credentials_admin)
client_args = [auth_provider_admin, 'network', 'regionOne']
Not sure why this is happening, the expected behavior should be An
user(either admin/non-admin) should be able to create a loadbalancer
for the default tenant and that 'tenant_id' should be equal to the
admin's 'tenant_id'. There are other test cases too specially for
'admin' role got succeeded and behaving properly.
Details about the code can be found at
https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/base.py
For the exact testcase:
(a) For admin_testcase: see line 55 - 61:
https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/test_load_balancers_admin.py
(b) For non_admin testcase: see line 259 -266:
https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/test_load_balancers_non_admin.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1444765/+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
