Oyvind Albrigtsen

We havent found a way to get our system in 'Error' state yet, so if you know a way to do that that would be great.

They are still supported, and available in the resource-agents-cloud subpackage.

Can you send us the output of the following 2 commands from all your nodes? ``` dpkg -l | grep fence-agents dpkg -l | grep multipath-tools ```

No. We have not been able to reproduce the issue even with newer versions than you've listed, so maybe we'll have to make a parameter to be able to choose...

Can you try updating the if() to `if instance_status == "Running" or instance_status == "Failed":` to see if that works?

You might have to add a `logger.info()` in `get_power_status()` if it's not working out of the box. I just guessed that "Failed" is the result it returns.

Is there still a virt-launcher Pod for the failed VMI?

We're not able to get the status of storage LAN via the API currently, so I'm in discussions with some Openshift devs to consider adding it.

The agent tries to report what has most likely happened with error code and a message: https://github.com/ClusterLabs/fence-agents/blob/main/lib/fencing.py.py#L579 Which is why it's always a good idea to check the logs to...

You have to run `make xml-upload` and attach the updated test metadata to avoid CI failing.