failed to run vm on Ocata version after deployed successfully
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
New
|
Undecided
|
Unassigned |
Bug Description
Hi Guys:
I deploy openstack ocata successfully by kolla, run init-runonce, failed to boot a vm .
[root@kode0 nova]# nova show demo1
/usr/lib/
warnings.
+------
| Property | Value |
+------
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-STS:vm_state | error |
| OS-SRV-
| OS-SRV-
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2017-03-
| description | demo1 |
| fault | {"message": "'NoneType' object is not iterable", "code": 500, "details": " File \"/usr/
| | filter_properties) |
| | File \"/usr/
| | instance_
| | ", "created": "2017-03-
| flavor | m1.tiny (1) |
| hostId | |
| host_status | |
| id | 50837923-
| image | cirros (c0945eb1-
| key_name | mykey |
| locked | False |
| metadata | {} |
| name | demo1 |
| os-extended-
| status | ERROR |
| tags | [] |
| tenant_id | aa0bc3b5640a4c8
| updated | 2017-03-
| user_id | 2b88490754924b8
+------
[root@kode0 nova]# vim /usr/lib/
[root@kode0 nova]#
[root@kode0 nova]#
[root@kode0 nova]# nova hypervisor-list
/usr/lib/
warnings.
+----+-
| ID | Hypervisor hostname | State | Status |
+----+-
| 4 | kode5.genomics.cn | up | enabled |
| 7 | kode4.genomics.cn | up | enabled |
+----+-
[root@kode0 nova]#
[root@kode0 nova]# nova service-list
/usr/lib/
warnings.
+----+-
| Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+----+-
| 22 | nova-consoleauth | kode0.genomics.cn | internal | enabled | up | 2017-03-
| 37 | nova-scheduler | kode0.genomics.cn | internal | enabled | up | 2017-03-
| 40 | nova-conductor | kode0.genomics.cn | internal | enabled | up | 2017-03-
| 46 | nova-consoleauth | kode2.genomics.cn | internal | enabled | up | 2017-03-
| 49 | nova-conductor | kode2.genomics.cn | internal | enabled | up | 2017-03-
| 52 | nova-consoleauth | kode1.genomics.cn | internal | enabled | up | 2017-03-
| 55 | nova-conductor | kode1.genomics.cn | internal | enabled | up | 2017-03-
| 58 | nova-scheduler | kode1.genomics.cn | internal | enabled | up | 2017-03-
| 61 | nova-scheduler | kode2.genomics.cn | internal | enabled | up | 2017-03-
| 64 | nova-compute | kode5.genomics.cn | nova | enabled | up | 2017-03-
| 67 | nova-compute | kode4.genomics.cn | nova | enabled | up | 2017-03-
+----+-
[root@kode0 n
how to trouble-shooting this issue?
I "docker logs" nova-compute, nova-scheduler,
Hi, logs can be found at /var/lib/ docker/ volumes/ kolla_logs/ _data/nova/
Check there for the error, probably will be at scheduler, compute or conductor logs.