I've looked on the one failed test, because it plays with netconfig task by adding an expected fail to its puppet. And I found that test failed on the next step, when we're re-deploying cluster with correct task:
[root@nailgun ~]# cat /etc/puppet/modules/osnailyfacter/modular/netconfig/connectivity_tests.pp
include ::osnailyfacter::netconfig::connectivity_tests
As you can see there is no fail emulation at the output.
So, this bug is not on QA side, something wrong with connectivity tests.
I've looked on the one failed test, because it plays with netconfig task by adding an expected fail to its puppet. And I found that test failed on the next step, when we're re-deploying cluster with correct task: modules/ osnailyfacter/ modular/ netconfig/ connectivity_ tests.pp ::netconfig: :connectivity_ tests
[root@nailgun ~]# cat /etc/puppet/
include ::osnailyfacter
As you can see there is no fail emulation at the output.
So, this bug is not on QA side, something wrong with connectivity tests.