[Yahoo-eng-team] [Bug 1803486] [NEW] Floating and negative values accepted in volume size field.
Public bug reported: As we know that in cinder, volume size cannot be a decimal value, only integer values are accepted. So when a user create a volume from horizon,horizon allows user to enter a decimal value or negative value in Size (GiB) field. obviously, user can't create a volume in decimal size as there are some validation on create button, But we can enforce more validation on the volume Size field (like user can't enter alphabets which is currently enforced), we shouldn't allow negative symbol '-' and decimal point '.' in the field too, So the user can only enter number from (0-9). ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: New ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- 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/1803486 Title: Floating and negative values accepted in volume size field. Status in OpenStack Dashboard (Horizon): New Bug description: As we know that in cinder, volume size cannot be a decimal value, only integer values are accepted. So when a user create a volume from horizon,horizon allows user to enter a decimal value or negative value in Size (GiB) field. obviously, user can't create a volume in decimal size as there are some validation on create button, But we can enforce more validation on the volume Size field (like user can't enter alphabets which is currently enforced), we shouldn't allow negative symbol '-' and decimal point '.' in the field too, So the user can only enter number from (0-9). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1803486/+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 1803475] [NEW] The init status of volume or snapshot will confusing user when resetting
Public bug reported: - Access admin->volume->volumes or admin->volume->snapshots; - Click update_status button; - On the dialog, we could see the current status, but could do nothing. ** 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/1803475 Title: The init status of volume or snapshot will confusing user when resetting Status in OpenStack Dashboard (Horizon): New Bug description: - Access admin->volume->volumes or admin->volume->snapshots; - Click update_status button; - On the dialog, we could see the current status, but could do nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1803475/+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 1803438] [NEW] Install and configure in keystone
Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [X] This doc is inaccurate in this way: Before configuring HTTP server need to install the same with 'zypper install apache2' - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2018-11-06 21:29 SHA: a9ca37cde55389153e578794e456ce2bbf4d9685 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-install-obs.rst URL: https://docs.openstack.org/keystone/rocky/install/keystone-install-obs.html ** Affects: keystone Importance: Undecided Status: New ** Tags: doc -- 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/1803438 Title: Install and configure in keystone Status in OpenStack Identity (keystone): New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [X] This doc is inaccurate in this way: Before configuring HTTP server need to install the same with 'zypper install apache2' - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2018-11-06 21:29 SHA: a9ca37cde55389153e578794e456ce2bbf4d9685 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/keystone-install-obs.rst URL: https://docs.openstack.org/keystone/rocky/install/keystone-install-obs.html To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1803438/+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 1800601] Re: [SRU] Infinite recursion in Python 3
This is fixed in disco in glance 2:18.0.0~b1~git20181108.97dac0f3-0ubuntu1. ** Changed in: glance (Ubuntu Disco) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1800601 Title: [SRU] Infinite recursion in Python 3 Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive rocky series: Fix Committed Status in Glance: Fix Released Status in glance package in Ubuntu: Fix Released Status in glance source package in Cosmic: Fix Committed Status in glance source package in Disco: Fix Released Bug description: Hi, When running unit tests under Python 3.7 when building the Rocky Debian package in Sid, I get a never ending recursion. Please see the Debian bug report: https://bugs.debian.org/911947 Basically, it's this: | File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys | return dict(self).keys() | File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys | return dict(self).keys() | File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys | return dict(self).keys() | RecursionError: maximum recursion depth exceeded while calling a Python object == Ubuntu SRU details == [Impact] An infinite recursion error occurs when running Python 3.6 glance from rocky. This issue has also been seen when running python 3.7 unit tests. The error has also been seen in a Rocky deployment and causes the glance api service to return 500 errors. [Test Case] Bionic (cloud-archive): Deploy the glance charm on bionic then upgrade it to rocky by updating the openstack-origin to cloud:bionic-rocky/proposed Cosmic: Note that for cosmic we don't have the ability to test an upgrade from queens to rocky like we can on bionic so we'll just manually test the python3 code. [Regression Potential] Fairly low. The patch is a minimal fix and will be fully exercised by the OpenStack charms team. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1800601/+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 1801326] Re: CRITICAL keystonemiddleware.auth_token
Looks like some kind of misconfiguration. You're trying to create a
flavor and nova-api is trying to call keystone to validate the token
using the keystone auth token middleware, and that is failing because
something is misconfigured. Check the install docs and config docs:
https://docs.openstack.org/nova/latest/configuration/config.html
#keystone-authtoken
https://docs.openstack.org/nova/latest/install/controller-install-
ubuntu.html
** Changed in: nova
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/1801326
Title:
CRITICAL keystonemiddleware.auth_token
Status in OpenStack Compute (nova):
Invalid
Bug description:
Hi
I am facing issue with dashboard (flavors function) and also command line
when creating new flavor.
Error (nova-api log):
2018-11-02 11:43:24.448 7149 INFO nova.osapi_compute.wsgi.server [-]
194.24.226.85 "POST /v2.1/b09e14755fcb47f897c55681c8ef73ff/flavors HTTP/1.1"
status: 503 len: 399 time: 0.0385082
2018-11-02 11:44:13.895 7143 WARNING keystonemiddleware.auth_token [-] Using
the in-process token cache is deprecated as of the 4.2.0 release and may be
removed in the 5.0.0 release or the 'O' development cycle. The in-process cache
causes inconsistent results and high memory usage. When the feature is removed
the auth_token middleware will not cache tokens by default which may result in
performance issues. It is recommended to use memcache for the auth_token token
cache by setting the memcached_servers option.
2018-11-02 11:44:13.919 7143 ERROR keystonemiddleware.auth_token [-] Bad
response code while validating token: 400
2018-11-02 11:44:13.929 7143 WARNING keystonemiddleware.auth_token [-]
Identity response: {"error": {"message": "Invalid input for field
'identity/password/user/password': None is not of type 'string'", "code": 400,
"title": "Bad Request"}}
2018-11-02 11:44:13.930 7143 CRITICAL keystonemiddleware.auth_token [-]
Unable to validate token: Failed to fetch token data from identity server
2018-11-02 11:44:13.932 7143 INFO nova.osapi_compute.wsgi.server [-]
194.24.226.85 "POST /v2.1/b09e14755fcb47f897c55681c8ef73ff/flavors HTTP/1.1"
status: 503 len: 399 time: 0.0378041
I have checked a lot of community posts and bugs raports but cannot
get rid of issue. Tried several methods. v2 api etc. Checked that
username and pw works for nova.
Configure paste: http://paste.openstack.org/show/733950/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1801326/+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 1803345] [NEW] unable to load custom identity domain drivers
Public bug reported: What's the reason of disabling ability of using custom identity drivers in domain configs? The feature was removed in Pike release. As I understand, the only way to use them is copy source code to keystone.identity namespace. Could you suggest any other ways or workarounds for using custom specific code for identity drivers? Example case - handle LDAP errors like password expiration in case of using ppolicy features in OpenLDAP (like password expire warning, login attempts warning, etc.) ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1803345 Title: unable to load custom identity domain drivers Status in OpenStack Identity (keystone): New Bug description: What's the reason of disabling ability of using custom identity drivers in domain configs? The feature was removed in Pike release. As I understand, the only way to use them is copy source code to keystone.identity namespace. Could you suggest any other ways or workarounds for using custom specific code for identity drivers? Example case - handle LDAP errors like password expiration in case of using ppolicy features in OpenLDAP (like password expire warning, login attempts warning, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1803345/+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 1803331] [NEW] Root disk lost when resizing instance from imagebackend to rbd backed flavor
Public bug reported:
We have flavor classes using different nova disk backends that are
separated using host aggregates. For example, we have a flavor named
l1.tiny which is using imagebackend, and s1.small using rbd backend. The
hypervisors configured for imagebackend are added to the host aggregate
where l1.* instances are scheduled, and the rbd hypervisors are in an
aggregate where s1.* instances are scheduled.
When resizing an instance from l1.tiny to s1.small, the instance fails
to resize and enters error state. The root disk is also lost during the
failed resize. The host of the instance is set to one of the s1.*
aggregate HVs, and the imagebackend disk is no longer present on the
original l1.* hypervisor.
The error provided in 'instance show' is:
| fault | {u'message': u'[errno 2] error
opening image 5a8ab7a3-3e59-442c-a603-2c24652788cb_disk at snapshot
None', u'code': 500, u'details': u' File "/openstack/venvs/nova-
untagged/local/lib/python2.7/site-packages/nova/compute/manager.py",
line 204, in decorated_function\nreturn function(self, context,
*args, **kwargs)\n File "/openstack/venvs/nova-
untagged/local/lib/python2.7/site-packages/nova/compute/manager.py",
line 4062, in finish_resize\n
self._set_instance_obj_error_state(context, instance)\n File
"/openstack/venvs/nova-untagged/local/lib/python2.7/site-
packages/oslo_utils/excutils.py", line 220, in __exit__\n
self.force_reraise()\n File "/openstack/venvs/nova-
untagged/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line
196, in force_reraise\nsix.reraise(self.type_, self.value,
self.tb)\n File "/openstack/venvs/nova-untagged/local/lib/python2.7
/site-packages/nova/compute/manager.py", line 4050, in finish_resize\n
disk_info, image_meta)\n File "/openstack/venvs/nova-
untagged/local/lib/python2.7/site-packages/nova/compute/manager.py",
line 4012, in _finish_resize\nold_instance_type)\n File
"/openstack/venvs/nova-untagged/local/lib/python2.7/site-
packages/oslo_utils/excutils.py", line 220, in __exit__\n
self.force_reraise()\n File "/openstack/venvs/nova-
untagged/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line
196, in force_reraise\nsix.reraise(self.type_, self.value,
self.tb)\n File "/openstack/venvs/nova-untagged/local/lib/python2.7
/site-packages/nova/compute/manager.py", line 4007, in _finish_resize\n
block_device_info, power_on)\n File "/openstack/venvs/nova-
untagged/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 7454, in finish_migration\n
fallback_from_host=migration.source_compute)\n File "/openstack/venvs
/nova-untagged/local/lib/python2.7/site-
packages/nova/virt/libvirt/driver.py", line 3160, in _create_image\n
fallback_from_host)\n File "/openstack/venvs/nova-
untagged/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py",
line 3264, in _create_and_inject_local_root\n
backend.create_snap(libvirt_utils.RESIZE_SNAPSHOT_NAME)\n File
"/openstack/venvs/nova-untagged/local/lib/python2.7/site-
packages/nova/virt/libvirt/imagebackend.py", line 941, in create_snap\n
return self.driver.create_snap(self.rbd_name, name)\n File
"/openstack/venvs/nova-untagged/local/lib/python2.7/site-
packages/nova/virt/libvirt/storage/rbd_utils.py", line 392, in
create_snap\nwith RBDVolumeProxy(self, str(volume), pool=pool) as
vol:\n File "/openstack/venvs/nova-untagged/local/lib/python2.7/site-
packages/nova/virt/libvirt/storage/rbd_utils.py", line 78, in __init__\n
driver._disconnect_from_rados(client, ioctx)\n File "/openstack/venvs
/nova-untagged/local/lib/python2.7/site-
packages/oslo_utils/excutils.py", line 220, in __exit__\n
self.force_reraise()\n File "/openstack/venvs/nova-
untagged/local/lib/python2.7/site-packages/oslo_utils/excutils.py", line
196, in force_reraise\nsix.reraise(self.type_, self.value,
self.tb)\n File "/openstack/venvs/nova-untagged/local/lib/python2.7
/site-packages/nova/virt/libvirt/storage/rbd_utils.py", line 74, in
__init__\nread_only=read_only))\n File "rbd.pyx", line 1392, in
rbd.Image.__init__ (/build/ceph-12.2.2/obj-x86_64-linux-
gnu/src/pybind/rbd/pyrex/rbd.c:13540)\n', u'created':
u'2018-11-14T11:03:11Z'} |
We are currently seeing this behavior on Ocata. I'm not certain if more recent
nova releases experience this 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/1803331
Title:
Root disk lost when resizing instance from imagebackend to rbd backed
flavor
Status in OpenStack Compute (nova):
New
Bug description:
We have flavor classes using different nova disk backends that are
separated using host aggregates. For example, we have a flavor named
l1.tiny which is using imagebackend, and s1.small using rbd backend.
The hypervisors configured for imagebackend are added to the
