我正在尝试安装DevStack Mitaka:
在执行./stack.sh期间,n-cpu和q-l3服务无法启动。两个屏幕(n-cpu和q-l3)中的错误均显示以下内容:
CRITICAL nova [req-..] TypeError: 'Version object does not support
indexing
类似的问题被标记为已解决,但没有答案(n-cpu failure after running ./stack.sh)
这是错误日志:
+./stack.sh:main:1337 [[ -x /opt/stack/devstack/local.sh ]]
+./stack.sh:main:1346 service_check
+functions-common:service_check:1633 local service
+functions-common:service_check:1634 local failures
+functions-common:service_check:1635 SCREEN_NAME=stack
+functions-common:service_check:1636 SERVICE_DIR=/opt/stack
/status
+functions-common:service_check:1639 [[ ! -d /opt/stack/status
/stack ]]
++functions-common:service_check:1646 ls /opt/stack/status/stack
/n-cpu.failure /opt/stack/status/stack/q-l3.failure
+functions-common:service_check:1646 failures='/opt/stack/status/stack/n-cpu.failure
/opt/stack/status/stack/q-l3.failure'
+functions-common:service_check:1648 for service in '$failures'
++functions-common:service_check:1649 basename /opt/stack/status
/stack/n-cpu.failure
+functions-common:service_check:1649 service=n-cpu.failure
+functions-common:service_check:1650 service=n-cpu
+functions-common:service_check:1651 echo 'Error: Service n-cpu
is not running'
Error: Service n-cpu is not running
+functions-common:service_check:1648 for service in '$failures'
++functions-common:service_check:1649 basename /opt/stack/status
/stack/q-l3.failure
+functions-common:service_check:1649 service=q-l3.failure
+functions-common:service_check:1650 service=q-l3
+functions-common:service_check:1651 echo 'Error: Service q-l3
is not running'
Error: Service q-l3 is not running
+functions-common:service_check:1654 '[' -n '/opt/stack/status/stack/n-cpu.failure
/opt/stack/status/stack/q-l3.failure' ']'
+functions-common:service_check:1655 die 1655 'More details
about the above errors can be found with screen'
+functions-common:die:186 local exitcode=0
[Call Trace]
./stack.sh:1346:service_check
/opt/stack/devstack/functions-common:1655:die
[ERROR] /opt/stack/devstack/functions-common:1655 More details about the above errors can be found with screen
Error on exit
答案 0 :(得分:0)
有时有助于运行clean.sh并再次运行stack.sh。如果再次发现相同的错误,则需要挖掘日志并将错误发布到此处。