Fuel 4.0 ostf platform_tests: "Time limit exceeded" even when "Currently in CREATE_FAILED status"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Yuriy Yekovenko |
Bug Description
fuel-4.0 134 iso
{"release": "4.0", "nailgun_sha": "66119c3f501014
Problem:
[platform_tests] Create stack, check its details, then update and delete Heat stack
Status: failure
Message: Time limit exceeded while waiting for stack status becoming 'CREATE_COMPLETE' to finish. Please refer to OpenStack logs for more details.
Platform health check works for 100 seconds and gives "Time limit exceeded" even when it gets CREATE_FAILED status.
Example from ostf-stdout.log:
fuel_health.
fuel_health.test: DEBUG: Sleeping for 10 seconds
Snapshot attached.
Changed in fuel: | |
importance: | Undecided → Critical |
assignee: | nobody → Yuriy Yekovenko (yyekovenko) |
Changed in fuel: | |
status: | New → In Progress |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
Lowering priority to High. I want to avoid to many criticals - I believe if just one of OSTF tests fails because of the issue in test, then it should not be critical.
If whole OSTF framework doesn't work - it is critical. Or if deployment fails in one of the modes.