Comment 7 for bug 1855985

I've seen the list_agent failure before. It looks like a race condition in the tempest test itself since the test immediately stores the agent state on the class via a list() and calls list again later and makes sure that the first agent in the list (and it's fields) is in the list of fields returned later. If the agent alive status happens to be False when the class is initialized, then becomes alive at some point later, then the test will fail. I have also seen it fail because one test updates the description on the agent and cleans up after itself, but the list_agent test runs in between.