Yeah the failure is logging the aggregates here:

https://github.com/openstack/nova/blob/fe21d29fa8b02f3e6437f035b0af6c58f8f454bb/nova/scheduler/host_manager.py#L171

With the unicode. This is similar to bug 1514325.

** Also affects: nova/mitaka
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: New => Confirmed

** Changed in: nova
   Importance: Undecided => Medium

** Changed in: nova/mitaka
       Status: New => Confirmed

** Changed in: nova/mitaka
   Importance: Undecided => Medium

-- 
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/1624277

Title:
  nova-scheduler: UnicodeDecodeError in host aggregates handling

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) mitaka series:
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1624277/+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

Reply via email to