Red Hat Bugzilla – Bug 1617976
Node service will also be stopped when dnsmasq is stopped on atomic host env
Last modified: 2018-10-11 03:25:45 EDT
Description of problem: this issue only happen on atomic host env, when stop dnsmasq service on node. the node service also be stopped. Version-Release number of selected component (if applicable): v3.11.0-0.16.0 How reproducible: alwyas Steps to Reproduce: 1. systemctl status dnsmasq atomic-openshift-node | grep active 2. systemctl stop dnsmasq 3. systemctl status dnsmasq atomic-openshift-node | grep active Actual results: step 3: systemctl status dnsmasq atomic-openshift-node | grep active Active: inactive (dead) since Thu 2018-08-16 08:19:23 UTC; 2s ago Active: inactive (dead) since Thu 2018-08-16 08:19:23 UTC; 2s ago Expected results: node service should not be stopped when dnsmasq stopped. Additional info: it works well on RHEL installed env the before bug https://bugzilla.redhat.com/show_bug.cgi?id=1532960
Can you please give me more information about the test environment, how it was created, how I can reproduce, etc.? Thanks!
Dan, Ok, since this is Atomic Host, this is a system container so the service is defined in the image. https://github.com/openshift/origin/blob/master/images/node/system-container/service.template#L4
Verified this bug on oc v3.11.0-0.22.0, the issue has been fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652