[Yahoo-eng-team] [Bug 1580728] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 386: ordinal not in range(128) in nova.virt.libvirt.vif:unplug with unicode instance.display_nam
Reviewed: https://review.openstack.org/462735
Committed:
https://git.openstack.org/cgit/openstack/oslo.log/commit/?id=72e5c3c1e258589957011506c36dd8af0a481513
Submitter: Jenkins
Branch:master
commit 72e5c3c1e258589957011506c36dd8af0a481513
Author: melanie witt
Date: Thu May 4 20:22:47 2017 +
Use dict arg values for unicode checks in ContextFormatter
In ContextFormatter.format(), for python2 it checks each arg to
determine whether unicode should be used for the format message.
The problem is the code assumes the args are a list, when they can
also be a dict, for example:
LOG.info('%(thing)s', {'thing': '...'})
and in that case, the dict keys were implicitly being used for the
checks. The checks will always pass on string dict keys, so the
format message gets converted to unicode even though the corresponding
args will ultimately fail decoding to unicode. Then, the logging fails
with:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc6 in
position 0: ordinal not in range(128)
when the unicode format message causes an implicit conversion attempt
of the args to unicode [1].
This adds a check for the args type and uses the dict values for the
unicode checks so that dict args with values that fail decoding will
have: should_use_unicode = False.
Closes-Bug: #1580728
[1]
https://github.com/python/cpython/blob/2e576f5/Lib/logging/__init__.py#L338
Change-Id: I8c479e507efcf8acd3e3faa4a702fa6e1f18772f
** Changed in: oslo.log
Status: In Progress => Fix Released
--
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/1580728
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
386: ordinal not in range(128) in nova.virt.libvirt.vif:unplug with
unicode instance.display_name
Status in devstack:
Confirmed
Status in OpenStack Compute (nova):
Fix Released
Status in oslo.log:
Fix Released
Status in oslo.versionedobjects:
New
Bug description:
I saw this in the n-cpu logs for a xenproject CI run:
http://logs.openstack.xenproject.org/00/315100/1/check/dsvm-tempest-
xen/9649dc5/logs/screen-n-cpu.txt.gz
2016-05-11 16:19:09.457 27252 INFO nova.virt.libvirt.driver [-] [instance:
76c4ad96-87dd-4300-acdc-cbe65d3aa0a6] Instance destroyed successfully.
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 851, in emit
msg = self.format(record)
File "/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py", line
73, in format
return logging.StreamHandler.format(self, record)
File "/usr/lib/python2.7/logging/__init__.py", line 724, in format
return fmt.format(record)
File "/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py", line
265, in format
return logging.Formatter.format(self, record)
File "/usr/lib/python2.7/logging/__init__.py", line 464, in format
record.message = record.getMessage()
File "/usr/lib/python2.7/logging/__init__.py", line 328, in getMessage
msg = msg % self.args
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 386:
ordinal not in range(128)
Logged from file vif.py, line 966
That would be logging the vif object in unplug:
https://github.com/openstack/nova/blob/15abb39ef20ae76d602d50e67e43c3500a00cd3e/nova/virt/libvirt/vif.py#L966
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1580728/+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 1669610] Re: Insecure defaults for `openstack security group rule create`
** Also affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1669610 Title: Insecure defaults for `openstack security group rule create` Status in neutron: New Status in python-openstackclient: Incomplete Bug description: It's really easy to open up access to anyone by mistake. If you supply no options when creating a new rule, it defaults to allowing access to all ports to any remote host. I'm not sure what the right fix is, but I would expect that sort of permissive access to be a bit harder to create. # allow anyone to access any tcp port - so simple! $ openstack security group rule create default +---+--+ | Field | Value| +---+--+ | created_at| None | | description | None | | direction | ingress | | ether_type| IPv4 | | id| 7d481fad-9b57-4e71-9d63-fbba895e1a6c | | name | None | | port_range_max| None | | port_range_min| None | | project_id| c6f313e10752449ea9b70acfba353c80 | | protocol | tcp | | remote_group_id | None | | remote_ip_prefix | 0.0.0.0/0| | revision_number | None | | security_group_id | a5fbd65f-e4da-47d3-90cb-8dfc81eccd66 | | updated_at| None | +---+--+ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1669610/+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 1688147] Re: The example of disabling floating IPs tab should be removed
Reviewed: https://review.openstack.org/462324 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=78ccc9a68a01c7fc1e8852938f1bc5963cc7180e Submitter: Jenkins Branch:master commit 78ccc9a68a01c7fc1e8852938f1bc5963cc7180e Author: Ying Zuo Date: Wed May 3 17:18:21 2017 -0700 Remove the invalid example of floating IPs tab from doc The floating IPs tab on access and security panel was moved to its own panel in Ocata. Replaced the example of disabling floating IPs tab with an example to disable the orchestration services tab. Change-Id: Ibba5834b17a116f16b761c495732928b103b7324 Closes-bug: #1688147 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1688147 Title: The example of disabling floating IPs tab should be removed Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The floating ip tab on access and security panel was moved to its own panel in Ocata. The example of disabling floating ips tab should be removed from the override existing methods section on the customization file. https://docs.openstack.org/developer/horizon/topics/customizing.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1688147/+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 1309831] Re: failed to reach VERIFY_RESIZE
There was not any activity in long-term, so it would be nice to drop this from our queue. ** Changed in: tempest Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1309831 Title: failed to reach VERIFY_RESIZE Status in OpenStack Compute (nova): Incomplete Status in tempest: Invalid Bug description: http://logs.openstack.org/65/88165/2/check/check-tempest-dsvm- full/da0fa73/console.html Traceback (most recent call last): File "tempest/api/compute/v3/servers/test_server_actions.py", line 209, in test_resize_server_revert self.client.wait_for_server_status(self.server_id, 'VERIFY_RESIZE') File "tempest/services/compute/v3/json/servers_client.py", line 168, in wait_for_server_status raise_on_error=raise_on_error) File "tempest/common/waiters.py", line 89, in wait_for_server_status raise exceptions.TimeoutException(message) TimeoutException: Request timed out Details: Server 65867fad-6671-4912-8f1c-28977ad404d1 failed to reach VERIFY_RESIZE status and task state "None" within the required time (196 s). Current status: RESIZE. Current task state: resize_finish. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1309831/+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 1676648] Re: Launch instance modal doesn't pre-populate disk size
Reviewed: https://review.openstack.org/450489 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=c6f8d7444af43e64041e19cf1103a3c11712b124 Submitter: Jenkins Branch:master commit c6f8d7444af43e64041e19cf1103a3c11712b124 Author: Ying Zuo Date: Mon Mar 27 17:23:38 2017 -0700 Set minimum volume size based on the flavor selected On the Angular launch instance modal, the volume size for the new instance does not take the disk size required by the selected flavor into consideration, which is inconsistent with the Django launch instance modal. This patch will set the volume size of the new instance to the minimum disk size required by the selected flavor. Change-Id: Ifb35b70c5b41820024e17da783687bfe7880b8e8 Closes-bug: #1676648 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1676648 Title: Launch instance modal doesn't pre-populate disk size Status in OpenStack Dashboard (Horizon): Fix Released Bug description: On the Django launch instance modal, when user selects a boot source with new volume, the disk size required by the flavor will be pre- populated as the volume size. This is missing from the Angular launch instance modal. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1676648/+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 1688366] [NEW] KeyError: u'overs' in unit test runs
Public bug reported: This was just introduced in this change: https://review.openstack.org/#/c/460305/6/nova/tests/unit/compute/test_compute.py ** Affects: nova Importance: Low Status: Triaged ** Tags: low-hanging-fruit testing ** Tags added: low-hanging-fruit -- 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/1688366 Title: KeyError: u'overs' in unit test runs Status in OpenStack Compute (nova): Triaged Bug description: This was just introduced in this change: https://review.openstack.org/#/c/460305/6/nova/tests/unit/compute/test_compute.py To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1688366/+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 1680457] Re: Volume related quota exceptions not handled while creating vms
** Also affects: nova/ocata Importance: Undecided Status: New ** Changed in: nova/ocata Status: New => In Progress ** Changed in: nova/ocata Assignee: (unassigned) => Abhishek Sharma M (abhi.sharma) ** Changed in: nova Importance: Undecided => Low ** Changed in: nova/ocata Importance: Undecided => Low -- 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/1680457 Title: Volume related quota exceptions not handled while creating vms Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) ocata series: In Progress Bug description: VM creation may fail if it fails to meet these 3 volume related quotas. 1. per_volume_gigabytes - maximum size in GB per volume 2. gigabytes- total GB used across all volumes in a project 3. volumes - maximum number of volumes per project When any vm creation fails because of exceeding the above quota, the error message is not specific to which quota failed. A generic error message is generated which says "Failure prepping block device". We need to handle this scenario & generate problem related error message. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1680457/+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 1642494] Re: Host memory used for other VMs is not included
You need to set CONF.reserved_host_memory_mb to the amount of memory used by "other VMs not tracked by Nova". In the case of XenServer, the dom0 counts for a VM not tracked by Nova. ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1642494 Title: Host memory used for other VMs is not included Status in OpenStack Compute (nova): Invalid Bug description: The host free memory is always set by this formula: "free = total - reserved - instances" while the actual consumption will be ignored. If there are some other VMs also hosted on the host, the resource view will report an incorrect memory usage, and scheduler will not prevent instance claiming memory even when there isn't enough available. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1642494/+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 1580728] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 386: ordinal not in range(128) in nova.virt.libvirt.vif:unplug with unicode instance.display_nam
Reviewed: https://review.openstack.org/461912 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=564958dba6c280eb8e11ae9bbc819c7da6e204bd Submitter: Jenkins Branch:master commit 564958dba6c280eb8e11ae9bbc819c7da6e204bd Author: melanie witt Date: Tue May 2 21:47:12 2017 + Use six.text_type() when logging Instance object We're seeing a trace in gate jobs, for example: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 402: ordinal not in range(128) when attempting to log an Instance object with a unicode display name. This resurfaced relatively recently because of the change in devstack to use the new OSJournalHandler with use_journal=True which is suspected of causing some deadlock issues [1] unrelated to this bug. The problem occurs in code that logs an entire Instance object when the object has a field with unicode characters in it (display_name). When the object is sent to logging, the UnicodeDecodeError is raised while formatting the log record here [2]. This implies an implicit conversion attempt to unicode at this point. I found that with the Instance object, the conversion to unicode fails with the UnicodeDecodeError unless the encoding 'utf-8' is explicitly specified to six.text_type(). And when specifying an encoding to six.text_type(), the argument to convert must be a string, not an Instance object, so this does the conversion in two steps as a utility function: 1. Get the string representation of the Instance with repr() 2. Call six.text_type(instance_repr, 'utf-8') passing the encoding if not six.PY3 Closes-Bug: #1580728 [1] https://review.openstack.org/#/c/462163 [2] https://github.com/python/cpython/blob/2e576f5/Lib/logging/__init__.py#L338 Change-Id: I0fc3ae02cb2e401b3240faf0d8b6aa5dc52b91fc ** Changed in: nova Status: In Progress => Fix Released -- 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/1580728 Title: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 386: ordinal not in range(128) in nova.virt.libvirt.vif:unplug with unicode instance.display_name Status in devstack: Confirmed Status in OpenStack Compute (nova): Fix Released Status in oslo.log: New Status in oslo.versionedobjects: New Bug description: I saw this in the n-cpu logs for a xenproject CI run: http://logs.openstack.xenproject.org/00/315100/1/check/dsvm-tempest- xen/9649dc5/logs/screen-n-cpu.txt.gz 2016-05-11 16:19:09.457 27252 INFO nova.virt.libvirt.driver [-] [instance: 76c4ad96-87dd-4300-acdc-cbe65d3aa0a6] Instance destroyed successfully. Traceback (most recent call last): File "/usr/lib/python2.7/logging/__init__.py", line 851, in emit msg = self.format(record) File "/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py", line 73, in format return logging.StreamHandler.format(self, record) File "/usr/lib/python2.7/logging/__init__.py", line 724, in format return fmt.format(record) File "/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py", line 265, in format return logging.Formatter.format(self, record) File "/usr/lib/python2.7/logging/__init__.py", line 464, in format record.message = record.getMessage() File "/usr/lib/python2.7/logging/__init__.py", line 328, in getMessage msg = msg % self.args UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 386: ordinal not in range(128) Logged from file vif.py, line 966 That would be logging the vif object in unplug: https://github.com/openstack/nova/blob/15abb39ef20ae76d602d50e67e43c3500a00cd3e/nova/virt/libvirt/vif.py#L966 To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1580728/+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 1688342] [NEW] Encryption key is not properly formatted before being passed to dmcrypt
Public bug reported:
Description
===
A TypeError occurs when using Nova to boot an instance with ephemeral storage
encryption enabled.
When key management was moved from Nova to Castellan in the Newton
release, the key retrieval return value was changed from being formatted
as a list of unsigned ints (in the case of an octet stream) [1] to not
being formatted at all [2]. Nova's dmcrypt still expects the retrieved
key [3][4] to be formatted as an array of unsigned bytes [5].
References:
[1]
https://github.com/openstack/nova/blob/9702e5d2e9433c67067847c02fb100cd808a3596/nova/keymgr/barbican.py#L297-L323
[2]
https://github.com/openstack/castellan/blob/8d3f1cf375d28047cfd5f251afbb3f6d3ea7cda5/castellan/key_manager/barbican_key_manager.py#L527-L549
[3]
https://github.com/openstack/nova/blob/d219a3dcdc9c51bff3ebf2df086ea61a840ea3e9/nova/virt/libvirt/imagebackend.py#L714-L715
[4]
https://github.com/openstack/nova/blob/d219a3dcdc9c51bff3ebf2df086ea61a840ea3e9/nova/virt/libvirt/imagebackend.py#L674-L680
[5]
https://github.com/openstack/nova/blob/d219a3dcdc9c51bff3ebf2df086ea61a840ea3e9/nova/virt/libvirt/storage/dmcrypt.py#L48-L70
Steps to reproduce
==
1. Set up an LVM device:
Create a backing file:
$ truncate nova-lvm -s 2G
Mount the backing file on a loop device:
$ sudo losetup /dev/loop1 nova-lvm
Prepare the device for LVM:
$ sudo pvcreate /dev/loop1
Create the LVM group on the loop device:
$ sudo vgcreate nova-lvm /dev/loop1
2. Set up a devstack environment with ephemeral storage encryption enabled by
adding the following lines to `lib/nova`:
iniset $NOVA_CONF ephemeral_storage_encryption enabled "True"
iniset $NOVA_CONF ephemeral_storage_encryption cipher "aes-xts-plain64"
iniset $NOVA_CONF ephemeral_storage_encryption key_size "256"
iniset $NOVA_CONF libvirt images_type "lvm"
iniset $NOVA_CONF libvirt images_volume_group "nova-lvm"
3. Stack:
$ ./stack
4. Use Nova to boot an instance:
$ nova boot --flavor 1 --image {image_id}
Expected result
===
Ephemeral storage encryption succeeds and Nova successfully boots the instance.
Actual result
=
Ephemeral storage encryption fails with a TypeError (similar results can be
seen from Barbican Tempest gate failures [1]):
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] Traceback (most recent call last):
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] File
"/opt/stack/nova/nova/compute/manager.py", line 2122, in _build_resources
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] yield resources
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] File
"/opt/stack/nova/nova/compute/manager.py", line 1927, in _build_and_run_instance
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] block_device_info=block_device_info)
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] File
"/opt/stack/nova/nova/virt/libvirt/driver.py", line 2688, in spawn
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] block_device_info=block_device_info)
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] File
"/opt/stack/nova/nova/virt/libvirt/driver.py", line 3095, in _create_image
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] fallback_from_host)
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] File
"/opt/stack/nova/nova/virt/libvirt/driver.py", line 3211, in
_create_and_inject_local_root
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] instance, size, fallback_from_host)
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] File
"/opt/stack/nova/nova/virt/libvirt/driver.py", line 6780, in
_try_fetch_image_cache
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] size=size)
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] File
"/opt/stack/nova/nova/virt/libvirt/imagebackend.py", line 227, in cache
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] *args, **kwargs)
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] File
"/opt/stack/nova/nova/virt/libvirt/imagebackend.py", line 735, in create_image
2017-05-04 11:51:23.531 TRACE nova.compute.manager [instance:
760dedd5-60d7-470e-b753-70ee65e3ec56] create_lvm_image(base, size)
2017-05-04 11:51:23.531 TRACE nova.
[Yahoo-eng-team] [Bug 1551103] Re: nova quota-update should throw error if tenant-id is not correct
*** This bug is a duplicate of bug 1118066 *** https://bugs.launchpad.net/bugs/1118066 ** This bug has been marked a duplicate of bug 1118066 Nova should confirm quota requests against Keystone -- 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/1551103 Title: nova quota-update should throw error if tenant-id is not correct Status in OpenStack Compute (nova): Invalid Status in python-novaclient: In Progress Bug description: According to the help for “nova quota-update” the command works only with tenant-id. But currently the command works with everything and doesn't check if the user entered a valid tenant-id or not. The command should check if the tenant-id entered is a valid id and if it that is not the case should result in an error. Steps to reproduce the bug : 1. Run “keystone tenant-list” command to get the list of the existing tenants stack@stack:~/devstack$ keystone tenant-list +--++-+ |id|name| enabled | +--++-+ | 5484649a676547a0b63db23c2e7abaec | admin| True | | 8d97085693a740de9f3a8ccf8dd5dc4e | alt_demo | True | | 52eab592d3e94af082442daa505583ac |demo| True | | 62bf50f477754e3d910e3fcf677b9aed | invisible_to_admin | True | | fc32936f81e5400bb38d00985ad10fdf | service | True | +--++-+ 2. Run the “nova quota-update” command with a valid tenant-id from the list you got using the keystone command stack@stack:~/devstack$ nova quota-update --instances 8 5484649a676547a0b63db23c2e7abaec 3. Check if the quota got updated stack@stack:~/devstack$ nova quota-show --tenant 5484649a676547a0b63db23c2e7abaec +-+---+ | Quota | Limit | +-+---+ | instances | 8 | | cores | 20| | ram | 51200 | | floating_ips| 10| | fixed_ips | -1| | metadata_items | 128 | | injected_files | 5 | | injected_file_content_bytes | 10240 | | injected_file_path_bytes| 255 | | key_pairs | 100 | | security_groups | 10| | security_group_rules| 20| | server_groups | 10| | server_group_members| 10| +-+---+ As we can see the quota got updated when we used a valid tenant-id. Now lets check what happens if we use a tenant-id that doesn't exits. 4. Run the “nova quota-update” command again using an incorrect tenant-id stack@stack:~/devstack$ nova quota-update --instances 8 123123123123 5. Check if the quota got updated for this tenant-id stack@stack:~/devstack$ nova quota-show --tenant 123123123123 +-+---+ | Quota | Limit | +-+---+ | instances | 8 | | cores | 20| | ram | 51200 | | floating_ips| 10| | fixed_ips | -1| | metadata_items | 128 | | injected_files | 5 | | injected_file_content_bytes | 10240 | | injected_file_path_bytes| 255 | | key_pairs | 100 | | security_groups | 10| | security_group_rules| 20| | server_groups | 10| | server_group_members| 10| +-+---+ So the command updates the quota for a tenant that doesn't exists resulting in a bug for OpenStack. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1551103/+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 1434317] Re: nova quota update command doesn't complain when tenant name is given instead of tenant-id
*** This bug is a duplicate of bug 1118066 *** https://bugs.launchpad.net/bugs/1118066 ** This bug has been marked a duplicate of bug 1118066 Nova should confirm quota requests against Keystone -- 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/1434317 Title: nova quota update command doesn't complain when tenant name is given instead of tenant-id Status in OpenStack Compute (nova): Confirmed Bug description: nova quota-update --instances 8 <> - Updates Instances Quota on Horizon UI (Identity > Projects > Edit Project > Quota) nova quota-update --instances 8 <> - DOES NOT Update Instances Quota on Horizon UI (Identity > Projects > Edit Project > Quota) 1. Update with Tenant ID in CLI and Show with Tenant ID from CLI : Pass 2. Update with Tenant Name in CLI and Show with Tenant Name from CLI: Pass 3. Update with Tenant ID in CLI and View from Horizon: Pass 4. Update with Tenant Name in CLI and View from Horizon: Fail To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1434317/+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 1688182] Re: quota project_id not validated
*** This bug is a duplicate of bug 1118066 ***
https://bugs.launchpad.net/bugs/1118066
** This bug has been marked a duplicate of bug 1118066
Nova should confirm quota requests against Keystone
--
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/1688182
Title:
quota project_id not validated
Status in OpenStack Compute (nova):
New
Bug description:
The primary problem here is that the quota update and show REST apis
do not do any input validation for the project_id that gets passed in
due to which the following can be done:
1. quota can be updated against any junk value, which subsequently
gets updated into the quotas able. For eg.
PUT /v2.1/tenant-id/os-quota-sets/auctionweaver.pl
{
"quota_set": {
"ram": 5000
}
}
Response :
{
"quota_set": {
"injected_file_content_bytes": 10240,
"metadata_items": 128,
"server_group_members": 100,
"server_groups": 25,
"ram": 5000,
"floating_ips": 10,
"key_pairs": 100,
"instances": 100,
"security_group_rules": 20,
"injected_files": 5,
"cores": 550,
"fixed_ips": -1,
"injected_file_path_bytes": 255,
"security_groups": 10
}
}
The DB table for quotas has the below data which is incorrect. This
shows that there is no input validation done .
MariaDB [nova]> select * from quotas;
++-+-++--+--++-+
| id | created_at | updated_at | deleted_at | project_id
| resource | hard_limit | deleted |
++-+-++--+--++-+
| 1 | 2017-04-19 07:46:12 | 2017-04-19 11:13:32 | NULL |
auctionweaver.pl | ram | 5000 | 0 |
++-+-++--+--++-+
2. I could easily replace "auctionweaver.pl" in the above example with
a valid projectid for which I don't have any role assignment and it
will work fine.
3. Point 2 is true not just in the case of an admin. It works for all
roles without prejudice.
4. There's absolutely no input validation that's done for the
project_id passed in. After updating junk values into the table, I can
retrieve those values as well:
I was able to list the nova quotas using the below invalid URL.Please
note the "id" attribute in the response.
GET /v2.1/tenant-id/os-quota-sets/sfkhdskfjhd
{
"quota_set": {
"injected_file_content_bytes": 10240,
"metadata_items": 128,
"server_group_members": 100,
"server_groups": 25,
"ram": 4096,
"floating_ips": 10,
"key_pairs": 100,
"id": "sfkhdskfjhd",
"instances": 100,
"security_group_rules": 20,
"injected_files": 5,
"cores": 100,
"fixed_ips": -1,
"injected_file_path_bytes": 255,
"security_groups": 10
}
}
5. It should be technically possible for someone to try out sql
injections using this api. Some user with non-admin privileges for a
particular project might be able to view or update quota values for
the other projects using the above mechanism.
6. This behavior is the same for cinder apis as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1688182/+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 1688333] [NEW] Angular table footer missing the 'table_count' class
Public bug reported: The Python tables have a 'table_count' class on the content that shows how many items are currently being displayed. This is missing from the angular tables, making it difficult to theme. ** Affects: horizon Importance: Low Assignee: Rob Cresswell (robcresswell) Status: New ** Changed in: horizon Milestone: None => pike-2 ** Changed in: horizon Assignee: (unassigned) => Rob Cresswell (robcresswell) ** Changed in: horizon Importance: Undecided => Low -- 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/1688333 Title: Angular table footer missing the 'table_count' class Status in OpenStack Dashboard (Horizon): New Bug description: The Python tables have a 'table_count' class on the content that shows how many items are currently being displayed. This is missing from the angular tables, making it difficult to theme. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1688333/+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 1688249] [NEW] Instance create was failed.
Public bug reported:
I try create instance using "openstack server create". but instance create was
not end.
I checked the log. it is following error.
Also, "reboot", "stop", and "start" is fine. it issue was only "create".
# openstack server create --flavor 1.Micro_EV --image Ubuntu16.04_x86_64 --nic
net-id=1ae44feb-48be-4bf4-9130-f2e4791b91ce --security-group default --key-name
my test
+--+---+
| Field| Value
|
+--+---+
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone |
|
| OS-EXT-SRV-ATTR:host | None
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | None
|
| OS-EXT-SRV-ATTR:instance_name| instance-003b
|
| OS-EXT-STS:power_state | NOSTATE
|
| OS-EXT-STS:task_state| scheduling
|
| OS-EXT-STS:vm_state | building
|
| OS-SRV-USG:launched_at | None
|
| OS-SRV-USG:terminated_at | None
|
| accessIPv4 |
|
| accessIPv6 |
|
| addresses|
|
| adminPass| 7oS2JcLYfNek
|
| config_drive |
|
| created | 2017-05-04T12:52:10Z
|
| flavor | 1.Micro_EV
(c10bcfa9-e6dc-46a1-9dbe-171dde0f87e8) |
| hostId |
|
| id | 4c113eb1-a392-4ac4-a517-c3d20ef3a161
|
| image| Ubuntu16.04_x86_64
(2f14ad56-4cf7-411c-a163-bbafa76bb4d0) |
| key_name | my
|
| name | test
|
| os-extended-volumes:volumes_attached | []
|
| progress | 0
|
| project_id | e9d59586015f49bfa29e9856b0857fcc
|
| properties |
|
| security_groups | [{u'name': u'default'}]
|
| status | BUILD
|
| updated | 2017-05-04T12:52:11Z
|
| user_id | f66a4379b9ab46de8f075b1a3d5bb663
|
+--+---+
nova instance-action-list 4c113eb1-a392-4ac4-a517-c3d20ef3a161
+++-++
| Action | Request_ID | Message | Start_Time |
+++-++
+++-++
May 4 21:52:11 openstack nova-compute: 2017-05-04 21:52:11.627 14714 INFO
nova.compute.manager [req-91859bf3-d097-4c4b-83df-e472a7315da7
f66a4379b9ab46de8f075b1a3d5bb663 e9d59586015f49bfa29e9856b0857fcc - - -]
[instance: 4c113eb1-a392-4ac4-a517-c3d20ef3a161] Successfully reverted task
state from scheduling on failure for instance.
May 4 21:52:11 openstack nova-compute[14714]: Traceback (most recent call
last):
May 4 21:52:11 openstack nova-compute[14714]: File
"/usr/lib/python2.7/dist-packages/eventlet/queue.py", line 118, in switch
May 4 21:52:11 openstack nova-compute[14714]: self.greenlet.switch(value)
May 4 21:52:11 openstack nova-compute[14714]: File
"/usr/lib/python2.7/dist-packages/nova/utils.py", line 1113, in context_wrapper
May 4 21:52:11 openstack nova-compute[14714]: func(*args, **kwargs)
May 4 21:52:11 openstack nova-compute[14
[Yahoo-eng-team] [Bug 1569122] Re: return 500 when referring an image with status "SAVING"
Not reproducible any more
** Changed in: python-glanceclient
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1569122
Title:
return 500 when referring an image with status "SAVING"
Status in OpenStack Compute (nova):
Confirmed
Status in Glance Client:
Invalid
Bug description:
When I referred an image which is "SAVING" state by using 'nova' command,
it returns 500 error.
[How to reproduce]
1. Create empty image
$ glance image-create --name test --visibility public --disk-format ari
+--+--+
| Property | Value|
+--+--+
| checksum | None |
| container_format | None |
| created_at | 2016-04-12T01:27:49Z |
| disk_format | ari |
| id | 6d1ce183-e6ed-4dd0-a799-2f1b5abc6b3b |
| min_disk | 0|
| min_ram | 0|
| name | test |
| owner| 662765a438ed40a9bc85b82e9f2a2cab |
| protected| False|
| size | None |
| status | queued |
| tags | [] |
| updated_at | 2016-04-12T01:27:49Z |
| virtual_size | None |
| visibility | public |
+--+--+
2. Confirm the image status.
$ nova image-list
+--+--+++
| ID | Name | Status | Server |
+--+--+++
| 6d1ce183-e6ed-4dd0-a799-2f1b5abc6b3b | test | SAVING ||
+--+--+++
3. Execute 'nova image-show' or 'nova image-delete'
(This is example of 'nova image-show')
$ nova --debug image-show 6d1ce183-e6ed-4dd0-a799-2f1b5abc6b3b
DEBUG (extension:157) found extension EntryPoint.parse('v2token =
keystoneauth1.loading._plugins.identity.v2:Token')
DEBUG (extension:157) found extension EntryPoint.parse('admin_token =
keystoneauth1.loading._plugins.admin_token:AdminToken')
DEBUG (extension:157) found extension EntryPoint.parse('v3oidcauthcode =
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
DEBUG (extension:157) found extension EntryPoint.parse('v2password =
keystoneauth1.loading._plugins.identity.v2:Password')
DEBUG (extension:157) found extension EntryPoint.parse('v3password =
keystoneauth1.loading._plugins.identity.v3:Password')
DEBUG (extension:157) found extension EntryPoint.parse('v3oidcpassword =
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
DEBUG (extension:157) found extension EntryPoint.parse('token =
keystoneauth1.loading._plugins.identity.generic:Token')
DEBUG (extension:157) found extension EntryPoint.parse('v3token =
keystoneauth1.loading._plugins.identity.v3:Token')
DEBUG (extension:157) found extension EntryPoint.parse('password =
keystoneauth1.loading._plugins.identity.generic:Password')
DEBUG (session:248) REQ: curl -g -i -X GET http://192.168.3.223:5000/v2.0 -H
"Accept: application/json" -H "User-Agent: keystoneauth1/2.3.0
python-requests/2.9.1 CPython/2.7.6"
INFO (connectionpool:207) Starting new HTTP connection (1): 192.168.3.223
DEBUG (connectionpool:387) "GET /v2.0 HTTP/1.1" 200 339
DEBUG (session:277) RESP: [200] Content-Length: 339 Vary: X-Auth-Token
Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu) Connection:
Keep-Alive Date: Tue, 12 Apr 2016
01:28:44 GMT Content-Type: application/json x-openstack-request-id:
req-bc96ffbe-fe92-4fbe-931e-51c071766609
RESP BODY: {"version": {"status": "stable", "updated":
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type":
"application/vnd.openstack.identity-v2.0+json"
}], "id": "v2.0", "links": [{"href": "http://192.168.3.223:5000/v2.0/";,
"rel": "self"}, {"href": "http://docs.openstack.org/";, "type": "text/html",
"rel": "describedby"}]}}
DEBUG (v2:63) Making authentication request to
http://192.168.3.223:5000/v2.0/tokens
DEBUG (connectionpool:387) "POST /v2.0/tokens HTTP/1.1" 200 3569
DEBUG (session:248) REQ: curl -g -i -X GET
http://192.168.3.223:8774/v2.1/662765a438ed40a9bc85b82e9f2a2cab -H "User-Agent:
python-novaclient" -H "Accept: application/json" -H "X-
Auth-Token: {SHA1}d52cbbc7997c02255185fbf06a3c608866de4091"
I
[Yahoo-eng-team] [Bug 1680457] Re: Volume related quota exceptions not handled while creating vms
Reviewed: https://review.openstack.org/460305 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=510371d526bd45195be806fb153646abdc269b70 Submitter: Jenkins Branch:master commit 510371d526bd45195be806fb153646abdc269b70 Author: Abhishek Sharma Date: Wed Apr 26 16:38:15 2017 -0400 Catching OverQuota Exception When any vm creation fails because of exceeding 'gigabytes', 'volumes', 'per_volume_gigabytes' quotas, the error message generated is specific to 'volumes' quota which says "Volume resource quota exceeded". Instead, the error message should be specific to the quota which failed. Change-Id: I9c1ac2cd4752d5aac20d06407792647b4549ad3d Closes-Bug: 1680457 ** Changed in: nova Status: In Progress => Fix Released -- 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/1680457 Title: Volume related quota exceptions not handled while creating vms Status in OpenStack Compute (nova): Fix Released Bug description: VM creation may fail if it fails to meet these 3 volume related quotas. 1. per_volume_gigabytes - maximum size in GB per volume 2. gigabytes- total GB used across all volumes in a project 3. volumes - maximum number of volumes per project When any vm creation fails because of exceeding the above quota, the error message is not specific to which quota failed. A generic error message is generated which says "Failure prepping block device". We need to handle this scenario & generate problem related error message. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1680457/+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 1688228] [NEW] Failure in resize_instance after cast to finish_resize still sets instance error state
Public bug reported: This is from code inspection only. ComputeManager.resize_instance does: with self._error_out_instance_on_exception(context, instance, quotas=quotas): ...stuff... self.compute_rpcapi.finish_resize(context, instance, migration, image, disk_info, migration.dest_compute, reservations=quotas.reservations) ... Responsibility for the instance has now been punted to the destination, but... self._notify_about_instance_usage(context, instance, "resize.end", network_info=network_info) compute_utils.notify_about_instance_action(context, instance, self.host, action=fields.NotificationAction.RESIZE, phase=fields.NotificationPhase.END) self.instance_events.clear_events_for_instance(instance) The problem is that a failure in anything after the cast to finish_resize will cause the instance to be put in an error state and its quotas rolled back. This would not be correct, as any error here would be purely ephemeral. The resize operation will continue on the destination regardless, so this would almost certainly result in an inconsistent state. ** 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/1688228 Title: Failure in resize_instance after cast to finish_resize still sets instance error state Status in OpenStack Compute (nova): New Bug description: This is from code inspection only. ComputeManager.resize_instance does: with self._error_out_instance_on_exception(context, instance, quotas=quotas): ...stuff... self.compute_rpcapi.finish_resize(context, instance, migration, image, disk_info, migration.dest_compute, reservations=quotas.reservations) ... Responsibility for the instance has now been punted to the destination, but... self._notify_about_instance_usage(context, instance, "resize.end", network_info=network_info) compute_utils.notify_about_instance_action(context, instance, self.host, action=fields.NotificationAction.RESIZE, phase=fields.NotificationPhase.END) self.instance_events.clear_events_for_instance(instance) The problem is that a failure in anything after the cast to finish_resize will cause the instance to be put in an error state and its quotas rolled back. This would not be correct, as any error here would be purely ephemeral. The resize operation will continue on the destination regardless, so this would almost certainly result in an inconsistent state. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1688228/+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 1684261] Re: AggregateImagePropertiesIsolation example doesn't actually indicate how it works
Adding nova to this bug report. I think some more working examples around that filter would benefit both the developer docs and the openstack-manuals doc. Currently there isn't anything concrete, really. ** 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/1684261 Title: AggregateImagePropertiesIsolation example doesn't actually indicate how it works Status in OpenStack Compute (nova): New Status in openstack-manuals: Confirmed Bug description: The AggregateImagePropertiesIsolation filter documentation in https://docs.openstack.org/ocata/config- reference/compute/schedulers.html does not actually effectively illustrate how the filter works. * "For example, the following aggregate myWinAgg has the Windows operating system as metadata (named ‘windows’):" - the subsequent `openstack aggregate show MyWinAgg` does not show any such metadata. * "In this example, because the following Win-2012 image has the windows property, it boots on the sf-devel host (all other filters being equal):" - the subsequent output for `openstack image show Win-2012` does not actually show the image properties (the output is truncated). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1684261/+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 1688220] [NEW] Operational error thrown by nova-api while serving the request
Public bug reported:
Request to be served by nova fails with operational error:
For reference adding floating ip to the server
Input task :
Rally:
"NovaServers.bootvm_userdata_test_snat": [
{
"runner": {
"type": "constant",
"concurrency": 7,
"times": 22
},
Below traces can be found: req-d5bc233e-d1de-45d8-a353-c17ced17cd63
2017-04-28 11:20:50.598 21334 DEBUG nova.api.openstack.wsgi
[req-d5bc233e-d1de-45d8-a353-c17ced17cd63 c_rally_46c61b3d_hnwpef3T
c_rally_46c61b3d_aYPvYjVl] Action: 'action', calling method: >, body: {"addFloatingIp": {"fixed_address": "1.2.44.3",
"address": "61.26.96.145"}} _process_stack
/opt/stack/nova/nova/api/openstack/wsgi.py:623
2017-04-28 11:20:50.601 21334 DEBUG nova.compute.api
[req-d5bc233e-d1de-45d8-a353-c17ced17cd63 c_rally_46c61b3d_hnwpef3T
c_rally_46c61b3d_aYPvYjVl] [instance: c57cddc2-3aed-4c47-99b0-6f3ac16015b2]
Fetching instance by UUID get /opt/stack/nova/nova/compute/api.py:2352
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
[req-d5bc233e-d1de-45d8-a353-c17ced17cd63 c_rally_46c61b3d_hnwpef3T
c_rally_46c61b3d_aYPvYjVl] Unexpected exception in API method
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions Traceback
(most recent call last):
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/extensions.py", line 338, in wrapped
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions return
f(*args, **kwargs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/validation/__init__.py", line 108, in wrapper
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions return
func(*args, **kwargs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/compute/floating_ips.py", line 223, in
_add_floating_ip
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
expected_attrs=['flavor'])
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/api/openstack/common.py", line 481, in get_instance
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
expected_attrs=expected_attrs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 2355, in get
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
expected_attrs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/compute/api.py", line 2315, in _get_instance
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions context,
instance_uuid, expected_attrs=expected_attrs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line
184, in wrapper
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions result =
fn(cls, context, *args, **kwargs)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/objects/instance.py", line 463, in get_by_uuid
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
use_slave=use_slave)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/opt/stack/nova/nova/db/sqlalchemy/api.py", line 235, in wrapper
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions with
reader_mode.using(context):
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/contextlib.py", line 17, in __enter__
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions return
self.gen.next()
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py",
line 944, in _transaction_scope
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
allow_async=self._allow_async) as resource:
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/lib/python2.7/contextlib.py", line 17, in __enter__
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions return
self.gen.next()
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py",
line 558, in _session
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
bind=self.connection, mode=self.mode)
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py",
line 317, in _create_session
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions
self._start()
2017-04-28 11:20:50.609 21334 ERROR nova.api.openstack.extensions File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py",
line 403, in
[Yahoo-eng-team] [Bug 1686898] Re: List of available QoS rules should be changed
Reviewed: https://review.openstack.org/461257 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3299cdffae5cd7196a1676da103da5e2e413ec21 Submitter: Jenkins Branch:master commit 3299cdffae5cd7196a1676da103da5e2e413ec21 Author: Sławek Kapłoński Date: Sun Apr 30 08:17:29 2017 + Change list of available qos rules This patch changes way how neutron calculates which QoS rules are available to use. It now returns all rule types which are supported by at least one loaded QoS driver. If user will want to apply policy with rule unsupported by driver used by port then it will be catched on port/network update event. This validation mechanism was introduced in I75bd18b3a1875daa5639dd141fb7bbd6e1c54118 DocImpact: list of returned available QoS rule types is changed Change-Id: Ia00d349625db358ab486802fc0ff2e69eaa3895e Closes-Bug: #1686898 ** 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/1686898 Title: List of available QoS rules should be changed Status in neutron: Fix Released Bug description: Currently Neutron has API call "qos-available-rule-types" which will return subset of qos rules supported by all loaded drivers (openvswitch, linuxbridge, etc.) After https://bugs.launchpad.net/neutron/+bug/1586056 was closed it should be done in different way. Neutron API in response to qos-available-rule-types should return subset of rules supported by ANY of loaded drivers, not by all drivers. This should be changed because now if rule is supported by at least on of drivers than it can be used and applied to ports bound with this driver. Neutron will not allow to apply such rule to other ports. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1686898/+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 1688215] [NEW] Change list of available qos rules
Public bug reported: https://review.openstack.org/461257 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 3299cdffae5cd7196a1676da103da5e2e413ec21 Author: Sławek Kapłoński Date: Sun Apr 30 08:17:29 2017 + Change list of available qos rules This patch changes way how neutron calculates which QoS rules are available to use. It now returns all rule types which are supported by at least one loaded QoS driver. If user will want to apply policy with rule unsupported by driver used by port then it will be catched on port/network update event. This validation mechanism was introduced in I75bd18b3a1875daa5639dd141fb7bbd6e1c54118 DocImpact: list of returned available QoS rule types is changed Change-Id: Ia00d349625db358ab486802fc0ff2e69eaa3895e Closes-Bug: #1686898 ** Affects: neutron Importance: Undecided Status: New ** Tags: doc neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1688215 Title: Change list of available qos rules Status in neutron: New Bug description: https://review.openstack.org/461257 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 3299cdffae5cd7196a1676da103da5e2e413ec21 Author: Sławek Kapłoński Date: Sun Apr 30 08:17:29 2017 + Change list of available qos rules This patch changes way how neutron calculates which QoS rules are available to use. It now returns all rule types which are supported by at least one loaded QoS driver. If user will want to apply policy with rule unsupported by driver used by port then it will be catched on port/network update event. This validation mechanism was introduced in I75bd18b3a1875daa5639dd141fb7bbd6e1c54118 DocImpact: list of returned available QoS rule types is changed Change-Id: Ia00d349625db358ab486802fc0ff2e69eaa3895e Closes-Bug: #1686898 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1688215/+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 1688206] [NEW] Operations log polluted with policy requests
Public bug reported:
Currently operations log is polluted with a lot of requests regarding
policy enforcement which are not generated by the user explicitly, like
in the following example:
2017-05-04 10:09:51,683 [Personal makowals]
[e6721c4a-2600-4260-a6f3-e287c04c1a4c] [makowals] [https] [/project/images]
[/api/policy/] [None] [POST] [200] [{"rules": [["image", "modify_image"]],
"token": "", "password": "", "csrfmiddlewaretoken": ""}]
2017-05-04 10:09:51,687 [Personal makowals]
[e6721c4a-2600-4260-a6f3-e287c04c1a4c] [makowals] [https] [/project/images]
[/api/policy/] [None] [POST] [200] [{"rules": [["image", "add_image"]],
"token": "", "password": "", "csrfmiddlewaretoken": ""}]
2017-05-04 10:09:51,693 [Personal makowals]
[e6721c4a-2600-4260-a6f3-e287c04c1a4c] [makowals] [https] [/project/images]
[/api/policy/] [None] [POST] [200] [{"rules": [["image", "delete_image"]],
"token": "", "password": "", "csrfmiddlewaretoken": ""}]
As for auditing purposes these requests have no value, it would make
more sense to hide them by default or at least provide some
configuration option (like 'ignored_urls') in order for the operator to
be able to disable these entries.
** Affects: horizon
Importance: Undecided
Assignee: Mateusz Kowalski (makowals)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1688206
Title:
Operations log polluted with policy requests
Status in OpenStack Dashboard (Horizon):
In Progress
Bug description:
Currently operations log is polluted with a lot of requests regarding
policy enforcement which are not generated by the user explicitly,
like in the following example:
2017-05-04 10:09:51,683 [Personal makowals]
[e6721c4a-2600-4260-a6f3-e287c04c1a4c] [makowals] [https] [/project/images]
[/api/policy/] [None] [POST] [200] [{"rules": [["image", "modify_image"]],
"token": "", "password": "", "csrfmiddlewaretoken": ""}]
2017-05-04 10:09:51,687 [Personal makowals]
[e6721c4a-2600-4260-a6f3-e287c04c1a4c] [makowals] [https] [/project/images]
[/api/policy/] [None] [POST] [200] [{"rules": [["image", "add_image"]],
"token": "", "password": "", "csrfmiddlewaretoken": ""}]
2017-05-04 10:09:51,693 [Personal makowals]
[e6721c4a-2600-4260-a6f3-e287c04c1a4c] [makowals] [https] [/project/images]
[/api/policy/] [None] [POST] [200] [{"rules": [["image", "delete_image"]],
"token": "", "password": "", "csrfmiddlewaretoken": ""}]
As for auditing purposes these requests have no value, it would make
more sense to hide them by default or at least provide some
configuration option (like 'ignored_urls') in order for the operator
to be able to disable these entries.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1688206/+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 1688188] [NEW] Handel auto created domain when creating duplicate idp in federation
Public bug reported: If we create an idp with ID 'keystone-ipd', then we create idp with the same ID. We get the result like 'conflict happens', it is ok. But when I see the domain list. the auto generated domain still here. I think, the second idp was created failed, then the resource auto generated it used should be cleared. If we create an idp specifing the domain, the idp was created failed and the specifing domain was not auto generated, so the resource should not be cleared. ** Affects: keystone Importance: Undecided Assignee: yangweiwei (496176919-6) Status: In Progress -- 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/1688188 Title: Handel auto created domain when creating duplicate idp in federation Status in OpenStack Identity (keystone): In Progress Bug description: If we create an idp with ID 'keystone-ipd', then we create idp with the same ID. We get the result like 'conflict happens', it is ok. But when I see the domain list. the auto generated domain still here. I think, the second idp was created failed, then the resource auto generated it used should be cleared. If we create an idp specifing the domain, the idp was created failed and the specifing domain was not auto generated, so the resource should not be cleared. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1688188/+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 1688189] [NEW] Member create raises 500 error for unicode charater values
Public bug reported:
If user passes member as Unicode character while creating member for
image then he will get HTTP 500 error.
Steps to reproduce:
1. Create image
2. Assign member to image using
$ glance member-create e64f4347-51d6-4f97-8b6e-02e40c7ecb30 𠜎
or using curl
$ curl -g -i -X POST
http://10.232.48.198:9292/v2/images/e64f4347-51d6-4f97-8b6e-02e40c7ecb30/members
-H "User-Agent: python-glanceclient" -H "Content-Type: application/json" -H
"X-Auth-Token:
gABZCs01HPjCjKDkYnWQECtu9dYOxySXXrMH-lH4xO9xZBtl4MXNIPbTwkuCWSQ4EOh0tKvOPz55DmMdyOM0RYziM-qNE2Jikncq2oExZvf6k8OZYj_Vad5Q04p_uCU0Rg-9b94mVFfv_HaImCnT9ofO6RQZyNLOf1zc-AOzQPOMnjv9e4g"
-d '{"member": "𠜎"}'
Output:
500 Internal Server Error
500 Internal Server Error
The server has either erred or is incapable of performing the requested
operation.
API Logs:
500 Internal Server Error: The server has either erred or is incapable of
performing the requested operation. (HTTP 500)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi self._flush(objects)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 2259,
in _flush
2017-05-04 12:18:14.460 TRACE glance.common.wsgi
transaction.rollback(_capture_exception=True)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line
66, in __exit__
2017-05-04 12:18:14.460 TRACE glance.common.wsgi compat.reraise(exc_type,
exc_value, exc_tb)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 2223,
in _flush
2017-05-04 12:18:14.460 TRACE glance.common.wsgi flush_context.execute()
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line
389, in execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi rec.execute(self)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line
548, in execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi uow
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line
181, in save_obj
2017-05-04 12:18:14.460 TRACE glance.common.wsgi mapper, table, insert)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line
835, in _emit_insert_statements
2017-05-04 12:18:14.460 TRACE glance.common.wsgi execute(statement, params)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 945,
in execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi return meth(self,
multiparams, params)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/elements.py", line 263,
in _execute_on_connection
2017-05-04 12:18:14.460 TRACE glance.common.wsgi return
connection._execute_clauseelement(self, multiparams, params)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1053,
in _execute_clauseelement
2017-05-04 12:18:14.460 TRACE glance.common.wsgi compiled_sql,
distilled_params
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1189,
in _execute_context
2017-05-04 12:18:14.460 TRACE glance.common.wsgi context)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1398,
in _handle_dbapi_exception
2017-05-04 12:18:14.460 TRACE glance.common.wsgi
util.raise_from_cause(newraise, exc_info)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/compat.py", line 203,
in raise_from_cause
2017-05-04 12:18:14.460 TRACE glance.common.wsgi reraise(type(exception),
exception, tb=exc_tb, cause=cause)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1182,
in _execute_context
2017-05-04 12:18:14.460 TRACE glance.common.wsgi context)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line
470, in do_execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi cursor.execute(statement,
parameters)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 166, in
execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi result = self._query(query)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/pymysql/cur
[Yahoo-eng-team] [Bug 1568208] Re: TypeError: cannot concatenate 'str' and 'OptGroup' objects during Guru Meditation Report run
** Changed in: oslo.config Status: In Progress => Invalid ** Changed in: oslo.config Assignee: Roman Podoliaka (rpodolyaka) => (unassigned) -- 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/1568208 Title: TypeError: cannot concatenate 'str' and 'OptGroup' objects during Guru Meditation Report run Status in OpenStack Compute (nova): Fix Released Status in oslo.config: Invalid Bug description: I noticed a trace in a recent tempest job run [1] like the following. From what I can tell, somehow rootkey here is an OptGroup object instead of the expected str. Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/oslo_reports/guru_meditation_report.py", line 180, in handle_signal res = cls(version, frame).run() File "/usr/local/lib/python2.7/dist-packages/oslo_reports/guru_meditation_report.py", line 228, in run return super(GuruMeditation, self).run() File "/usr/local/lib/python2.7/dist-packages/oslo_reports/report.py", line 77, in run return "\n".join(six.text_type(sect) for sect in self.sections) File "/usr/local/lib/python2.7/dist-packages/oslo_reports/report.py", line 77, in return "\n".join(six.text_type(sect) for sect in self.sections) File "/usr/local/lib/python2.7/dist-packages/oslo_reports/report.py", line 102, in __str__ return self.view(self.generator()) File "/usr/local/lib/python2.7/dist-packages/oslo_reports/views/text/header.py", line 36, in __call__ return six.text_type(self.header) + "\n" + six.text_type(model) File "/usr/local/lib/python2.7/dist-packages/oslo_reports/models/base.py", line 73, in __str__ return self.attached_view(self_cpy) File "/usr/local/lib/python2.7/dist-packages/oslo_reports/views/text/generic.py", line 153, in __call__ return "\n".join(serialize(model, None, -1)) File "/usr/local/lib/python2.7/dist-packages/oslo_reports/views/text/generic.py", line 124, in serialize res.extend(serialize(root[key], key, indent + 1)) File "/usr/local/lib/python2.7/dist-packages/oslo_reports/views/text/generic.py", line 113, in serialize res.append((self.indent_str * indent) + rootkey) TypeError: cannot concatenate 'str' and 'OptGroup' objects Unable to run Guru Meditation Report! [1] http://logs.openstack.org/41/302341/5/check/gate-tempest-dsvm-full/f51065e/logs/screen-n-cpu.txt.gz?#_2016-04-08_21_08_08_994 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1568208/+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
