Description of problem: Restraint doesn't work after reboot. See this recipe: https://beaker.engineering.redhat.com/recipes/8217169#task109920760 The net-snmp task reboots the system but restraint doesn't pick up after the boot. Last few lines from console log: Red Hat Enterprise Linux Server 7.7 (Maipo) Kernel 3.10.0-1062.21.1.el7.x86_64 on an x86_64 kvm-05-guest12 login: [ 16.862880] traps: restraintd[1548] trap int3 ip:5fcdf1 sp:7ffc46091410 error:0 in restraintd[400000+6da000] [ 20.954802] random: crng init done [-- MARK -- Wed May 6 16:10:00 2020] [-- MARK -- Wed May 6 16:15:00 2020] [-- MARK -- Wed May 6 16:20:00 2020] [-- MARK -- Wed May 6 16:25:00 2020] [-- MARK -- Wed May 6 16:30:00 2020] Version: ---> Package restraint.x86_64 0:0.2.0-1.el7bkr will be installed
Restraint is failing to start when IPv6 is disabled, as the test requires, > Unnecessary error messages are reported by the snmpd when IPv6 is disabled. This was already reported in https://bugzilla.redhat.com/show_bug.cgi?id=1825548 It was fixed in https://github.com/beaker-project/restraint/issues/42 Using restraint-rhts-0.1.45 for harness in ksmeta should work, as the issue was introduced in 0.2.0.
When I reproduced this issue, I saw the following error in the journal log. restraintd[1765]: Unable to listen on either ipV4 or ipV6 protocols, exiting... Pinged Daniel as I believed he may had run into this error in earlier triage sessions. The above comment from Daniel was his response. *** This bug has been marked as a duplicate of bug 1825548 ***
When running same job with BZ1825548, Job ran to completion.