Thanks Marios, same thoughts from my side. Let's see how the CI goes (and if future failures will be related to this issue), then we can move it to invalid since I think it's not a real tripleo bug.
Thanks Marios, same thoughts from my side.
Let's see how the CI goes (and if future failures will be related to this issue), then we can move it to invalid since I think it's not a real tripleo bug.