[Yahoo-eng-team] [Bug 1540983] Re: Gate failures for neutron in test_dualnet_multi_prefix_slaac
[Expired for OpenStack-Gate because there has been no activity for 60 days.] ** Changed in: openstack-gate 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/1540983 Title: Gate failures for neutron in test_dualnet_multi_prefix_slaac Status in neutron: Expired Status in OpenStack-Gate: Expired Bug description: 24 hits in 7 days for logstash query : message:"in test_dualnet_multi_prefix_slaac" AND voting:1 2016-02-02 14:35:49.054 | Captured traceback: 2016-02-02 14:35:49.054 | ~~~ 2016-02-02 14:35:49.054 | Traceback (most recent call last): 2016-02-02 14:35:49.054 | File "tempest/test.py", line 113, in wrapper 2016-02-02 14:35:49.055 | return f(self, *func_args, **func_kwargs) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 246, in test_dualnet_multi_prefix_slaac 2016-02-02 14:35:49.055 | dualnet=True) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 155, in _prepare_and_test 2016-02-02 14:35:49.055 | sshv4_1, ips_from_api_1, sid1 = self.prepare_server(networks=net_list) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 128, in prepare_server 2016-02-02 14:35:49.055 | username=username) 2016-02-02 14:35:49.056 | File "tempest/scenario/manager.py", line 390, in get_remote_client 2016-02-02 14:35:49.056 | linux_client.validate_authentication() 2016-02-02 14:35:49.056 | File "tempest/common/utils/linux/remote_client.py", line 63, in validate_authentication 2016-02-02 14:35:49.056 | self.ssh_client.test_connection_auth() 2016-02-02 14:35:49.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 172, in test_connection_auth 2016-02-02 14:35:49.056 | connection = self._get_ssh_connection() 2016-02-02 14:35:49.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 87, in _get_ssh_connection 2016-02-02 14:35:49.057 | password=self.password) 2016-02-02 14:35:49.057 | tempest_lib.exceptions.SSHTimeout: Connection to the 172.24.5.141 via SSH timed out. 2016-02-02 14:35:49.057 | User: cirros, Password: None To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1540983/+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 1540983] Re: Gate failures for neutron in test_dualnet_multi_prefix_slaac
[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/1540983 Title: Gate failures for neutron in test_dualnet_multi_prefix_slaac Status in neutron: Expired Status in OpenStack-Gate: Expired Bug description: 24 hits in 7 days for logstash query : message:"in test_dualnet_multi_prefix_slaac" AND voting:1 2016-02-02 14:35:49.054 | Captured traceback: 2016-02-02 14:35:49.054 | ~~~ 2016-02-02 14:35:49.054 | Traceback (most recent call last): 2016-02-02 14:35:49.054 | File "tempest/test.py", line 113, in wrapper 2016-02-02 14:35:49.055 | return f(self, *func_args, **func_kwargs) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 246, in test_dualnet_multi_prefix_slaac 2016-02-02 14:35:49.055 | dualnet=True) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 155, in _prepare_and_test 2016-02-02 14:35:49.055 | sshv4_1, ips_from_api_1, sid1 = self.prepare_server(networks=net_list) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 128, in prepare_server 2016-02-02 14:35:49.055 | username=username) 2016-02-02 14:35:49.056 | File "tempest/scenario/manager.py", line 390, in get_remote_client 2016-02-02 14:35:49.056 | linux_client.validate_authentication() 2016-02-02 14:35:49.056 | File "tempest/common/utils/linux/remote_client.py", line 63, in validate_authentication 2016-02-02 14:35:49.056 | self.ssh_client.test_connection_auth() 2016-02-02 14:35:49.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 172, in test_connection_auth 2016-02-02 14:35:49.056 | connection = self._get_ssh_connection() 2016-02-02 14:35:49.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 87, in _get_ssh_connection 2016-02-02 14:35:49.057 | password=self.password) 2016-02-02 14:35:49.057 | tempest_lib.exceptions.SSHTimeout: Connection to the 172.24.5.141 via SSH timed out. 2016-02-02 14:35:49.057 | User: cirros, Password: None To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1540983/+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 1622516] Re: TestNetworkBasicOps.test_router_rescheduling failed with 'No IPv4 addresses found in: ...'
[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/1622516
Title:
TestNetworkBasicOps.test_router_rescheduling failed with 'No IPv4
addresses found in: ...'
Status in neutron:
Expired
Bug description:
http://logs.openstack.org/01/367501/1/gate/gate-tempest-dsvm-neutron-
linuxbridge-ubuntu-xenial/3370b9c/console.html
2016-09-11 05:27:03.407325 | Captured traceback:
2016-09-11 05:27:03.407342 | ~~~
2016-09-11 05:27:03.407364 | Traceback (most recent call last):
2016-09-11 05:27:03.407389 | File "tempest/test.py", line 152, in
wrapper
2016-09-11 05:27:03.407414 | return func(*func_args, **func_kwargs)
2016-09-11 05:27:03.407439 | File "tempest/test.py", line 107, in
wrapper
2016-09-11 05:27:03.407464 | return f(self, *func_args, **func_kwargs)
2016-09-11 05:27:03.407500 | File
"tempest/scenario/test_network_basic_ops.py", line 717, in
test_router_rescheduling
2016-09-11 05:27:03.407524 | self._setup_network_and_servers()
2016-09-11 05:27:03.407561 | File
"tempest/scenario/test_network_basic_ops.py", line 124, in
_setup_network_and_servers
2016-09-11 05:27:03.407588 | floating_ip =
self.create_floating_ip(server)
2016-09-11 05:27:03.407619 | File "tempest/scenario/manager.py", line
816, in create_floating_ip
2016-09-11 05:27:03.407648 | port_id, ip4 =
self._get_server_port_id_and_ip4(thing)
2016-09-11 05:27:03.407681 | File "tempest/scenario/manager.py", line
795, in _get_server_port_id_and_ip4
2016-09-11 05:27:03.407707 | "No IPv4 addresses found in: %s" % ports)
2016-09-11 05:27:03.407753 | File
"/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/unittest2/case.py",
line 845, in assertNotEqual
2016-09-11 05:27:03.40 | raise self.failureException(msg)
2016-09-11 05:27:03.408051 | AssertionError: 0 == 0 : No IPv4 addresses
found in: [{u'binding:host_id': u'ubuntu-xenial-rax-ord-4213156', u'id':
u'ef74f0f4-aa7c-4fc7-ad90-e6aab9531309', u'allowed_address_pairs': [],
u'status': u'BUILD', u'extra_dhcp_opts': [], u'name': u'', u'admin_state_up':
True, u'tenant_id': u'05e1e2af7c5246b1ab35831d6ac59896', u'network_id':
u'ebc57b5b-63cc-4ff9-86b1-f5bf13950908', u'description': u'',
u'security_groups': [u'aa9f20fa-bdf7-4d4b-b072-55ade7d92776'], u'device_id':
u'd08c8b65-ac5b-4d44-a954-41b3f8eb357f', u'created_at': u'2016-09-11T05:13:53',
u'binding:vnic_type': u'normal', u'fixed_ips': [{u'ip_address': u'10.1.0.9',
u'subnet_id': u'abbb64d7-a2e9-4ead-8b55-937e2415faff'}], u'device_owner':
u'compute:None', u'binding:vif_type': u'bridge', u'updated_at':
u'2016-09-11T05:14:00', u'port_security_enabled': True, u'binding:vif_details':
{u'port_filter': True}, u'binding:profile': {}, u'revision_number': 9,
u'mac_address': u'fa:16:3e:73:99:fe'}]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622516/+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 1628886] Re: test_reprocess_port_when_ovs_restarts fails nondeterministically
[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/1628886 Title: test_reprocess_port_when_ovs_restarts fails nondeterministically Status in neutron: Expired Bug description: Encountered in https://review.openstack.org/#/c/365326/8/, specifically http://logs.openstack.org/26/365326/8/check/gate-neutron- dsvm-functional-ubuntu-trusty/cc5f8eb/testr_results.html.gz Stack trace from tox (if the logs are deleted from the server): http://paste.openstack.org/show/583476/ Stack trace from dsvm-functional log dir: http://paste.openstack.org/show/583478/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1628886/+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 1689238] Re: enable qos scenario
https://review.openstack.org/#/c/463268/ ** Project changed: networking-midonet => neutron ** Summary changed: - enable qos scenario + Do not disable qos scenario unconditionally ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => YAMAMOTO Takashi (yamamoto) ** Tags added: ocata-backport-potential ** Description changed: qos scenario test is disabled in neutron for bug 1662109. the bug doesn't seem related to midonet implementation. + note that the tempest plugin is used by subprojects' gate jobs. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1689238 Title: Do not disable qos scenario unconditionally Status in neutron: In Progress Bug description: qos scenario test is disabled in neutron for bug 1662109. the bug doesn't seem related to midonet implementation. note that the tempest plugin is used by subprojects' gate jobs. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1689238/+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 1689238] [NEW] enable qos scenario
You have been subscribed to a public bug: qos scenario test is disabled in neutron for bug 1662109. the bug doesn't seem related to midonet implementation. ** Affects: neutron Importance: Undecided Status: New -- enable qos scenario https://bugs.launchpad.net/bugs/1689238 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. -- 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 1689694] [NEW] When using glance v2 client, uploaded temporary file in /tmp is not removed.
Public bug reported: When using glance v2 client, temporary upload file remains in /tmp folder after a successful or failed upload. ** Affects: horizon Importance: Undecided Assignee: Chao Guo (jimmygc) Status: New ** Changed in: horizon Assignee: (unassigned) => Chao Guo (jimmygc) -- 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/1689694 Title: When using glance v2 client, uploaded temporary file in /tmp is not removed. Status in OpenStack Dashboard (Horizon): New Bug description: When using glance v2 client, temporary upload file remains in /tmp folder after a successful or failed upload. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1689694/+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 1689692] [NEW] marker not found
Public bug reported: In my Ocata/RDO enviroment, nova version is 15.0.3, if I list instances with a marker&limit, sometimes it says "maker not found". More details of my operation steps: First, all instances are listed here without limit&marker: [root@host015 astute(keystone_admin)]# nova list --sort created_at:desc +--+--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+++-+--+ | 0e02233c-6c73-4bbe-bede-299ba41f44c3 | 11 | ERROR | - | NOSTATE | | | f6347ddb-e870-447f-8f14-3e3b57a610f2 | 11 | ERROR | - | NOSTATE | | | 5de9524f-1167-4ccb-b13c-13acf5435ead | 11 | ERROR | - | NOSTATE | | | 0548ebed-f0e4-4233-acf3-0339c4802f0d | 11 | ERROR | - | NOSTATE | | | 2c9ee616-eab9-4a4a-af3c-79f858c571d5 | 11 | ERROR | - | NOSTATE | | | 9aab5d6a-f5bd-459b-bb25-c04bc56efcf0 | 11 | ERROR | - | NOSTATE | | | f9ca1f1c-01f3-41a5-a68b-63f01fd87081 | 11 | ERROR | - | NOSTATE | | | dbb3955a-c768-4883-aae4-f3143f7b3a51 | 11 | ERROR | - | NOSTATE | | | a587dc5c-54c8-432b-9e38-174aae5e848c | 11 | ERROR | - | NOSTATE | | | 609ba5ca-bc49-4de5-be7a-16aab8fcb6d2 | 11 | ERROR | - | NOSTATE | | | b42e32e5-2aaa-46ee-b0bf-b08f29867af1 | 11 | ERROR | - | NOSTATE | | +--+--+++-+--+ Then, I try to list with the first instance id as marker, limited to 3, it's OK: [root@host015 astute(keystone_admin)]# nova list --sort created_at:desc --limit 3 --marker 0e02233c-6c73-4bbe-bede-299ba41f44c3 +--+--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+++-+--+ | f6347ddb-e870-447f-8f14-3e3b57a610f2 | 11 | ERROR | - | NOSTATE | | | 5de9524f-1167-4ccb-b13c-13acf5435ead | 11 | ERROR | - | NOSTATE | | | 0548ebed-f0e4-4233-acf3-0339c4802f0d | 11 | ERROR | - | NOSTATE | | +--+--+++-+--+ Then, I try to list with another instance, limited to 3, it's error: [root@host015 astute(keystone_admin)]# nova list --sort created_at:desc --limit 3 --marker a587dc5c-54c8-432b-9e38-174aae5e848c ERROR (BadRequest): marker [a587dc5c-54c8-432b-9e38-174aae5e848c] not found (HTTP 400) (Request-ID: req-308371f4-2962-4f3f-8d4c-69bf8c19664f) That's because no enough instance of limitation after the marker? When I set limitation to 2, it's OK: [root@host015 astute(keystone_admin)]# nova list --sort created_at:desc --limit 2 --marker a587dc5c-54c8-432b-9e38-174aae5e848c +--+--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+++-+--+ | 609ba5ca-bc49-4de5-be7a-16aab8fcb6d2 | 11 | ERROR | - | NOSTATE | | | b42e32e5-2aaa-46ee-b0bf-b08f29867af1 | 11 | ERROR | - | NOSTATE | | +--+--+++-+--+ My question: Why does not limitation work when no enough instance ? ** Affects: nova Importance: Undecided Status: New -- 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/1689692 Title: marker not found Status in OpenStack Compute (nova): New Bug description: In my Ocata/RDO enviroment, nova version is 15.0.3, if I list instances with a marker&limit, sometimes it says "maker not found". More details of my operation steps: First, all instances are listed here without limit&marker: [root@host015 astute(keystone_admin)]# nova list --sort created_at:desc +--+--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+++-+--+ | 0e02233c-6c73-4bbe-bede-299ba41f44c3 | 11 | ERROR | - | NOSTATE | | | f6347ddb-e870-447f-8f14-3e3b57a610f2 | 11 | ERROR | - | NOSTATE |
[Yahoo-eng-team] [Bug 1687401] Re: Keystone 403 Forbidden
I am unable to communicate with Keystone via the HTTP API, I have tried both
internal and admin endpoints but I always get a 401 Unauthorised.
When accessing Keystone properties in the Dashboard (horizon) I also get a 403,
however, everything else works fine.
I have also tried manually composing some HTTP requests from the CLI:
curl -vv -X POST -H 'Content-Type: application/json' -d '{
"auth": {
"identity": {
"methods": ["password"],
"password": {
"user": {
"name": "tiferrei",
"domain": { "id": "default" },
"password": ""
}
}
},
"scope": {
"project": {
"name": "default",
"domain": { "id": "default" }
}
}
}
}' http://controller:5000/v3/auth/tokens ; echo
And:
curl -vv -X POST -H 'Content-Type: application/json' -d '{
"auth": {
"identity": {
"methods": ["password"],
"password": {
"user": {
"name": "tiferrei",
"domain": { "id": "default" },
"password": ""
}
}
},
"scope": {
"project": {
"name": "default",
"domain": { "id": "default" }
}
}
}
}' http://controller:35357/v3/auth/tokens ; echo
They both return:
{"error": {"message": "The request you have made requires authentication.",
"code": 401, "title": "Unauthorized"}}
Any ideas as to why I'm being denied access to Keystone?
** Summary changed:
- Horizon 403 Forbidden
+ Keystone 403 Forbidden
** Also affects: keystone
Importance: Undecided
Status: New
--
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/1687401
Title:
Keystone 403 Forbidden
Status in OpenStack Dashboard (Horizon):
Invalid
Status in OpenStack Identity (keystone):
New
Bug description:
Hello there,
I have been struggling a bit with moving the horizon page from
domain.com/horizon to domain.com/ + setting up HTTPS, here's what I have tied:
- [General 403
debugging](https://askubuntu.com/questions/292968/apache2-forbidden-you-dont-have-permission-to-access-dir-on-this-server)
- [General 403
debugging](https://unix.stackexchange.com/questions/169513/403-forbidden-you-dont-have-permission-to-access-on-this-server-apache2)
- [403 fix for
Horizon](https://fosshelp.blogspot.co.uk/2014/02/openstack-horizon-you-dont-have.html)
- [General 403
debugging](https://stackoverflow.com/questions/10873295/error-message-forbidden-you-dont-have-permission-to-access-on-this-server)
- [Launchpad 403 knwon (and fixed) bug
](https://bugs.launchpad.net/devstack/+bug/1243075)
- [HTTPS config guide (from
Juno)](https://docs.openstack.org/juno/config-reference/content/configure-dashboard.html#after-example)
### Environment
- Followed the latest installation guide (Ocata)
- Apache2 version: Apache/2.4.18 (Ubuntu)
- Ubuntu 16.04.2 LTS AMD64
### Configuration
**local_settings.py**
https://paste.debian.net/930199/
**openstack-dashboard.conf**
https://paste.debian.net/930200/
**error.log**
https://paste.debian.net/930201/
This leaves me with some funny results, the login page loads but is
missing CSS, only plain HTML. When I log in, everything else gives me
a `403`.
Any help would be appreciated.
Thank you,
Tiago Ferreira
m...@tiferrei.com
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1687401/+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 1689644] [NEW] Keystone does not report microversion headers
Public bug reported: Keystone is now behind the other projects in reporting the microversions in the microversion header ** Affects: keystone Importance: Undecided Status: New -- 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/1689644 Title: Keystone does not report microversion headers Status in OpenStack Identity (keystone): New Bug description: Keystone is now behind the other projects in reporting the microversions in the microversion header To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1689644/+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 1683580] Re: gate-neutron-dynamic-routing-dsvm-tempest-api failure by "BGP Speaker extension is not enabled"
** No longer affects: cinder -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1683580 Title: gate-neutron-dynamic-routing-dsvm-tempest-api failure by "BGP Speaker extension is not enabled" Status in neutron: In Progress Status in OpenStack Object Storage (swift): New Bug description: In a stable branch of devstack, API extensions list used in tempest is harded code since [1] and BGP is not included in this list[2]. tempest tests using extensions that is not listed in DEFAULT_NET_EXT may be affected by this. You can look the results of tempest tests from the following. http://logs.openstack.org/39/443839/1/check/gate-neutron-dynamic- routing-dsvm-tempest- api/85fa064/console.html#_2017-04-17_07_14_03_346935 [1] Iac8f858793d5ab514d6ba69b68d5420acd0fe903 I1a4d1ea8c8d34b8cd1020e76597db6c67f85f6ec [2] http://logs.openstack.org/39/443839/1/check/gate-neutron-dynamic-routing-dsvm-tempest-api/85fa064/logs/tempest_conf.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1683580/+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 1689284] Re: should capture quota exceed error from cinder when create image for volume backed instance
Oh I see, here: https://github.com/openstack/nova/blob/5532d6f4042aa41d1bd9e2e4a7fabb63a0ab6b93/nova/compute/api.py#L2987 That would raise this exception: https://github.com/openstack/nova/blob/5532d6f4042aa41d1bd9e2e4a7fabb63a0ab6b93/nova/volume/cinder.py#L242 And yeah we don't handle that in the exceptions here: https://github.com/openstack/nova/blob/5532d6f4042aa41d1bd9e2e4a7fabb63a0ab6b93/nova/api/openstack/compute/servers.py#L996 ** Changed in: nova Status: New => Triaged ** Changed in: nova Importance: Undecided => Medium ** Also affects: nova/newton Importance: Undecided Status: New ** Also affects: nova/ocata Importance: Undecided Status: New -- 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/1689284 Title: should capture quota exceed error from cinder when create image for volume backed instance Status in OpenStack Compute (nova): Triaged Status in OpenStack Compute (nova) newton series: New Status in OpenStack Compute (nova) ocata series: New Bug description: When create image for a volume backed instance, nova will create snapshots for all volumes attached to the instance in Cinder, and if quota exceed in Cinder, HTTP 500 will raise, we should capture this error and raise 404. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1689284/+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 1689626] Re: Call Us +1-844-489-0820 TurboTax™ Support Live Support for TurboTax™ Technical Problems | TurboTax™ Phone Number To Talk To A Live Person | Talk To A Live Person On
** Project changed: nova => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void 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/1689626 Title: Call Us +1-844-489-0820 TurboTax™ Support Live Support for TurboTax™ Technical Problems | TurboTax™ Phone Number To Talk To A Live Person | Talk To A Live Person On The Phone | Turbotax Phone Number Live Person Status in NULL Project: Invalid Bug description: Call Us +1-844-489-0820 TurboTax™ Support Live Support for TurboTax™ Technical Problems | TurboTax™ Phone Number To Talk To A Live Person | Talk To A Live Person On The Phone | Turbotax Phone Number Live Person +1-844-489-0820 TurboTax™ Customer Support Talk To A Live Person | TurboTax™ customer support phone number with shortest wait time and best customer care service for intuit chat, phone and email support for TurboTax. +1-844-489-0820 - Support for TurboTax™ turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person, turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number c
[Yahoo-eng-team] [Bug 1689626] [NEW] Call Us +1-844-489-0820 TurboTax™ Support Live Support for TurboTax™ Technical Problems | TurboTax™ Phone Number To Talk To A Live Person | Talk To A Live Person O
Private bug reported: Call Us +1-844-489-0820 TurboTax™ Support Live Support for TurboTax™ Technical Problems | TurboTax™ Phone Number To Talk To A Live Person | Talk To A Live Person On The Phone | Turbotax Phone Number Live Person +1-844-489-0820 TurboTax™ Customer Support Talk To A Live Person | TurboTax™ customer support phone number with shortest wait time and best customer care service for intuit chat, phone and email support for TurboTax. +1-844-489-0820 - Support for TurboTax™ turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person, turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax phone number customer support, turbotax phone number to talk to a live person,turbotax phone number to talk to a live person, turbotax phone number live person, turbotax phone number live person, turbotax phone number to talk to a live person, turbotax
[Yahoo-eng-team] [Bug 1689623] [NEW] ds-identify: disable ec-strict for s390x in yaketty
Public bug reported: DS-identify runs with DI_EC2_STRICT_ID_DEFAULT="warn" on s390x using yakkety. With zesty EC2_STRICT is set to "true". Having it set to "true" is important, as on s390x the OpenStack datasource cannot be detected. Each ds-identify run results in ec2-maybe (if no other detectable ds is present). This could cause problems in OpenStack environments where only the Openstack metadata service is available (without ec2 support). In this special case it's important that the good all "try out everything" algorithm gets enabled. Therefore the request is to set DI_EC2_STRICT_ID_DEFAULT="true" for yakkety as well! # apt install cloud-init Reading package lists... Done Building dependency tree Reading state information... Done cloud-init is already the newest version (0.7.9-90-g61eb03fe-0ubuntu1~16.10.1). # apt-cache show cloud-init Package: cloud-init Priority: extra Section: admin Installed-Size: 1455 Maintainer: Scott Moser Architecture: all Version: 0.7.9-90-g61eb03fe-0ubuntu1~16.10.1 Depends: cloud-guest-utils | cloud-utils, ifupdown (>= 0.6.10ubuntu5), procps, python3 (>= 3.2), python3-requests (>= 0.8.2), python3-serial, debconf (>= 0.5) | debconf-2.0, init-system-helpers (>= 1.18~), python3-configobj, python3-jinja2, python3-jsonpatch, python3-oauthlib, python3-prettytable, python3-six, python3-yaml, python3:any (>= 3.3.2-2~) Recommends: eatmydata, gdisk, software-properties-common Filename: pool/main/c/cloud-init/cloud-init_0.7.9-90-g61eb03fe-0ubuntu1~16.10.1_all.deb Size: 307142 MD5sum: 85dac3c31c9dc1085f814acd2d46b56c SHA1: a333708d949fa05f296356877a8b7f0ae88da4e6 SHA256: 6051cf4897c1268dbce3c41909734bb54958bfe2fd0e48960cedad92be5599eb Description-en: Init scripts for cloud instances Cloud instances need special scripts to run during initialisation to retrieve and install ssh keys and to let the user run various scripts. Description-md5: 8719ef0e4178017b7147590b1fde082e Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 9m Task: ubuntu-core, cloud-image, ubuntu-core Package: cloud-init Priority: extra Section: admin Installed-Size: 1413 Maintainer: Scott Moser Architecture: all Version: 0.7.8-15-g6e45ffb-0ubuntu1 Depends: cloud-guest-utils | cloud-utils, ifupdown (>= 0.6.10ubuntu5), procps, python3 (>= 3.2), python3-requests (>= 0.8.2), python3-serial, debconf (>= 0.5) | debconf-2.0, init-system-helpers (>= 1.18~), python3-configobj, python3-jinja2, python3-jsonpatch, python3-oauthlib, python3-prettytable, python3-six, python3-yaml, python3:any (>= 3.3.2-2~) Recommends: eatmydata, gdisk, software-properties-common Filename: pool/main/c/cloud-init/cloud-init_0.7.8-15-g6e45ffb-0ubuntu1_all.deb Size: 281760 MD5sum: 8bd4212c57d3e731c1d93372c2cf13ec SHA1: 3801b47c2e8afb7a721c9394d7658a7621efd66f SHA256: f2b87a3db886fb41cb4000f23e88a54b04e5eca890eb3a682c8b154970b838d9 Description-en: Init scripts for cloud instances Cloud instances need special scripts to run during initialisation to retrieve and install ssh keys and to let the user run various scripts. Description-md5: 8719ef0e4178017b7147590b1fde082e Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 9m Task: ubuntu-core, cloud-image, ubuntu-core # uname -a Linux your-host-name 4.8.0-51-generic #54-Ubuntu SMP Tue Apr 25 16:33:55 UTC 2017 s390x s390x s390x GNU/Linux # cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" NAME="Ubuntu" VERSION="16.10 (Yakkety Yak)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.10" VERSION_ID="16.10" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="http://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=yakkety UBUNTU_CODENAME=yakkety ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1689623 Title: ds-identify: disable ec-strict for s390x in yaketty Status in cloud-init: New Bug description: DS-identify runs with DI_EC2_STRICT_ID_DEFAULT="warn" on s390x using yakkety. With zesty EC2_STRICT is set to "true". Having it set to "true" is important, as on s390x the OpenStack datasource cannot be detected. Each ds-identify run results in ec2-maybe (if no other detectable ds is present). This could cause problems in OpenStack environments where only the Openstack metadata service is available (without ec2 support). In this special case it's important that the good all "try out everything" algorithm gets enabled. Therefore the request is to set DI_EC2_STRICT_ID_DEFAULT="true" for yakkety as well! # apt install cloud-init Reading package lists... Done Building dependency tree Reading state information... Done cloud-init is already
[Yahoo-eng-team] [Bug 1570122] Re: ipv6 prefix delegated subnets are not accessable external of the router they are attached.
Added neturon/UCA tasks so it shows up more obviously for the Triagers of those components ** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-archive 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/1570122 Title: ipv6 prefix delegated subnets are not accessable external of the router they are attached. Status in Ubuntu Cloud Archive: New Status in neutron: Fix Released Status in neutron package in Ubuntu: Confirmed Bug description: currently ip6tables in the qrouter namespace has the following rule. This causes unmarked packets to drop. -A neutron-l3-agent-scope -o qr-ca9ffa4f-fd -m mark ! --mark 0x401/0x -j DROP It seems that prefix delegated subnets don't get that mark set on incoming trafic from the gateway port, I had to add my own rule to do that. ip6tables -t mangle -A neutron-l3-agent-scope -i qg-ac290c4b-4f -j MARK --set-xmark 0x401/0x At the moment that is probably too permissive, it should likely be limited based on the prefix delegated. with a '-d dead:beef:cafe::/64' or whatever the delegation is (tested this and it does work). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1570122/+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 1689510] [NEW] Wrong DVR and HA properties reported to non-admin users
Public bug reported: Our routers are HA-DVR by default. Executing "openstack router list" as user with admin privileges correctly returns Distributed=True, HA=True. The same command executed as a regular user returns Distributed=False, HA=False which is factually incorrect. Seems to me that regular users are being misinformed about the properties of their routers. Is this by design or is it a bug? If it is by design, what reason would we have to lie to our users? ** 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/1689510 Title: Wrong DVR and HA properties reported to non-admin users Status in neutron: New Bug description: Our routers are HA-DVR by default. Executing "openstack router list" as user with admin privileges correctly returns Distributed=True, HA=True. The same command executed as a regular user returns Distributed=False, HA=False which is factually incorrect. Seems to me that regular users are being misinformed about the properties of their routers. Is this by design or is it a bug? If it is by design, what reason would we have to lie to our users? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1689510/+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 1667679] Re: Setting quota fails saying admin project is not a valid project
** Also affects: kolla-kubernetes Importance: Undecided Status: New ** Changed in: kolla-kubernetes Assignee: (unassigned) => Chung Chih, Hung (lyanchih) -- 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/1667679 Title: Setting quota fails saying admin project is not a valid project Status in kolla-kubernetes: New Status in OpenStack Compute (nova): Confirmed Status in tripleo: Fix Released Bug description: This is what's in the logs http://logs.openstack.org/15/359215/63 /check-tripleo/gate-tripleo-ci-centos-7-ovb- ha/3465882/console.html#_2017-02-24_11_07_08_893276 2017-02-24 11:07:08.893276 | 2017-02-24 11:07:02.000 | 2017-02-24 11:07:02,929 INFO: + openstack quota set --cores -1 --instances -1 --ram -1 b0fe52b0ac15450ba0a38ac9acd8fea8 2017-02-24 11:07:08.893365 | 2017-02-24 11:07:08.000 | 2017-02-24 11:07:08,674 INFO: Project ID b0fe52b0ac15450ba0a38ac9acd8fea8 is not a valid project. (HTTP 400) (Request-ID: req-9e0a00b7-75ae-41d5-aeed-705bb1a54bae) 2017-02-24 11:07:08.893493 | 2017-02-24 11:07:08.000 | 2017-02-24 11:07:08,758 INFO: [2017-02-24 11:07:08,757] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/post-configure.d']' returned non-zero exit status 1] To manage notifications about this bug go to: https://bugs.launchpad.net/kolla-kubernetes/+bug/1667679/+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 1689504] [NEW] Favicons incorrectly displayed on Apple devices
Public bug reported: Apple devices handle website icons through Apple Touch Icon which requires apple-touch-icon tag in stylesheet. Also Safari pinned tab icon requires a separate SVG for being correctly displayed. ** Affects: horizon Importance: Undecided Assignee: Mateusz Kowalski (makowals) Status: In Progress -- 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/1689504 Title: Favicons incorrectly displayed on Apple devices Status in OpenStack Dashboard (Horizon): In Progress Bug description: Apple devices handle website icons through Apple Touch Icon which requires apple-touch-icon tag in stylesheet. Also Safari pinned tab icon requires a separate SVG for being correctly displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1689504/+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 1687544] Re: tempest job failure (keystone related?)
fixed in rally
** 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/1687544
Title:
tempest job failure (keystone related?)
Status in neutron:
Fix Released
Bug description:
on networking-midonet gate, both of ml2 and v2 jobs are failing.
ft1.1:
neutron.tests.tempest.api.admin.test_floating_ips_admin_actions.FloatingIPAdminTestJSON.test_associate_floating_ip_with_port_from_another_tenant[id-6ee9-4e99-5b15-b8e1-aa7df92ca589,negative]_StringException:
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2017-05-02 05:40:22,447 14623 INFO [tempest.lib.common.rest_client]
Request
(FloatingIPAdminTestJSON:test_associate_floating_ip_with_port_from_another_tenant):
201 POST http://10.36.171.211/identity/v3/auth/tokens
2017-05-02 05:40:22,448 14623 DEBUG[tempest.lib.common.rest_client]
Request - Headers: {'Content-Type': 'application/json', 'Accept':
'application/json'}
Body:
Response - Headers: {'status': '201', u'server': 'Apache/2.4.18
(Ubuntu)', u'x-subject-token': '', u'date': 'Tue, 02 May 2017 05:40:22
GMT', 'content-location': 'http://10.36.171.211/identity/v3/auth/tokens',
u'content-type': 'application/json', u'x-openstack-request-id':
'req-45f6388d-a217-498f-a680-bfd6210fe7d7', u'vary': 'X-Auth-Token',
u'content-length': '2382', u'connection': 'close'}
Body: {"token": {"is_domain": false, "methods": ["password"],
"roles": [{"id": "05c2fe7912fa44d890676d7f087a0ccf", "name": "admin"}, {"id":
"0593b5fa632a496e865a4ca65e18baa1", "name": "Member"}], "expires_at":
"2017-05-02T06:40:22.00Z", "project": {"domain": {"id": "default", "name":
"Default"}, "id": "be5d7c7060034c33bba28e0299d0a5bd", "name":
"tempest-FloatingIPAdminTestJSON-304146397"}, "catalog": [{"endpoints":
[{"url": "http://10.36.171.211/placement";, "interface": "public", "region":
"RegionOne", "region_id": "RegionOne", "id":
"73fe7cfa06574ea084a14ffe5cc04f4f"}], "type": "placement", "id":
"2aca05580953402fa9f5c0a73805e9ad", "name": "placement"}, {"endpoints":
[{"url": "http://10.36.171.211/identity";, "interface": "public", "region":
"RegionOne", "region_id": "RegionOne", "id":
"78989aee5a1a4ec7b3755c304a7b22cb"}, {"url": "http://10.36.171.211/identity";,
"interface": "admin", "region": "RegionOne", "region_id": "RegionOne", "id":
"84e6b9dd0369400eb54de27fe19cec35"}], "type": "identity", "id":
"82c9a82012664518a1aeaea9baca66e6", "name": "keystone"}, {"endpoints": [{"url":
"http://10.36.171.211:9292";, "interface": "public", "region": "RegionOne",
"region_id": "RegionOne", "id": "d8e527942b704f79b5f8d58cef59672e"}], "type":
"image", "id": "a4b7c39e887b494686ae35954845bc9a", "name": "glance"},
{"endpoints": [{"url":
"http://10.36.171.211:8774/v2/be5d7c7060034c33bba28e0299d0a5bd";, "interface":
"public", "region": "RegionOne", "region_id": "RegionOne", "id":
"8971013f2a6e40c3a3bef2b8a04721b6"}], "type": "compute_legacy", "id":
"add743da019f411cbafbcff634bc26dd", "name": "nova_legacy"}, {"endpoints":
[{"url": "http://10.36.171.211:9696/";, "interface": "public", "region":
"RegionOne", "region_id": "RegionOne", "id":
"60ac7875fd1f49e7933724859c1fcd02"}], "type": "network", "id":
"b33998fa154d44978bbc3425a4e387a3", "name": "neutron"}, {"endpoints": [{"url":
"http://10.36.171.211:8774/v2.1";, "interface": "public", "region": "RegionOne",
"region_id": "RegionOne", "id": "fdc48a91c5ee4213a1b385861afb1b31"}], "type":
"compute", "id": "bf04908653054d38bab6555ef40e3baf", "name": "nova"}], "user":
{"password_expires_at": null, "domain": {"id": "default", "name": "Default"},
"id": "8935acfa6bfa48169dd19c3d84aa8355", "name":
"tempest-FloatingIPAdminTestJSON-304146397"}, "audit_ids":
["gU7OX01KRwebKUNSdCdhMA"], "issued_at": "2017-05-02T05:40:22.00Z"}}
2017-05-02 05:40:23,932 14623 INFO [tempest.lib.common.rest_client]
Request
(FloatingIPAdminTestJSON:test_associate_floating_ip_with_port_from_another_tenant):
201 POST http://10.36.171.211:9696/v2.0/floatingips 1.483s
2017-05-02 05:40:23,932 14623 DEBUG[tempest.lib.common.rest_client]
Request - Headers: {'Content-Type': 'application/json', 'X-Auth-Token':
'', 'Accept': 'application/json'}
Body: {"floatingip": {"floating_network_id":
"d7c26168-469d-45ee-94f5-bd6bf474b048"}}
Response - Headers: {u'x-openstack-request-id':
'req-9d69594f-a433-4d0a-aec9-160ef32a6ae0', 'status': '201', u'content-length':
'460', u'date': 'Tue, 02 May 2017 05:40:23 GMT', 'content-location':
'http://10.36.171.211:9696/v2.0/floatingips', u'content-type':
'application/json', u'connection': 'close'}
Body: {"floatingip": {"router_id": null, "status": "ACTIVE",
"description": "", "updated_at": "2017-05-02T05:40:23Z", "floating_network_id":
"d7c26168-469d-45ee-94f5-bd6bf474b048", "fixed_ip_address": null,
"floa
