nova-scheduler: UnicodeDecodeError in host aggregates handling

Bug #1624277 reported by Roman Bogorodskiy on 2016-09-16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Nazeema Begum

Bug Description

nova-scheduler doesn't seem to like when there are non-asci characters in the host aggregate objects.

Steps to reproduce:

1. Create a host aggregate with some non-asci chars in properties, e.g.:

$ openstack aggregate show test_aggr
| Field | Value |
| availability_zone | nova |
| created_at | 2016-09-09T17:31:12.000000 |
| deleted | False |
| deleted_at | None |
| hosts | [u'node-6.domain.tld', u'node-7.domain.tld'] |
| id | 54 |
| name | test_aggr |
| properties | test_meta='проверка мета' |
| updated_at | None |

2. Start an instance

Expected result: instance started.
Actual result: instance creating failed, exception in the nova-scheduler.log attached.

This is reproducible with Mitaka, didn't try master.

Roman Bogorodskiy (novel) wrote :
description: updated
Matt Riedemann (mriedem) wrote :

Yeah the failure is logging the aggregates here:

With the unicode. This is similar to bug 1514325.

Changed in nova:
status: New → Confirmed
importance: Undecided → Medium
Andrey Volkov (avolkov) wrote :

With high probability, it's related to oslo.log library bug

I prepared backport to upstream stable mitaka
which should fix the issue.

Changed in nova:
status: Confirmed → In Progress
assignee: nobody → Andrey Volkov (avolkov)
Sean Dague (sdague) on 2017-06-14
Changed in nova:
status: In Progress → Incomplete
Sean Dague (sdague) on 2017-06-23
Changed in nova:
assignee: Andrey Volkov (avolkov) → nobody
Sam Morrison (sorrison) wrote :

We have started to see this in Pike

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers