Hide Forgot
Description of problem: restraint can't start when ipv6 is disabled Version-Release number of selected component (if applicable): beaker-26.2 restraint-0.1.36-1.git.2.4e1c859.el8 How reproducible: Always Steps to Reproduce: 1. disable ipv6 and reboot Actual results: restraint fail to start Expected results: restraint can start Additional info: as following job shows: https://beaker.engineering.redhat.com/jobs/3268809 systemctl status restraintd ● restraintd.service - The restraint harness. Loaded: loaded (/usr/lib/systemd/system/restraintd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2019-01-03 03:43:39 EST; 4min 2s ago Main PID: 14875 (code=exited, status=1/FAILURE)
*** Bug 1663460 has been marked as a duplicate of this bug. ***
on the console you will see the following message: restraintd[1757]: Unable to bind to server port 8081
(In reply to Bill Peck from comment #2) > on the console you will see the following message: > restraintd[1757]: Unable to bind to server port 8081 I also noticed the error, the reason why I created the bug is that I want to know how can restraint start with ipv6 disabled
I wasn't discounting the bug, just providing more info about when it's seen.
Hi Bill, As we QE are required to run tests with ipv6 disabled. is there any work around before the next release is ready? if not, when will the next release become ready? we are in snapshot 4 of RHEL8, it's better to get it ready before rhel8 RC.
Hello Jianlin, I will try to answer your questions. 1. As far as I know, due to the implementation of Restraint, it is not possible to make a workaround for the current situation (0.1.36) 2. I'm starting preparation for the new release of Restraint today. Hopefully, we will be able to ship it today/next week when everything will be settled after the outage.
(In reply to Martin Styk from comment #6) > Hello Jianlin, > > I will try to answer your questions. > 1. As far as I know, due to the implementation of Restraint, it is not > possible to make a workaround for the current situation (0.1.36) > 2. I'm starting preparation for the new release of Restraint today. > Hopefully, we will be able to ship it today/next week when everything will > be settled after the outage. That's great, so we can use the new release in rhel8 RC testing. please update here after the new release is shipped, thanks
Restraint 0.1.37 has been released.