That's coming from mostly volume-related tests, so I think they are all related to the same thing, something is doing a blocking (on i/o?) call in cinder on the delete flow (or something using the same lock that gets into the delete flow, like a volume update periodic task maybe?) and we timeout.
It would be nice if that Tempest error message gave the type of resource in the error message rather than just 'failed to delete resource'. Then we could filter a bit better on the error message.
Looking at a logstash query like this:
message:"Failed to delete resource" AND message:"within the required time" AND tags:"console"
http:// logstash. openstack. org/#eyJzZWFyY2 giOiJtZXNzYWdlO lwiRmFpbGVkIHRv IGRlbGV0ZSByZXN vdXJjZVwiIEFORC BtZXNzYWdlOlwid 2l0aGluIHRoZSBy ZXF1aXJlZCB0aW1 lXCIgQU5EIHRhZ3 M6XCJjb25zb2xlX CIiLCJmaWVsZHMi OltdLCJvZmZzZXQ iOjAsInRpbWVmcm FtZSI6IjYwNDgwM CIsImdyYXBobW9k ZSI6ImNvdW50Iiw idGltZSI6eyJ1c2 VyX2ludGVydmFsI jowfSwic3RhbXAi OjE0MTMyMTkyOTU xMDgsIm1vZGUiOi IiLCJhbmFseXplX 2ZpZWxkIjoiIn0=
That's coming from mostly volume-related tests, so I think they are all related to the same thing, something is doing a blocking (on i/o?) call in cinder on the delete flow (or something using the same lock that gets into the delete flow, like a volume update periodic task maybe?) and we timeout.
It would be nice if that Tempest error message gave the type of resource in the error message rather than just 'failed to delete resource'. Then we could filter a bit better on the error message.