[Yahoo-eng-team] [Bug 1268480] Re: assertTrue(isinstance()) in tests should be replace with assertIsInstance()
Reviewed: https://review.openstack.org/315474 Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=d744f813a0509d91d230a3260f4d1dcb7fed8c0f Submitter: Jenkins Branch:master commit d744f813a0509d91d230a3260f4d1dcb7fed8c0f Author: sharat.sharma Date: Thu May 12 16:18:15 2016 +0530 Changed assertTrue(isinstance()) to assertIsInstance. Change-Id: I0cb3e994ce813ceedaad91d441c20e7e67946c39 Closes-Bug: #1268480 ** Changed in: zaqar Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1268480 Title: assertTrue(isinstance()) in tests should be replace with assertIsInstance() Status in anvil: Invalid Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: In Progress Status in CloudRoast: In Progress Status in congress: Fix Released Status in Glance: Fix Released Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Released Status in Murano: Fix Released Status in networking-powervm: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Invalid Status in python-keystoneclient: Fix Released Status in python-manilaclient: Fix Released Status in python-novaclient: Fix Released Status in python-openstackclient: Invalid Status in OpenStack SDK: Fix Released Status in python-rackclient: Invalid Status in Rally: In Progress Status in Sahara: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in Vitrage: Fix Released Status in zaqar: Fix Released Bug description: some of tests use different method of assertTrue(isinstance(A, B)) or assertEqual(type(A), B). The correct way is to use assertIsInstance(A, B) provided by testtools To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1268480/+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 1587253] [NEW] Make logic network mtu to be Configurable
Public bug reported: In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow: ------ --- | VM1 || VM2 | | VM3 | ------ --- | || | || | || ------ --- | tenant1 || tenant2 | | tenant3 | | network || network | | network | ------ --- | || | || | || --- | | | proivder network | | mtu=9000| --- | || | || | || ------ --- | Physic || Physic | | physic | | network1|| network2| | network3| | mtu=1500|| mtu=1200| | mtu=9000| ------ --- tenant1 network pass through physic network1 tenant2 network pass through physic network2 tenant3 network pass through physic network3 So, I suggest to make the logic network MTU to be configurable to solve the problem. ** Affects: neutron Importance: Undecided Status: New ** Description changed: In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow: - ------ --- - | VM1 || VM2 | | VM3 | - ------ --- -| || -| || -| || - ------ --- - | tenant1 || tenant2 | | tenant3 | - | network || network | | network | - ------ --- -| || -| || -| || - --- - | | - | proivder network | - | mtu=9000| - --- -| || -| || -| || - ------ --- - | Physic || Physic | | physic | - | network1|| network2| | network3| - | mtu=1500|| mtu=1200| | mtu=9000| - ------ --- + ------ --- + | VM1 || VM2 | | VM3 | + ------ --- + | || + | || + | || + ------ --- + | tenant1 || tenant2 | | tenant3 | + | network || network | | network | + ------ --- + | || + | || + | || + --- + | | + | proivder network | + | mtu=9000| + ---
[Yahoo-eng-team] [Bug 1587240] [NEW] Orchestration resources out of scope
Public bug reported: When we have large number of resources, horizon can't appear to show all resource With a screen shot to show the case, we need to have way to present all resources properly in console. ** Affects: horizon Importance: Undecided Status: New ** Tags: heat ** Attachment added: "resource_out_of_scope.jpg" https://bugs.launchpad.net/bugs/1587240/+attachment/4673266/+files/resource_out_of_scope.jpg -- 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/1587240 Title: Orchestration resources out of scope Status in OpenStack Dashboard (Horizon): New Bug description: When we have large number of resources, horizon can't appear to show all resource With a screen shot to show the case, we need to have way to present all resources properly in console. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1587240/+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 1587239] [NEW] cover job is failing too frequently
Public bug reported:
this appears a lot in the cover job logs:
2016-05-31 03:10:56.236 | pkg_resources.ContextualVersionConflict: (amqp
2.0.0 (/home/jenkins/workspace/keystone-coverage-
db/.tox/cover/lib/python2.7/site-packages),
Requirement.parse('amqp<2.0,>=1.4.9'), set(['kombu']))
Looking at the logs, this was installed:
2016-05-31 03:10:47.259 | cover installed: amqp==2.0.0,...kombu==3.0.35
Which goes against global-requirements:
amqp>=1.4.0,<2.0 # LGPL
And upper-requirements:
amqp===1.4.9
The tox target does not honor the upper constraints, but has a comment
indicating it's not possible? I'm not sure.
[testenv:cover]
# Also do not run test_coverage_ext tests while gathering coverage as those
# tests conflict with coverage.
# NOTE(sdague): this target does not use constraints because
# upstream infra does not yet support it. Once that's fixed, we can
# drop the install_command.
install_command = pip install -U --force-reinstall {opts} {packages}
commands =
find keystone -type f -name "*.pyc" -delete
python setup.py testr --coverage --testr-args='{posargs}'
** Affects: keystone
Importance: High
Status: New
** Changed in: keystone
Importance: Undecided => High
** Description changed:
this appears a lot in the cover job logs:
2016-05-31 03:10:56.236 | pkg_resources.ContextualVersionConflict: (amqp
2.0.0 (/home/jenkins/workspace/keystone-coverage-
db/.tox/cover/lib/python2.7/site-packages),
Requirement.parse('amqp<2.0,>=1.4.9'), set(['kombu']))
- Looking at:
+ Looking at the logs, this was installed:
2016-05-31 03:10:47.259 | cover installed: amqp==2.0.0,...kombu==3.0.35
Which goes against global-requirements:
amqp>=1.4.0,<2.0 # LGPL
And upper-requirements:
amqp===1.4.9
The tox target does not honor the upper constraints, but has a comment
indicating it's not possible? I'm not sure.
[testenv:cover]
# Also do not run test_coverage_ext tests while gathering coverage as those
# tests conflict with coverage.
# NOTE(sdague): this target does not use constraints because
# upstream infra does not yet support it. Once that's fixed, we can
# drop the install_command.
install_command = pip install -U --force-reinstall {opts} {packages}
commands =
- find keystone -type f -name "*.pyc" -delete
- python setup.py testr --coverage --testr-args='{posargs}'
+ find keystone -type f -name "*.pyc" -delete
+ python setup.py testr --coverage --testr-args='{posargs}'
--
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/1587239
Title:
cover job is failing too frequently
Status in OpenStack Identity (keystone):
New
Bug description:
this appears a lot in the cover job logs:
2016-05-31 03:10:56.236 | pkg_resources.ContextualVersionConflict:
(amqp 2.0.0 (/home/jenkins/workspace/keystone-coverage-
db/.tox/cover/lib/python2.7/site-packages),
Requirement.parse('amqp<2.0,>=1.4.9'), set(['kombu']))
Looking at the logs, this was installed:
2016-05-31 03:10:47.259 | cover installed:
amqp==2.0.0,...kombu==3.0.35
Which goes against global-requirements:
amqp>=1.4.0,<2.0 # LGPL
And upper-requirements:
amqp===1.4.9
The tox target does not honor the upper constraints, but has a comment
indicating it's not possible? I'm not sure.
[testenv:cover]
# Also do not run test_coverage_ext tests while gathering coverage as those
# tests conflict with coverage.
# NOTE(sdague): this target does not use constraints because
# upstream infra does not yet support it. Once that's fixed, we can
# drop the install_command.
install_command = pip install -U --force-reinstall {opts} {packages}
commands =
find keystone -type f -name "*.pyc" -delete
python setup.py testr --coverage --testr-args='{posargs}'
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1587239/+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 1490787] Re: show_numbers(self.data) on Pie Charts are broken
[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.] ** Changed in: horizon Status: Incomplete => Expired -- 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/1490787 Title: show_numbers(self.data) on Pie Charts are broken Status in OpenStack Dashboard (Horizon): Expired Bug description: show_numbers(self.data) in horizon/static/horizon/js/horizon.d3piechart.js obviously doesn't work as intended any longer. If you turn this on, It prints: [object Object] on top of the Pie Chart. o.O To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1490787/+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 1493407] Re: Can't add member role on a project on latest DevStack
[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.] ** Changed in: horizon Status: Incomplete => Expired -- 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/1493407 Title: Can't add member role on a project on latest DevStack Status in OpenStack Dashboard (Horizon): Expired Bug description: Deploy latest stack. 1. Login as admin, create project with a member (Identity -> Projects-> +Create project) 2. Try to add more roles to a member (Edit project -> members) Actual result: Not all of the tries, but often enough you will be Unauthorized, and after you login, page layout will be broken(refer screenshot "second_login.png"). When you are not Unauthorized error message shown "Unable to modify project" Expected result: No error appeard, and roles added To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1493407/+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 1587219] [NEW] unable to retrieve project list
Public bug reported:
in Newest devstack,dashboard error:Error: Unable to retrieve project
list.
However,in CLI,curl command: curl -g -i -X GET
http://192.168.139.142/identity/v3/users/ac4292a3f5bf40e5b75e25b8215c7c5c/projects
-H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H
"X-Auth-Token: 9bc1fc6b9cc54fc48d833791e00cfa4a"
gets them:
HTTP/1.1 200 OK
Date: Tue, 31 May 2016 02:50:59 GMT
Server: Apache/2.4.7 (Ubuntu)
Vary: X-Auth-Token
x-openstack-request-id: req-18a00aa9-28c0-41c0-99a3-a63c8293affe
Content-Length: 990
Content-Type: application/json
{"links": {"self":
"http://192.168.139.142/identity/v3/users/ac4292a3f5bf40e5b75e25b8215c7c5c/projects";,
"previous": null, "next": null}, "projects": [{"is_domain": false,
"description": "", "links": {"self":
"http://192.168.139.142/identity/v3/projects/17e4851935624c60a43c97abebe20ae9"},
"enabled": true, "id": "17e4851935624c60a43c97abebe20ae9", "parent_id":
"default", "domain_id": "default", "name": "alt_demo"}, {"is_domain":
false, "description": "", "links": {"self":
"http://192.168.139.142/identity/v3/projects/62c82523d3ac44e683962be71a87c63b"},
"enabled": true, "id": "62c82523d3ac44e683962be71a87c63b", "parent_id":
"default", "domain_id": "default", "name": "demo"}, {"is_domain": false,
"description": "Bootstrap project for initializing the cloud.", "links":
{"self":
"http://192.168.139.142/identity/v3/projects/e8c17c54df62455a9305b1c31b298596"},
"enabled": true, "id": "e8c17c54df62455a9305b1c31b298596", "parent_id":
"default", "domain_id": "default", "name":
"admin"}]}root@dev:/opt/devstack#
** Affects: horizon
Importance: Undecided
Status: New
--
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/1587219
Title:
unable to retrieve project list
Status in OpenStack Dashboard (Horizon):
New
Bug description:
in Newest devstack,dashboard error:Error: Unable to retrieve project
list.
However,in CLI,curl command: curl -g -i -X GET
http://192.168.139.142/identity/v3/users/ac4292a3f5bf40e5b75e25b8215c7c5c/projects
-H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H
"X-Auth-Token: 9bc1fc6b9cc54fc48d833791e00cfa4a"
gets them:
HTTP/1.1 200 OK
Date: Tue, 31 May 2016 02:50:59 GMT
Server: Apache/2.4.7 (Ubuntu)
Vary: X-Auth-Token
x-openstack-request-id: req-18a00aa9-28c0-41c0-99a3-a63c8293affe
Content-Length: 990
Content-Type: application/json
{"links": {"self":
"http://192.168.139.142/identity/v3/users/ac4292a3f5bf40e5b75e25b8215c7c5c/projects";,
"previous": null, "next": null}, "projects": [{"is_domain": false,
"description": "", "links": {"self":
"http://192.168.139.142/identity/v3/projects/17e4851935624c60a43c97abebe20ae9"},
"enabled": true, "id": "17e4851935624c60a43c97abebe20ae9",
"parent_id": "default", "domain_id": "default", "name": "alt_demo"},
{"is_domain": false, "description": "", "links": {"self":
"http://192.168.139.142/identity/v3/projects/62c82523d3ac44e683962be71a87c63b"},
"enabled": true, "id": "62c82523d3ac44e683962be71a87c63b",
"parent_id": "default", "domain_id": "default", "name": "demo"},
{"is_domain": false, "description": "Bootstrap project for
initializing the cloud.", "links": {"self":
"http://192.168.139.142/identity/v3/projects/e8c17c54df62455a9305b1c31b298596"},
"enabled": true, "id": "e8c17c54df62455a9305b1c31b298596",
"parent_id": "default", "domain_id": "default", "name":
"admin"}]}root@dev:/opt/devstack#
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1587219/+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 1587208] [NEW] Non admin is not able to view all ports of shared network
Public bug reported: If you create a shared network and create ports under say tenant_1 tenant, admin of both tenant_1 and another tenant say tenant_2 can view the port of shared (as well as non-shared) networks. However, if a non-admin of tenant_2 executes port-list, port(s) of shared network is not listed. In certain OpenStack driver environments, a port is created with a specific IP address and any knowledge of existing ports under a specific network (atleast shared network) is very useful and required, so that a port cannot even be attempted to be created with an already allocated IP address. In the case of shared networks, all ports created under it by any tenant should be visible to non-admins of any tenant. The network is shared anyway, so non-admins can get access to list of ports. This bug is related to mitaka version and will be applicable to liberty as well. ** Affects: neutron Importance: Undecided Assignee: Sridhar Venkat (svenkat) Status: In Progress ** Tags: api ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => Sridhar Venkat (svenkat) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1587208 Title: Non admin is not able to view all ports of shared network Status in neutron: In Progress Bug description: If you create a shared network and create ports under say tenant_1 tenant, admin of both tenant_1 and another tenant say tenant_2 can view the port of shared (as well as non-shared) networks. However, if a non-admin of tenant_2 executes port-list, port(s) of shared network is not listed. In certain OpenStack driver environments, a port is created with a specific IP address and any knowledge of existing ports under a specific network (atleast shared network) is very useful and required, so that a port cannot even be attempted to be created with an already allocated IP address. In the case of shared networks, all ports created under it by any tenant should be visible to non-admins of any tenant. The network is shared anyway, so non-admins can get access to list of ports. This bug is related to mitaka version and will be applicable to liberty as well. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1587208/+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 1582290] Re: tests depend on testresouces
I have confirmed with Doug Hellmann in #openstack-oslo that testresources is coming in via the fixtures extra. Thus, keystone does not have to have it added to test-requirements directly ** Changed in: keystone Status: In Progress => Won't Fix -- 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/1582290 Title: tests depend on testresouces Status in OpenStack Identity (keystone): Won't Fix Bug description: testresources needs to be specified in test-requirements.txt == FAIL: unittest2.loader._FailedTest.keystone.tests.unit.identity.backends.test_sql unittest2.loader._FailedTest.keystone.tests.unit.identity.backends.test_sql -- _StringException: Traceback (most recent call last): ImportError: Failed to import test module: keystone.tests.unit.identity.backends.test_sql Traceback (most recent call last): File "/usr/lib/python2.7/dist- packages/unittest2/loader.py", line 456, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python2.7/dist- packages/unittest2/loader.py", line 395, in _get_module_from_name __import__(name) File "/<>/keystone/tests/unit/identity/backends/test_sql.py", line 14, in from oslo_db.sqlalchemy import test_base as db_test File "/usr/lib/python2.7/dist- packages/oslo_db/sqlalchemy/test_base.py", line 17, in import testresources ImportError: No module named testresources To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1582290/+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 1586931] Re: TestServerBasicOps: Test fails with redundant step of deleting server
** Also 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/1586931
Title:
TestServerBasicOps: Test fails with redundant step of deleting server
Status in OpenStack Compute (nova):
New
Status in tempest:
In Progress
Bug description:
In
tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops,
last step: self.servers_client.delete_server(self.instance['id']) is
not necessary since there is cleanup in create_server, otherwise, it
may cause failure with following deletion of floating ip:
Here is the partial log:
2016-05-29 21:51:29.499 29791 INFO tempest.lib.common.rest_client
[req-c3588ac4-21ca-47c3-bdb1-62088efd7a8b ] Request
(TestServerBasicOps:test_server_basic_ops): 204 DELETE
https://:8774/v2/159886ce087a4f8fbfbcab14947d96b1/servers/6d44763b-ea79-4b5b-b57e-714191802c7c
0.465s
2016-05-29 21:51:29.499 29791 DEBUG tempest.lib.common.rest_client
[req-c3588ac4-21ca-47c3-bdb1-62088efd7a8b ] Request - Headers: {'Content-Type':
'application/json', 'Accept': 'application/json', 'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '204', 'content-length': '0',
'content-location':
'https://:8774/v2/159886ce087a4f8fbfbcab14947d96b1/servers/6d44763b-ea79-4b5b-b57e-714191802c7c',
'date': 'Mon, 30 May 2016 02:51:29 GMT', 'x-compute-request-id':
'req-c3588ac4-21ca-47c3-bdb1-62088efd7a8b', 'content-type': 'application/json',
'connection': 'close'}
Body: _log_request_full tempest/lib/common/rest_client.py:422
2016-05-29 21:51:30.410 29791 INFO tempest.lib.common.rest_client
[req-db2323f5-3d58-4fd7-ae51-44f5525c6689 ] Request
(TestServerBasicOps:_run_cleanups): 500 DELETE
https://:8774/v2/159886ce087a4f8fbfbcab14947d96b1/os-floating-ips/948912f6-ce03-4856-922b-59c4f16d3740
0.910s
2016-05-29 21:51:30.410 29791 DEBUG tempest.lib.common.rest_client
[req-db2323f5-3d58-4fd7-ae51-44f5525c6689 ] Request - Headers: {'Content-Type':
'application/json', 'Accept': 'application/json', 'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '500', 'content-length': '224',
'content-location':
'https://:8774/v2/159886ce087a4f8fbfbcab14947d96b1/os-floating-ips/948912f6-ce03-4856-922b-59c4f16d3740',
'date': 'Mon, 30 May 2016 02:51:30 GMT', 'x-compute-request-id':
'req-db2323f5-3d58-4fd7-ae51-44f5525c6689', 'content-type': 'application/json;
charset=UTF-8', 'connection': 'close'}
Body: {"computeFault": {"message": "Unexpected API Error. Please
report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if
possible.\n",
"code": 500}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1586931/+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 1586816] Re: SAWarning: in_(empty sequence) from get_networks_segments()
Reviewed: https://review.openstack.org/322618
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=1080620e5af6d3aae8034f516ded86dda257282b
Submitter: Jenkins
Branch:master
commit 1080620e5af6d3aae8034f516ded86dda257282b
Author: Hong Hui Xiao
Date: Mon May 30 03:13:21 2016 +
Dont use query if network_ids is empty
A warning could be found in SQLAlchemy, if handling empty WHERE IN
clauses. This is found at neutron.db.segments_db.get_networks_segments
To avoid it, just return empty dict in such case.
Change-Id: I3cf727dede1d5909aeefbf852332818164ad3777
Closes-bug: #1586816
** 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/1586816
Title:
SAWarning: in_(empty sequence) from get_networks_segments()
Status in neutron:
Fix Released
Bug description:
neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/sql/default_comparator.py:153:
SAWarning: The IN-predicate on "networksegments.network_id" was
invoked with an empty sequence. This results in a contradiction,
which nonetheless can be expensive to evaluate. Consider
alternative strategies for improved performance.
This is coming from neutron.db.segments_db.get_networks_segments:
def get_networks_segments(session, network_ids, filter_dynamic=False):
with session.begin(subtransactions=True):
query = (session.query(NetworkSegment).
filter(NetworkSegment.network_id.in_(network_ids)).
order_by(NetworkSegment.segment_index))
if filter_dynamic is not None:
query = query.filter_by(is_dynamic=filter_dynamic)
records = query.all()
result = {net_id: [] for net_id in network_ids}
for record in records:
result[record.network_id].append(_make_segment_dict(record))
return result
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1586816/+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 1587125] [NEW] Keysone always tries to use domain token regardless of OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT setting
Public bug reported: There is a bug during initialization of keystoneclient (openstack_dashboard/api/keystone.py) where is_multi_domain_enabled is not called to check wheter domain token should be retrieved - only value of function object itself is checked, always resulting in True. ** Affects: horizon Importance: Undecided Assignee: Aleš Křivák (aleskrivak) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Aleš Křivák (aleskrivak) -- 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/1587125 Title: Keysone always tries to use domain token regardless of OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT setting Status in OpenStack Dashboard (Horizon): In Progress Bug description: There is a bug during initialization of keystoneclient (openstack_dashboard/api/keystone.py) where is_multi_domain_enabled is not called to check wheter domain token should be retrieved - only value of function object itself is checked, always resulting in True. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1587125/+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 1575909] Re: VPN shared PSK shown in plaintext
Based on above comment, I removed the OSSA task. ** Changed in: ossa Status: Incomplete => Won't Fix -- 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/1575909 Title: VPN shared PSK shown in plaintext Status in OpenStack Dashboard (Horizon): New Status in OpenStack Security Advisory: Won't Fix Bug description: In the neutron VPN details and form, https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/vpn/templates/vpn/_ipsecsiteconnection_details.html#L43 and https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/vpn/forms.py#L249 don't offer the option of hiding the string. Typically sensitive information like passwords is hidden by default, requiring the user to explicitly choose to make it visible by clicking an icon (like the eye icon). Filing this as a security bug out of an overabundance of caution; while it is related to security it doesn't describe a vulnerability that can be exploited by means other than shoulder surfing. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1575909/+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 1587108] [NEW] Booting an instance from snapshot (which is an instance booted from Cinder volume) fails with: "Volume is smaller than the minimum size specified in image metadata
Public bug reported:
Description
===
Booting an instance from snapshot (which is an instance booted from
Cinder volume) fails with:
ERROR (BadRequest): Volume is smaller than the minimum size specified in
image metadata. Volume size is 1073741824 bytes, minimum size is
3221225472 bytes. (HTTP 400) (Request-ID:
req-547c0339-0576-418f-a5a1-72d9ff114401)
[Source: Originally reported by cshas...@redhat.com as a downstream bug
report.]
I reproduced this issue with upstream Nova on a single-node DevStack.
Details below:
Steps to reproduce
==
(1) Create a new Nova flavor (`nova flavor-create
`):
$ nova flavor-create m1.test 6 256 3 1
(2) Create a Cinder volume (the UUID here is of
cirros-0.3.4-x86_64-disk):
$ cinder create --display-name cirr-vol1 \
--image-id 577d309a-b9e8-48fa-b461-28b14e002b4d 1
(3) Boot an instance from the created volume the UUID below is of
the the Cinder volume created above:
$ nova boot --boot-volume 360f97a0-6588-46ae-b25a-e5687cc2c0e0 \
--flavor 6 instance-boot-from-vol
(4) Create a snapshot of the instance we just booted:
$ nova image-create --poll instance-boot-from-vol \
snap-of-instance-boot-from-vol
(5) Enumerate Glance images to get the UUID of the snapshot created
above:
$ glance image-list | grep snap-of-instance-boot-from-vol \
| awk '{print$2}'
a8b8b3b1-1312-4ece-96b0-2216e4e2d075
(6) Boot an instance using the above snapshot UUID as the image:
$ nova boot --flavor 6 --image a8b8b3b1-1312-4ece-96b0-2216e4e2d075
instance-from-snap
Actual Results
==
$ nova boot --flavor 6 --image a8b8b3b1-1312-4ece-96b0-2216e4e2d075
instance-from-snap
ERROR (BadRequest): Volume is smaller than the minimum size specified in
image metadata. Volume size is 1073741824 bytes, minimum size is
3221225472 bytes. (HTTP 400) (Request-ID:
req-547c0339-0576-418f-a5a1-72d9ff114401)
Expected Results
Booting an instance from snapshot of a Cinder volume should succeed
Environment
===
When I reproduced this issue with upstream Nova on DevStack, I was on
these commits:
cinder
1eef3c7 (Merge "NetApp: Add iterator handling to client library", 2016-05-26)
devstack
327f8d1 (Merge "Fix typo in local variable name in time_stop", 2016-05-27)
devstack-tar-installer-plugin
d2d9575 (Added .gitreview, 2016-04-21)
glance
24fae90 (Merge "Normalize the options use singele quotes", 2016-05-24)
keystone
0b65a96 (Merge "Add identity providers integration tests", 2016-05-26)
neutron
d320df5 (Merge "Don't load DNS integration in l3_router_plugin", 2016-05-26)
nova
784f88b (Merge "Updated from global requirements", 2016-05-27)
requirements
2d2d21d (Merge "Raise mock requirement to 2.0", 2016-05-26)
** 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/1587108
Title:
Booting an instance from snapshot (which is an instance booted from
Cinder volume) fails with: "Volume is smaller than the minimum size
specified in image metadata."
Status in OpenStack Compute (nova):
New
Bug description:
Description
===
Booting an instance from snapshot (which is an instance booted from
Cinder volume) fails with:
ERROR (BadRequest): Volume is smaller than the minimum size specified in
image metadata. Volume size is 1073741824 bytes, minimum size is
3221225472 bytes. (HTTP 400) (Request-ID:
req-547c0339-0576-418f-a5a1-72d9ff114401)
[Source: Originally reported by cshas...@redhat.com as a downstream
bug report.]
I reproduced this issue with upstream Nova on a single-node DevStack.
Details below:
Steps to reproduce
==
(1) Create a new Nova flavor (`nova flavor-create
`):
$ nova flavor-create m1.test 6 256 3 1
(2) Create a Cinder volume (the UUID here is of
cirros-0.3.4-x86_64-disk):
$ cinder create --display-name cirr-vol1 \
--image-id 577d309a-b9e8-48fa-b461-28b14e002b4d 1
(3) Boot an instance from the created volume the UUID below is of
the the Cinder volume created above:
$ nova boot --boot-volume 360f97a0-6588-46ae-b25a-e5687cc2c0e0 \
--flavor 6 instance-boot-from-vol
(4) Create a snapshot of the instance we just booted:
$ nova image-create --poll instance-boot-from-vol \
snap-of-instance-boot-from-vol
(5) Enumerate Glance images to get the UUID of the snapshot created
above:
$ glance image-list | grep snap-of-instance-boot-from-vol \
| awk '{print$2}'
a8b8b3b1-1312-4ece-96b0-2216e4e2d075
(6)
[Yahoo-eng-team] [Bug 1585983] Re: horizon issue with connection to keystone
** Also affects: horizon
Importance: Undecided
Status: New
** 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 Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1585983
Title:
horizon issue with connection to keystone
Status in devstack:
New
Status in OpenStack Dashboard (Horizon):
New
Status in OpenStack Identity (keystone):
New
Bug description:
Hello.
I have fresh installation by devstack.
When I try to access the Users or Projects panels I get an error:
Error: Unable to retrieve project list.
I've in local_settings.py:
OPENSTACK_API_VERSIONS={"identity":3}
OPENSTACK_KEYSTONE_URL="http://192.168.100.56/identity/v3";
I tried to change:
OPENSTACK_API_VERSIONS={"identity":2}
OPENSTACK_KEYSTONE_URL="http://192.168.100.56/identity/v2";
or:
OPENSTACK_API_VERSIONS={"identity":3}
OPENSTACK_KEYSTONE_URL = "http://192.168.100.56:35357/v3";
but all time getting same error in horizon.log:
2016-05-26 10:10:10.271844 DEBUG:keystoneauth.session:REQ: curl -g -i -X GET
http://192.168.100.56/identity/users/12d3903866c04c03867014b46405549b/projects
-H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}3a82a8e5488a184982dda25814ae171bb25c4382"
2016-05-26 10:10:10.275675 DEBUG:keystoneauth.session:RESP: [404] Date: Thu,
26 May 2016 10:10:10 GMT Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips
mod_wsgi/3.4 Python/2.7.5 Vary: X-Auth-Token Content-Length: 93 Keep-Alive:
timeout=5, max=100 Connection: Keep-Alive Content-Type: application/json
2016-05-26 10:10:10.275699 RESP BODY: {"error": {"message": "The resource
could not be found.", "code": 404, "title": "Not Found"}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1585983/+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 1586976] Re: UTs and functional tests broken related to msgid translations
Okay, I think I found the root case.
https://review.openstack.org/#/c/294751/ was introduced on 2016-04-12
but only tagged for 1.7.0 on http://git.openstack.org/cgit/openstack
/python-cinderclient/commit/?id=0cdcfb5988f57da80551b1a11fcd3d96d0baf1d8
(which was reverted quickly) and then only applied again when 1.7.1 was
pushed to upper-constraints.txt (
https://github.com/openstack/requirements/commit/c682e3b8355b3e4648e3ec6158f6b4a2758be71a
#diff-0bdd949ed8a7fdd4f95240bd951779c8 )
It seems the new cinderclient globally modifies the translation catalog
lookup fonctions (LW, LI, etc.) *globally* :
https://review.openstack.org/#/c/294751/2/cinderclient/_i18n.py
** Also affects: python-cinderclient
Importance: Undecided
Status: New
** Changed in: python-cinderclient
Status: New => Confirmed
** Summary changed:
- UTs and functional tests broken related to msgid translations
+ UTs and functional tests broken due to cinderclient modifying i18n global vars
--
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/1586976
Title:
Nova UTs and functional tests broken due to cinderclient modifying
i18n global vars
Status in OpenStack Compute (nova):
Confirmed
Status in python-cinderclient:
Confirmed
Bug description:
Python unittests and functional tests are trampled by our Translation
system, and in particular the gettext module.
For example :
2016-05-30 05:45:25.217 |
nova.tests.unit.virt.libvirt.test_driver.LibvirtConnTestCase.test_create_images_and_backing_images_exist
2016-05-30 05:45:25.218 |
2016-05-30 05:45:25.218 |
2016-05-30 05:45:25.218 | Captured traceback:
2016-05-30 05:45:25.218 | ~~~
2016-05-30 05:45:25.218 | Traceback (most recent call last):
2016-05-30 05:45:25.218 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py",
line 1305, in patched
2016-05-30 05:45:25.218 | return func(*args, **keywargs)
2016-05-30 05:45:25.218 | File
"nova/tests/unit/virt/libvirt/test_driver.py", line 8337, in
test_create_images_and_backing_images_exist
2016-05-30 05:45:25.218 | conn =
libvirt_driver.LibvirtDriver(fake.FakeVirtAPI(), False)
2016-05-30 05:45:25.218 | File "nova/virt/libvirt/driver.py", line 325,
in __init__
2016-05-30 05:45:25.218 | host=self._host)
2016-05-30 05:45:25.219 | File "nova/virt/firewall.py", line 37, in
load_driver
2016-05-30 05:45:25.219 | return fw_class(*args, **kwargs)
2016-05-30 05:45:25.219 | File "nova/virt/libvirt/firewall.py", line
335, in __init__
2016-05-30 05:45:25.219 | self.nwfilter =
NWFilterFirewall(kwargs['host'])
2016-05-30 05:45:25.219 | File "nova/virt/libvirt/firewall.py", line
58, in __init__
2016-05-30 05:45:25.219 | LOG.warning(_LW("Libvirt module could not
be loaded. "
2016-05-30 05:45:25.219 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/oslo_i18n/_factory.py",
line 83, in f
2016-05-30 05:45:25.219 | return _message.Message(msg, domain=domain)
2016-05-30 05:45:25.219 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/oslo_i18n/_message.py",
line 60, in __new__
2016-05-30 05:45:25.219 | msgtext = Message._translate_msgid(msgid,
domain)
2016-05-30 05:45:25.219 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/oslo_i18n/_message.py",
line 117, in _translate_msgid
2016-05-30 05:45:25.219 | fallback=True)
2016-05-30 05:45:25.220 | File "/usr/lib/python2.7/gettext.py", line
492, in translation
2016-05-30 05:45:25.220 | with open(mofile, 'rb') as fp:
2016-05-30 05:45:25.220 | IOError: [Errno 2] No such file or directory:
'/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/share/locale/en_US.ISO8859-1/LC_MESSAGES/nova-log-warning.mo'
2016-05-30 05:45:25.220 |
Or :
2016-05-30 05:45:25.210 |
nova.tests.unit.virt.libvirt.test_driver.LibvirtDriverTestCase.test_delete_instance_files_resize
2016-05-30 05:45:25.210 |
2016-05-30 05:45:25.210 |
2016-05-30 05:45:25.210 | Captured pythonlogging:
2016-05-30 05:45:25.210 | ~~~
2016-05-30 05:45:25.210 | 2016-05-30 05:42:04,467 WARNING
[nova.virt.libvirt.firewall] Libvirt module could not be loaded.
NWFilterFirewall will not work correctly.
2016-05-30 05:45:25.210 | 2016-05-30 05:42:04,469 INFO
[os_brick.initiator.connector] Init DISCO connector
2016-05-30 05:45:25.210 |
2016-05-30 05:45:25.210 |
[Yahoo-eng-team] [Bug 1586066] Re: handle oslo.log verbose deprecation
Reviewed: https://review.openstack.org/321481 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=22da3db98b8699f48d93892007e6a93340a3913c Submitter: Jenkins Branch:master commit 22da3db98b8699f48d93892007e6a93340a3913c Author: Ihar Hrachyshka Date: Thu May 26 13:16:30 2016 +0200 oslo: remove usage of oslo.log verbose option The option was deprecated a long time ago, and will be removed in one of the next library releases, which will render neutron broken if we keep using the option. More details: http://lists.openstack.org/pipermail/openstack-dev/2016-May/095166.html Closes-Bug: #1586066 Change-Id: I884b4cc3ed04e4b5489e265c14e04eb1bc27 ** 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/1586066 Title: handle oslo.log verbose deprecation Status in neutron: Fix Released Status in OpenStack DBaaS (Trove): In Progress Bug description: In https://review.openstack.org/#/c/314573/ the verbose option was deleted. Time for projects to do the same. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1586066/+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 1586757] Re: Neutron: show_port fails when QoS service plugin is enabled
This doesn't happen in the stantard ml2 plugin. It could be an
implementation detail in the nsx plugin, from a change of behaviour in
the internal apis may be (sorry for breaking you in that unexpected way
:/ )
** 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/1586757
Title:
Neutron: show_port fails when QoS service plugin is enabled
Status in neutron:
Invalid
Status in tempest:
In Progress
Bug description:
ft29.11:
tempest.api.network.test_ports.PortsTestJSON.test_show_port[id-c9a685bd-e83f-499c-939f-9f7863ca259f,smoke]_StringException:
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2016-05-29 09:44:21,198 23021 INFO [tempest.lib.common.rest_client]
Request (PortsTestJSON:test_show_port): 200 GET
http://10.161.224.53:9696/v2.0/ports/fdf8fc22-3e7e-4429-a820-1d0516395266 0.143s
2016-05-29 09:44:21,199 23021 DEBUG[tempest.lib.common.rest_client]
Request - Headers: {'Content-Type': 'application/json', 'Accept':
'application/json', 'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '200', 'content-length': '535',
'content-location':
'http://10.161.224.53:9696/v2.0/ports/fdf8fc22-3e7e-4429-a820-1d0516395266',
'date': 'Sun, 29 May 2016 09:44:21 GMT', 'content-type': 'application/json',
'connection': 'close', 'x-openstack-request-id':
'req-f7ec521d-11d3-41dd-9502-fad4c1598f68'}
Body: {"port": {"status": "ACTIVE", "created_at":
"2016-05-29T09:43:40", "description": "", "allowed_address_pairs": [],
"admin_state_up": true, "network_id": "3d6cda6c-a2bd-4f99-bea7-b1370a987d6e",
"tenant_id": "83c870fba45c4333b8049272df23e670", "extra_dhcp_opts": [],
"updated_at": "2016-05-29T09:43:40", "name": "", "device_owner": "",
"mac_address": "fa:16:3e:ac:0c:82", "port_security_enabled": true,
"binding:vnic_type": "normal", "fixed_ips": [], "id":
"fdf8fc22-3e7e-4429-a820-1d0516395266", "security_groups": [], "device_id": ""}}
}}}
Traceback (most recent call last):
File "/opt/stack/tempest/tempest/api/network/test_ports.py", line 142, in
test_show_port
'updated_at']))
File
"/opt/stack/tempest/.venv/local/lib/python2.7/site-packages/testtools/testcase.py",
line 498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: Only in actual:
{'qos_policy_id': None}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1586757/+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 1587021] [NEW] Log file full of info messages that segments are not supported
Public bug reported: The following info messages are in the log file: 2016-05-30 11:27:46.320 INFO neutron.services.segments.db [req- be57cc26-a3ae-4370-aed9-cdb4ed6ccabb None None] Core plug-in does not implement 'check_segment_for_agent'. It is not possible to build a hosts segments mapping In the even that a core plugin does not support this we should not be posting this for each update sent by the agent ** Affects: neutron Importance: Undecided Assignee: Gary Kotton (garyk) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1587021 Title: Log file full of info messages that segments are not supported Status in neutron: In Progress Bug description: The following info messages are in the log file: 2016-05-30 11:27:46.320 INFO neutron.services.segments.db [req- be57cc26-a3ae-4370-aed9-cdb4ed6ccabb None None] Core plug-in does not implement 'check_segment_for_agent'. It is not possible to build a hosts segments mapping In the even that a core plugin does not support this we should not be posting this for each update sent by the agent To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1587021/+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 1587014] [NEW] Serial ports lost after hard-reboot
Public bug reported: After I executed "nova reboot --hard ", We could not access to the vm's serial-console. This is due because during hare-reboot process in driver destroy the guest without to undefine the domain. So when we recreate the guest and so call 'get_guest_xml' serial ports are still defined in the XML so the process does not try to re-acquire them on host. ** Affects: nova Importance: Undecided Assignee: sahid (sahid-ferdjaoui) Status: New ** Tags: console libvirt ** Changed in: nova Assignee: (unassigned) => sahid (sahid-ferdjaoui) -- 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/1587014 Title: Serial ports lost after hard-reboot Status in OpenStack Compute (nova): New Bug description: After I executed "nova reboot --hard ", We could not access to the vm's serial-console. This is due because during hare-reboot process in driver destroy the guest without to undefine the domain. So when we recreate the guest and so call 'get_guest_xml' serial ports are still defined in the XML so the process does not try to re-acquire them on host. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1587014/+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 1491823] Re: Glance return 405 error when we try update element in bloblist
** Changed in: glance
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1491823
Title:
Glance return 405 error when we try update element in bloblist
Status in Glance:
Won't Fix
Bug description:
ENVIRONMENT: devstack, Glance (master, 03.09.2015)
STEPS TO REPRODUCE:
We have artifact:
{"description": null, "published_at": null, "tags": [], "created_at":
"2015-09-02T09:29:27.00", "type_name": "MyArtifact", "updated_at":
"2015-09-02T09:29:27.00", "visibility": "private", "id":
"917ec8d2-44fb-4445-abb7-e28b65f7f07b", "type_version": "2.0", "state":
"creating", "version": "12.0.0", "prop1": null, "prop2": null, "owner":
"13db150f0268414ca7f2d81ea60a8205", "image_file": null, "deleted_at": null,
"screenshots": [{"checksum": "db78f300f6509d4fc131cb4a23fd9356",
"download_link":
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/0/download",
"size": 14}, {"checksum": "6807f2db24acbf20a715b41665c99a18", "download_link":
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/1/download",
"size": 14}, {"checksum": "db78f300f6509d4fc131cb4a23fd9356", "download_link":
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/2/download",
"size": 14}], "int_list": null, "name": "artifact1"}
Send request:
curl -H "X-Auth-Token: 3309284e1ff543e89ac57f9b0a643ad3" -H
"Content-Type:octet-stream" -X PUT -d '{"data": "new_data"}'
http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/0
-i
EXPECTED RESULT:
status code 200 and update the element in screenshots
ACTUAL RESULT:
HTTP/1.1 405 Method Not Allowed
Content-Length: 187
Content-Type: text/html; charset=UTF-8
X-Openstack-Request-Id: req-ad97df1c-0fb6-4244-9ce6-6fada6bf38a7
Date: Thu, 03 Sep 2015 12:30:45 GMT
405 Method Not Allowed
405 Method Not Allowed
The method PUT is not allowed for this resource.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1491823/+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 1489941] Re: v2 client sorts on name in wrong direction
Marked as Won't fix. See reason in comment #10. Also python-glanceclient is going to be deprecated in favor of openstackclient. So the bug marked as won't fix for glanceclient too. ** Changed in: glance Status: In Progress => Won't Fix ** Changed in: python-glanceclient Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1489941 Title: v2 client sorts on name in wrong direction Status in Glance: Won't Fix Status in python-glanceclient: Won't Fix Bug description: The v1 client sorts images by name alphabetically: $ glance --os-image-api-version 1 image-list --sort-key name +--+-+-+--+---++ | ID | Name| Disk Format | Container Format | Size | Status | +--+-+-+--+---++ | 7d1923d7-68e8-4a8e-b23e-a7c77f8117fd | | raw | bare | 1034 | active | | 5e9dc64e-7c05-431c-b81f-ae6a212353e8 | | qcow2 | bare | | queued | | 6802e222-6eac-45c6-8c9f-0d62aed26406 | | qcow2 | bare | 145 | active | | 7af0d66b-5b48-48a6-a6d9-c2cd3eafa83e | | | | | queued | | dde89c3c-c8af-46a4-87b0-f39ed6c61c42 | | raw | bare | 2 | active | | 262ac5aa-e580-4bec-a3b2-580924425fd5 | | raw | bare | 2 | active | | 4cc5b305-43a7-495e-8e67-16d95629621e | | raw | bare | 2 | active | The v2 client sorts in reverse alphabetical: $ glance --os-image-api-version 2 image-list --sort-key name +--+-+ | ID | Name| +--+-+ | b16dbfb2-f435-40a8-aa08-2aadaee99cd1 | trusty2 | | cc658de9-039a-46d7-829a-dc1f08cac153 | test1 | | 2fa0f342-623e-423f-8faa-70f000b3e4cc | test1 | | c95a4ee7-28d0-4fd5-86c6-fe9816fcef23 | test1 | | d75354ed-ef63-4f41-9d53-a0d67394d1a3 | test1 | | ecc24d0d-140c-484d-ae42-427e60be9270 | test1 | | f3b996a9-469c-4882-864b-fef0cd24429d | test1 | adding the sort dir gives the same result as v1: $ glance --os-image-api-version 2 image-list --sort-key name --sort-dir asc +--+-+ | ID | Name| +--+-+ | 7d1923d7-68e8-4a8e-b23e-a7c77f8117fd | | | 5e9dc64e-7c05-431c-b81f-ae6a212353e8 | | | 6802e222-6eac-45c6-8c9f-0d62aed26406 | | | 7af0d66b-5b48-48a6-a6d9-c2cd3eafa83e | | | dde89c3c-c8af-46a4-87b0-f39ed6c61c42 | | | 262ac5aa-e580-4bec-a3b2-580924425fd5 | | | 4cc5b305-43a7-495e-8e67-16d95629621e | | To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1489941/+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 1493833] Re: Glance returns 500 error when trying to replace non-exising blob item in artifact blob-list
** Changed in: glance
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1493833
Title:
Glance returns 500 error when trying to replace non-exising blob item
in artifact blob-list
Status in Glance:
Invalid
Bug description:
Steps to reproduce:
1. Create an artifact (type=MyArtifact)
2. Update artifact blob list with some value:
curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H
"Content-Type:application/octet-stream" -X POST -d '{"data":
"someupdates_datawithtretrtrt"}'
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/6d16c3e9-26d6-4abd-8ad6-e70e66e31aab/screenshots
-i
3. Try to replace non-existing blob item in blob list
curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H
"Content-Type:application/octet-stream" -X PUT -d '{"data":
"someupdates_datawithtretrtrt"}'
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/6d16c3e9-26d6-4abd-8ad6-e70e66e31aab/screenshots/1
-i
AR: Internal Server Error
ER: BadRequest Error
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1493833/+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 1491815] Re: Glance return 404 error when we try delete element in bloblist/blob
** Changed in: glance
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1491815
Title:
Glance return 404 error when we try delete element in bloblist/blob
Status in Glance:
Invalid
Bug description:
ENVIRONMENT: devstack, Glance (master, 03.09.2015)
STEPS TO REPRODUCE:
We have artifact:
{"description": null, "published_at": null, "tags": [], "created_at":
"2015-09-02T09:29:27.00", "type_name": "MyArtifact", "updated_at":
"2015-09-02T09:29:27.00", "visibility": "private", "id":
"917ec8d2-44fb-4445-abb7-e28b65f7f07b", "type_version": "2.0", "state":
"creating", "version": "12.0.0", "prop1": null, "prop2": null, "owner":
"13db150f0268414ca7f2d81ea60a8205", "image_file": null, "deleted_at": null,
"screenshots": [{"checksum": "db78f300f6509d4fc131cb4a23fd9356",
"download_link":
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/0/download",
"size": 14}, {"checksum": "6807f2db24acbf20a715b41665c99a18", "download_link":
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/1/download",
"size": 14}, {"checksum": "db78f300f6509d4fc131cb4a23fd9356", "download_link":
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/2/download",
"size": 14}], "int_list": null, "name": "artifact1"}
Send request:
curl -H "X-Auth-Token: 3309284e1ff543e89ac57f9b0a643ad3" -X DELETE
http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/917ec8d2-44fb-444528b65f7f07b/screenshots/0
-i
EXPECTED RESULT:
status code 204 and delete the item in screenshots
ACTUAL RESULT:
HTTP/1.1 404 Not Found
Content-Length: 154
Content-Type: text/html; charset=UTF-8
X-Openstack-Request-Id: req-adc1f847-fca2-4419-bda0-058eebb9f8da
Date: Thu, 03 Sep 2015 12:21:24 GMT
404 Not Found
404 Not Found
The resource could not be found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1491815/+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 1493826] Re: Glance doesn't replace blob property correctly in artifacts
** Changed in: glance
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1493826
Title:
Glance doesn't replace blob property correctly in artifacts
Status in Glance:
Invalid
Bug description:
Version: glance liberty master (latest 04.09.15)
Steps to reproduce:
1. Create an artifact(type=MyArtifact) with blob property (image_file)
2. Update blob property image_file with some value:
curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H
"Content-Type:application/octet-stream" -X POST -d '{"data":
"someupdates_datawithtretrtrt"}'
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
-i
3. Request blob property replace:
curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H
"Content-Type:application/octet-stream" -X PUT -d '{"data":
"someupdates_datawithtretrtrt"}'
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
-i
AR: 405 Method not allowed
ER: 200 OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1493826/+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 1586776] Re: RPC Unit tests: have future warnings about UUIDS
Reviewed: https://review.openstack.org/322503 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1328000f9b9415c4fc6c0a91e68b7756d93bca5c Submitter: Jenkins Branch:master commit 1328000f9b9415c4fc6c0a91e68b7756d93bca5c Author: Gary Kotton Date: Sun May 29 06:47:09 2016 -0700 RPC unit tests: remove UUID future warnings Mkae sure that objects make use of a UUID and not a fake one. Change-Id: I6c4c51e8b5d8d5a347e9ccbef40ba04286850a41 Closes-bug: #1586776 ** 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/1586776 Title: RPC Unit tests: have future warnings about UUIDS Status in neutron: Fix Released Bug description: /home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_versionedobjects/fields.py:329: FutureWarning: uuid is an invalid UUID. Using UUIDFields with invalid UUIDs is no longer supported, and will be removed in a future release. Please update your code to input valid UUIDs or accept ValueErrors for invalid UUIDs. See http://docs.openstack.org/developer/oslo.versionedobjects/api/fields.html#oslo_versionedobjects.fields.UUIDField for further details 2016-05-28 23:27:53.481 | "for further details" % value, FutureWarning) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1586776/+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 1586986] [NEW] vpnaas: Copy strongswan.d needs root rights
Public bug reported:
Using shutil.copytree() doesn't work if "/etc/strongwan.d/ is owned by root but
the neutron-vpn-agent is running on a different user (i.e. "neutron").
The error message is:
2016-05-30 08:21:09.974 25950 ERROR oslo_messaging.rpc.dispatcher
[req-a50cffcd-b59e-4aa3-a38c-80276e7855f2 bb02d9c6a9d142bdb9beb6dea7b71271
49748f1f979846ec9b05f100bffe30a8 - - -] Exception during message handling:
[('/etc/strongswan.d/starter.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/starter.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/starter.conf'"),
('/etc/strongswan.d/tools.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/tools.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/tools.conf'"),
('/etc/strongswan.d/charon.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon.conf'"),
('/etc/strongswan.d/charon-logging.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon-logging.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon-lo
gging.conf'"), ('/etc/strongswan.d/pool.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/pool.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/pool.conf'"),
('/etc/strongswan.d/imcv.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/imcv.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/imcv.conf'"),
('/etc/strongswan.d/tnc.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/tnc.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/tnc.conf'"),
('/etc/strongswan.d/charon/x509.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/x509.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/x509.conf'"),
('/etc/strongswan.d/charon/radattr.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/radattr.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/radattr.conf'"),
('/etc/strongswan.d/charon/pkcs8.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/pkcs8.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/pkcs8.conf'"),
('/etc/strongswan.d/charon/fips-prf.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/fips-prf.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/fips-prf.conf'"),
('/etc/strongswan.d/charon/smp.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/smp.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/smp.conf'"),
('/etc/strongswan.d/charon/eap-identity.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/eap-identity.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/eap-identity.conf'"),
('/etc/strongswan.d/charon/tnc-tnccs.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charo
n/tnc-tnccs.conf', "[Errno 13] Permission denied:
'/etc/strongswan.d/charon/tnc-tnccs.conf'"),
('/etc/strongswan.d/charon/ldap.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/ldap.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/ldap.conf'"),
('/etc/strongswan.d/charon/dnskey.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/dnskey.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/dnskey.conf'"),
('/etc/strongswan.d/charon/sha2.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/sha2.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/sha2.conf'"),
('/etc/strongswan.d/charon/tnc-pdp.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/tnc-pdp.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/tnc-pdp.conf'"),
('/etc/strongswan.d/charon/sshkey.conf', u'/var/lib/neu
tron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/sshkey.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/sshkey.conf'"),
('/etc/strongswan.d/charon/pkcs7.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/pkcs7.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/pkcs7.conf'"),
('/etc/strongswan.d/charon/eap-dynamic.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/eap-dynamic.conf',
"[Errno 13] Permission denied: '/etc/strongswan.d/charon/eap-dynamic.conf'"),
('/etc/strongswan.d/charon/hmac.conf',
u'/var/lib/neutron/ipsec/c987ad68-be1b-468f-ac05-2d3c021248f1/etc/strongswan.d/charon/hmac.conf',
"[E
[Yahoo-eng-team] [Bug 1586979] [NEW] AMQP 2.0 prevents services from starting
Public bug reported:
We are running nova from the stable/mitaka branch (not using packages).
Our build process has flagged this. Previously, when we've built, we've
used the requirements.txt file to pull in dependencies, and one of the
dependencies pulls in AMQP.
Initial investigation leads us to believe that oslo.messaging pulls in
AMQP as a dependency. It looks to be pulling in the latest version
(2.0). Our previous successful builds show AMQP of 1.4.9, which is
fully functional.
2.0 completely breaks, for example, the nova-compute service with the
following trace:
2016-05-30 01:04:58.192 11335 CRITICAL nova
[req-992ce9e3-fab8-47f9-8879-36b42594fae8 - - - - -] AttributeError:
'Connection' object has no attribute '_frame_writer'
2016-05-30 01:04:58.192 11335 ERROR nova Traceback (most recent call last):
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/bin/nova-compute", line 10, in
2016-05-30 01:04:58.192 11335 ERROR nova sys.exit(main())
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/nova/cmd/compute.py",
line 73, in main
2016-05-30 01:04:58.192 11335 ERROR nova
db_allowed=CONF.conductor.use_local)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/nova/service.py",
line 218, in create
2016-05-30 01:04:58.192 11335 ERROR nova db_allowed=db_allowed)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/nova/service.py",
line 101, in init
2016-05-30 01:04:58.192 11335 ERROR nova
self.conductor_api.wait_until_ready(context.get_admin_context())
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/nova/conductor/api.py",
line 157, in wait_until_ready
2016-05-30 01:04:58.192 11335 ERROR nova timeout=timeout)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/nova/baserpc.py",
line 58, in ping
2016-05-30 01:04:58.192 11335 ERROR nova return cctxt.call(context, 'ping',
arg=arg_p)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/rpc/client.py",
line 157, in call
2016-05-30 01:04:58.192 11335 ERROR nova retry=self.retry)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/transport.py",
line 91, in _send
2016-05-30 01:04:58.192 11335 ERROR nova timeout=timeout, retry=retry)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py",
line 466, in send
2016-05-30 01:04:58.192 11335 ERROR nova retry=retry)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py",
line 410, in _send
2016-05-30 01:04:58.192 11335 ERROR nova msg.update({'_reply_q':
self._get_reply_q()})
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py",
line 382, in _get_reply_q
2016-05-30 01:04:58.192 11335 ERROR nova conn =
self._get_connection(rpc_common.PURPOSE_LISTEN)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py",
line 373, in _get_connection
2016-05-30 01:04:58.192 11335 ERROR nova purpose=purpose)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/common.py",
line 396, in init
2016-05-30 01:04:58.192 11335 ERROR nova self.connection =
connection_pool.create(purpose)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/pool.py",
line 110, in create
2016-05-30 01:04:58.192 11335 ERROR nova return
self.connection_cls(self.conf, self.url, purpose)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py",
line 556, in init
2016-05-30 01:04:58.192 11335 ERROR nova self.ensure_connection()
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py",
line 654, in ensure_connection
2016-05-30 01:04:58.192 11335 ERROR nova self.ensure(method=lambda:
self.connection.connection)
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/local/lib/python2.7/site-packages/oslo_messaging/_drivers/impl_rabbit.py",
line 759, in ensure
2016-05-30 01:04:58.192 11335 ERROR nova ret, channel = autoretry_method()
2016-05-30 01:04:58.192 11335 ERROR nova File
"/opt/mhos/openstack/nova/lo
[Yahoo-eng-team] [Bug 1586976] [NEW] oslo.i18n modules breaking nova's UTs and functional tests
Public bug reported:
Python unittests and functional tests are trampled by our Translation
system, and in particular the gettext module.
For example :
2016-05-30 05:45:25.217 |
nova.tests.unit.virt.libvirt.test_driver.LibvirtConnTestCase.test_create_images_and_backing_images_exist
2016-05-30 05:45:25.218 |
2016-05-30 05:45:25.218 |
2016-05-30 05:45:25.218 | Captured traceback:
2016-05-30 05:45:25.218 | ~~~
2016-05-30 05:45:25.218 | Traceback (most recent call last):
2016-05-30 05:45:25.218 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py",
line 1305, in patched
2016-05-30 05:45:25.218 | return func(*args, **keywargs)
2016-05-30 05:45:25.218 | File
"nova/tests/unit/virt/libvirt/test_driver.py", line 8337, in
test_create_images_and_backing_images_exist
2016-05-30 05:45:25.218 | conn =
libvirt_driver.LibvirtDriver(fake.FakeVirtAPI(), False)
2016-05-30 05:45:25.218 | File "nova/virt/libvirt/driver.py", line 325,
in __init__
2016-05-30 05:45:25.218 | host=self._host)
2016-05-30 05:45:25.219 | File "nova/virt/firewall.py", line 37, in
load_driver
2016-05-30 05:45:25.219 | return fw_class(*args, **kwargs)
2016-05-30 05:45:25.219 | File "nova/virt/libvirt/firewall.py", line 335,
in __init__
2016-05-30 05:45:25.219 | self.nwfilter =
NWFilterFirewall(kwargs['host'])
2016-05-30 05:45:25.219 | File "nova/virt/libvirt/firewall.py", line 58,
in __init__
2016-05-30 05:45:25.219 | LOG.warning(_LW("Libvirt module could not be
loaded. "
2016-05-30 05:45:25.219 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/oslo_i18n/_factory.py",
line 83, in f
2016-05-30 05:45:25.219 | return _message.Message(msg, domain=domain)
2016-05-30 05:45:25.219 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/oslo_i18n/_message.py",
line 60, in __new__
2016-05-30 05:45:25.219 | msgtext = Message._translate_msgid(msgid,
domain)
2016-05-30 05:45:25.219 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/oslo_i18n/_message.py",
line 117, in _translate_msgid
2016-05-30 05:45:25.219 | fallback=True)
2016-05-30 05:45:25.220 | File "/usr/lib/python2.7/gettext.py", line 492,
in translation
2016-05-30 05:45:25.220 | with open(mofile, 'rb') as fp:
2016-05-30 05:45:25.220 | IOError: [Errno 2] No such file or directory:
'/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/share/locale/en_US.ISO8859-1/LC_MESSAGES/nova-log-warning.mo'
2016-05-30 05:45:25.220 |
Or :
2016-05-30 05:45:25.210 |
nova.tests.unit.virt.libvirt.test_driver.LibvirtDriverTestCase.test_delete_instance_files_resize
2016-05-30 05:45:25.210 |
2016-05-30 05:45:25.210 |
2016-05-30 05:45:25.210 | Captured pythonlogging:
2016-05-30 05:45:25.210 | ~~~
2016-05-30 05:45:25.210 | 2016-05-30 05:42:04,467 WARNING
[nova.virt.libvirt.firewall] Libvirt module could not be loaded.
NWFilterFirewall will not work correctly.
2016-05-30 05:45:25.210 | 2016-05-30 05:42:04,469 INFO
[os_brick.initiator.connector] Init DISCO connector
2016-05-30 05:45:25.210 |
2016-05-30 05:45:25.210 |
2016-05-30 05:45:25.210 | Captured traceback:
2016-05-30 05:45:25.210 | ~~~
2016-05-30 05:45:25.211 | Traceback (most recent call last):
2016-05-30 05:45:25.211 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py",
line 1305, in patched
2016-05-30 05:45:25.211 | return func(*args, **keywargs)
2016-05-30 05:45:25.211 | File
"nova/tests/unit/virt/libvirt/test_driver.py", line 15409, in
test_delete_instance_files_resize
2016-05-30 05:45:25.211 | result =
self.drvr.delete_instance_files(instance)
2016-05-30 05:45:25.211 | File "nova/virt/libvirt/driver.py", line 7422,
in delete_instance_files
2016-05-30 05:45:25.211 | LOG.info(_LI('Deleting instance files %s'),
target_del,
2016-05-30 05:45:25.211 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/oslo_i18n/_factory.py",
line 83, in f
2016-05-30 05:45:25.211 | return _message.Message(msg, domain=domain)
2016-05-30 05:45:25.211 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-packages/oslo_i18n/_message.py",
line 60, in __new__
2016-05-30 05:45:25.212 | msgtext = Message._translate_msgid(msgid,
domain)
2016-05-30 05:45:25.212 | File
"/home/jenkins/workspace/gate-nova-python27-db/.tox/py27/local/lib/python2.7/site-pac
[Yahoo-eng-team] [Bug 1507826] Re: Error - "Unable to find authentication token in headers" when run "nova image-list on a new install env
** Project changed: openstack-community => glance
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1507826
Title:
Error - "Unable to find authentication token in headers" when run
"nova image-list on a new install env
Status in Glance:
New
Bug description:
I just tried to set up a minimum environment with a control node, a
network node and a compute node by following the document "openstack-
install-guide-kilo.pdf". I went through setting up keystone, glance
and compute. At the end of Adding Compute Node section, it verifies
the install. The commands "nova service-list", "nova endpoints" had
good results.
But "nova image-list" has following error:
$ nova image-list
ERROR (ClientException): The server has either erred or is incapable of
performing the requested operation. (HTTP 500) (Request-ID:
req-2c4cd3c7-da8d-480d-949d-1a54f51ec994)
The error "HTTP 500" is kind of general error from http server.
From glance-registry.log, it has following error msg:
2015-10-19 20:08:14.976 32745 WARNING keystonemiddleware.auth_token [-]
Identity response: {"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Unauthorized"}}
2015-10-19 20:08:14.997 32745 WARNING keystonemiddleware.auth_token [-]
Identity response: {"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Unauthorized"}}
2015-10-19 20:08:14.997 32745 WARNING keystonemiddleware.auth_token [-]
Authorization failed for token
2015-10-19 20:08:14.998 32745 INFO eventlet.wsgi.server [-] 127.0.0.1 - -
[19/Oct/2015 20:08:14] "GET /images/detail?is_public=none&limit=20 HTTP/1.1"
401 187 0.063297
2015-10-19 20:08:15.000 32745 WARNING keystonemiddleware.auth_token [-]
Unable to find authentication token in headers
2015-10-19 20:08:15.001 32745 INFO eventlet.wsgi.server [-] 127.0.0.1 - -
[19/Oct/2015 20:08:15] "GET /images/detail?is_public=none&limit=20 HTTP/1.1"
401 187 0.000781
I searched the forum, I knew there is a post "nova image-list returns
500 error", I tried the steps listed in that post but it didn't fix my
issue. I have double, triple checked the configuration in nova.conf,
glance-api.conf, glance-registry.conf. restarted all nova, glance
services, but the error is still there.
Can anyone tell what I could do to investigate it?
Some other info is as below.
Thanks,
Allen
nova.conf on control node:
# cat /etc/nova/nova.conf
[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
log_dir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
libvirt_use_virtio_for_bridges=True
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
enabled_apis=ec2,osapi_compute,metadata
rpc_backend = rabbit
auth_strategy = keystone
my_ip = 10.6.117.173
vncserver_listen = 10.6.117.173
vncserver_proxyclient_address = 10.6.117.173
[oslo_messaging_rabbit]
rabbit_host=fbdl4
rabbit_userid=openstack
rabbit_password=abc123
[database]
connection = mysql://nova:abc123@fbdl4/nova
[keystone_authtoken]
auth_uri = http://fbdl4:5000
auth_url = http://fbdl4:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = nova
password = abc123
[glance]
host = fbdl4
[oslo_concurrency]
lock_path = /var/lib/nova/tmp
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1507826/+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 1515528] Re: openstack-nova-novncproxy-2014.1.5-1.el6.noarch
** Project changed: openstack-community => nova -- 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/1515528 Title: openstack-nova-novncproxy-2014.1.5-1.el6.noarch Status in OpenStack Compute (nova): New Bug description: #/usr/bin/nova-novncproxy --web /usr/share/novnc/ WARNING: no 'numpy' module, HyBi protocol will be slower Traceback (most recent call last): File "/usr/bin/nova-novncproxy", line 10, in sys.exit(main()) File "/usr/lib/python2.6/site-packages/nova/cmd/novncproxy.py", line 87, in main wrap_cmd=None) File "/usr/lib/python2.6/site-packages/nova/console/websocketproxy.py", line 47, in __init__ ssl_target=None, *args, **kwargs) File "/usr/lib/python2.6/site-packages/websockify/websocketproxy.py", line 231, in __init__ websocket.WebSocketServer.__init__(self, RequestHandlerClass, *args, **kwargs) TypeError: __init__() got an unexpected keyword argument 'no_parent' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1515528/+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 1586757] Re: Neutron: show_port fails when QoS service plugin is enabled
I don't think the refactoring was supposed to change any behaviour. If
it did, it was a bug in the refactoring patch.
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1586757
Title:
Neutron: show_port fails when QoS service plugin is enabled
Status in neutron:
New
Status in tempest:
In Progress
Bug description:
ft29.11:
tempest.api.network.test_ports.PortsTestJSON.test_show_port[id-c9a685bd-e83f-499c-939f-9f7863ca259f,smoke]_StringException:
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2016-05-29 09:44:21,198 23021 INFO [tempest.lib.common.rest_client]
Request (PortsTestJSON:test_show_port): 200 GET
http://10.161.224.53:9696/v2.0/ports/fdf8fc22-3e7e-4429-a820-1d0516395266 0.143s
2016-05-29 09:44:21,199 23021 DEBUG[tempest.lib.common.rest_client]
Request - Headers: {'Content-Type': 'application/json', 'Accept':
'application/json', 'X-Auth-Token': ''}
Body: None
Response - Headers: {'status': '200', 'content-length': '535',
'content-location':
'http://10.161.224.53:9696/v2.0/ports/fdf8fc22-3e7e-4429-a820-1d0516395266',
'date': 'Sun, 29 May 2016 09:44:21 GMT', 'content-type': 'application/json',
'connection': 'close', 'x-openstack-request-id':
'req-f7ec521d-11d3-41dd-9502-fad4c1598f68'}
Body: {"port": {"status": "ACTIVE", "created_at":
"2016-05-29T09:43:40", "description": "", "allowed_address_pairs": [],
"admin_state_up": true, "network_id": "3d6cda6c-a2bd-4f99-bea7-b1370a987d6e",
"tenant_id": "83c870fba45c4333b8049272df23e670", "extra_dhcp_opts": [],
"updated_at": "2016-05-29T09:43:40", "name": "", "device_owner": "",
"mac_address": "fa:16:3e:ac:0c:82", "port_security_enabled": true,
"binding:vnic_type": "normal", "fixed_ips": [], "id":
"fdf8fc22-3e7e-4429-a820-1d0516395266", "security_groups": [], "device_id": ""}}
}}}
Traceback (most recent call last):
File "/opt/stack/tempest/tempest/api/network/test_ports.py", line 142, in
test_show_port
'updated_at']))
File
"/opt/stack/tempest/.venv/local/lib/python2.7/site-packages/testtools/testcase.py",
line 498, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: Only in actual:
{'qos_policy_id': None}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1586757/+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 1507826] [NEW] Error - "Unable to find authentication token in headers" when run "nova image-list on a new install env
You have been subscribed to a public bug:
I just tried to set up a minimum environment with a control node, a
network node and a compute node by following the document "openstack-
install-guide-kilo.pdf". I went through setting up keystone, glance and
compute. At the end of Adding Compute Node section, it verifies the
install. The commands "nova service-list", "nova endpoints" had good
results.
But "nova image-list" has following error:
$ nova image-list
ERROR (ClientException): The server has either erred or is incapable of
performing the requested operation. (HTTP 500) (Request-ID:
req-2c4cd3c7-da8d-480d-949d-1a54f51ec994)
The error "HTTP 500" is kind of general error from http server.
>From glance-registry.log, it has following error msg:
2015-10-19 20:08:14.976 32745 WARNING keystonemiddleware.auth_token [-]
Identity response: {"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Unauthorized"}}
2015-10-19 20:08:14.997 32745 WARNING keystonemiddleware.auth_token [-]
Identity response: {"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Unauthorized"}}
2015-10-19 20:08:14.997 32745 WARNING keystonemiddleware.auth_token [-]
Authorization failed for token
2015-10-19 20:08:14.998 32745 INFO eventlet.wsgi.server [-] 127.0.0.1 - -
[19/Oct/2015 20:08:14] "GET /images/detail?is_public=none&limit=20 HTTP/1.1"
401 187 0.063297
2015-10-19 20:08:15.000 32745 WARNING keystonemiddleware.auth_token [-] Unable
to find authentication token in headers
2015-10-19 20:08:15.001 32745 INFO eventlet.wsgi.server [-] 127.0.0.1 - -
[19/Oct/2015 20:08:15] "GET /images/detail?is_public=none&limit=20 HTTP/1.1"
401 187 0.000781
I searched the forum, I knew there is a post "nova image-list returns
500 error", I tried the steps listed in that post but it didn't fix my
issue. I have double, triple checked the configuration in nova.conf,
glance-api.conf, glance-registry.conf. restarted all nova, glance
services, but the error is still there.
Can anyone tell what I could do to investigate it?
Some other info is as below.
Thanks,
Allen
nova.conf on control node:
# cat /etc/nova/nova.conf
[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
log_dir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
libvirt_use_virtio_for_bridges=True
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
enabled_apis=ec2,osapi_compute,metadata
rpc_backend = rabbit
auth_strategy = keystone
my_ip = 10.6.117.173
vncserver_listen = 10.6.117.173
vncserver_proxyclient_address = 10.6.117.173
[oslo_messaging_rabbit]
rabbit_host=fbdl4
rabbit_userid=openstack
rabbit_password=abc123
[database]
connection = mysql://nova:abc123@fbdl4/nova
[keystone_authtoken]
auth_uri = http://fbdl4:5000
auth_url = http://fbdl4:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = nova
password = abc123
[glance]
host = fbdl4
[oslo_concurrency]
lock_path = /var/lib/nova/tmp
** Affects: glance
Importance: Undecided
Status: New
** Tags: image-list
--
Error - "Unable to find authentication token in headers" when run "nova
image-list on a new install env
https://bugs.launchpad.net/bugs/1507826
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
--
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 1515528] [NEW] openstack-nova-novncproxy-2014.1.5-1.el6.noarch
You have been subscribed to a public bug: #/usr/bin/nova-novncproxy --web /usr/share/novnc/ WARNING: no 'numpy' module, HyBi protocol will be slower Traceback (most recent call last): File "/usr/bin/nova-novncproxy", line 10, in sys.exit(main()) File "/usr/lib/python2.6/site-packages/nova/cmd/novncproxy.py", line 87, in main wrap_cmd=None) File "/usr/lib/python2.6/site-packages/nova/console/websocketproxy.py", line 47, in __init__ ssl_target=None, *args, **kwargs) File "/usr/lib/python2.6/site-packages/websockify/websocketproxy.py", line 231, in __init__ websocket.WebSocketServer.__init__(self, RequestHandlerClass, *args, **kwargs) TypeError: __init__() got an unexpected keyword argument 'no_parent' ** Affects: nova Importance: Undecided Status: New -- openstack-nova-novncproxy-2014.1.5-1.el6.noarch https://bugs.launchpad.net/bugs/1515528 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). -- 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 1586950] [NEW] ImportError: No module named novadocker.virt.docker.driver
Public bug reported: /usr/local/bin/nova-compute --config-file /etc/nova /nova.conf & echo $! >/opt/stack/status/stack/n-cpu.pid; fg || echo "n-cpu faile d to start" | tee "/opt/stack/status/stack/n-cpu.failure" [1] 61162 /usr/local/bin/nova-compute --config-file /etc/nova/nova.conf 2016-05-30 00:12:07.120 ^[[01;33mWARNING oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m] ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.^[[00m 2016-05-30 00:12:07.305 ^[[00;36mINFO nova.virt.driver [^[[00;36m-^[[00;36m] ^[[01;35m^[[00;36mLoading compute driver 'novadocker.virt.docker.driver.DockerDriver'^[[00m 2016-05-30 00:12:07.306 ^[[01;31mERROR nova.virt.driver [^[[00;36m-^[[01;31m] ^[[01;35m^[[01;31mUnable to load the virtualization driver^[[00m ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00mTraceback (most recent call last): ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m File "/opt/stack/nova/nova/virt/driver.py", line 1624, in load_compute_driver ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m virtapi) ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 44, in import_object ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m return import_class(import_str)(*args, **kwargs) ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 30, in import_class ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m __import__(mod_str) ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00mImportError: No module named novadocker.virt.docker.driver ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m n-cpu failed to start ** Affects: nova Importance: Undecided Assignee: caowei (caowei-e) Status: In Progress -- 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/1586950 Title: ImportError: No module named novadocker.virt.docker.driver Status in OpenStack Compute (nova): In Progress Bug description: /usr/local/bin/nova-compute --config-file /etc/nova /nova.conf & echo $! >/opt/stack/status/stack/n-cpu.pid; fg || echo "n-cpu faile d to start" | tee "/opt/stack/status/stack/n-cpu.failure" [1] 61162 /usr/local/bin/nova-compute --config-file /etc/nova/nova.conf 2016-05-30 00:12:07.120 ^[[01;33mWARNING oslo_reports.guru_meditation_report [^[[00;36m-^[[01;33m] ^[[01;35m^[[01;33mGuru mediation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.^[[00m 2016-05-30 00:12:07.305 ^[[00;36mINFO nova.virt.driver [^[[00;36m-^[[00;36m] ^[[01;35m^[[00;36mLoading compute driver 'novadocker.virt.docker.driver.DockerDriver'^[[00m 2016-05-30 00:12:07.306 ^[[01;31mERROR nova.virt.driver [^[[00;36m-^[[01;31m] ^[[01;35m^[[01;31mUnable to load the virtualization driver^[[00m ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00mTraceback (most recent call last): ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m File "/opt/stack/nova/nova/virt/driver.py", line 1624, in load_compute_driver ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m virtapi) ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 44, in import_object ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m return import_class(import_str)(*args, **kwargs) ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 30, in import_class ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m __import__(mod_str) ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00mImportError: No module named novadocker.virt.docker.driver ^[[01;31m2016-05-30 00:12:07.306 TRACE nova.virt.driver ^[[01;35m^[[00m n-cpu failed to start To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1586950/+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 1586915] [NEW] There is no supported disk format for hyperv image when performing operation "volume to upload to image"
Public bug reported: I have created a volume or boot volume and trying to perform an operation "upload to image" with disk format vhd. There is no option to "upload to image" with disk format vhd or vhdx. ** Affects: horizon Importance: Undecided Status: New -- 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/1586915 Title: There is no supported disk format for hyperv image when performing operation "volume to upload to image" Status in OpenStack Dashboard (Horizon): New Bug description: I have created a volume or boot volume and trying to perform an operation "upload to image" with disk format vhd. There is no option to "upload to image" with disk format vhd or vhdx. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1586915/+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
