install phase seems to be working as expected:
http://artifacts.dev.testing-farm.io/cf11435c-92bf-49e1-a0a4-b2ee3aaece08/work-installabilityVc6S8Q/installability/execute/data/install/output.txt

but all subsequent stages then error because of the ssh connection error to the machine:
http://artifacts.dev.testing-farm.io/cf11435c-92bf-49e1-a0a4-b2ee3aaece08/work-installabilityVc6S8Q/installability/execute/data/remove/output.txt

So I suspect one of the subpackages (workstation?) is turning on firewall or something, and thus the worker cannot connect to the machine and run other tests:
http://artifacts.dev.testing-farm.io/cf11435c-92bf-49e1-a0a4-b2ee3aaece08/work-installabilityVc6S8Q/installability/execute/data/remove/output.txt

Assuming that each test is a separate ssh connection (?) or not? @mvadkert

Maybe we could add some "--fix-ssh" option to installability that would make sure that the machine is still accessible after the test.

@mvadkert I also see that there is a xunit that points to the pre/post artifact installation logs. Nice;) This will make debugging easier for people. Not sure why it was not processed by Jenkins though.

In cases like these, when one test actually passed and others errored, would it be possible to add those results to the xunit as well?

@msrb

Assuming that each test is a separate ssh connection (?) or not? @mvadkert

It should be yeah, each test runs in its own ssh connection ...

@msrb I believe we agreed here to move to testing-farm dashboard later, so parsing via jenkins xunit is not needed. Our xunit-viewer actually has custom code to show this stuff