| 2016-09-16 08:57:34 |
Roman Bogorodskiy |
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. |
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. |
|
