I am having troubles booting an server. It will start booting, perhaps for several minutes, and then it will go into an error state.
[email protected]:/home/jeff# nova list +--------------------------------------+-----------------------+--------+----------------------+-------------+----------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+-----------------------+--------+----------------------+-------------+----------------------+ | 72cc091c-3ebc-40c5-b075-32295003edc9 | jeff5_app1-pokki-dev3 | BUILD | block_device_mapping | NOSTATE | VLAN_40=10.50.40.93 | | 6633c7f1-5aba-4b49-8781-bd1d74b1b72e | jeff_app1-pokki-dev3 | ACTIVE | - | Running | VLAN_40=10.50.40.92 | | 4f45c14d-57bf-4dc8-9e96-d7934816fa6e | observium1-prod | ACTIVE | - | Running | VLAN_15=10.50.15.144 | +--------------------------------------+-----------------------+--------+----------------------+-------------+----------------------+ [email protected]:/home/jeff# [email protected]:/home/jeff# nova list +--------------------------------------+-----------------------+--------+------------+-------------+----------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+-----------------------+--------+------------+-------------+----------------------+ | 72cc091c-3ebc-40c5-b075-32295003edc9 | jeff5_app1-pokki-dev3 | ERROR | - | NOSTATE | | | 6633c7f1-5aba-4b49-8781-bd1d74b1b72e | jeff_app1-pokki-dev3 | ACTIVE | - | Running | VLAN_40=10.50.40.92 | | 4f45c14d-57bf-4dc8-9e96-d7934816fa6e | observium1-prod | ACTIVE | - | Running | VLAN_15=10.50.15.144 | +--------------------------------------+-----------------------+--------+------------+-------------+----------------------+ [email protected]:/home/jeff# I have tried using the --debug switch to the nova command, and I see the API calls go by. They all have 200 status codes. I have tried fgreping the ID in /var/log/* with the -r switch, and I see lots of GETs with 200 status returns. On one of the tests, I was experimenting with using a network port, and I see that something is deleting the network port, but this latest attempt didn't use a network port. What I am looking for is a pointer to a general troubleshooting process. If everybody who is having problems sends a message to a mailing list - well, that doesn't scale very well. Thank you Jeff -- *Jeff Silverman* Systems Engineer (253) 459-2318 (c)
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
