Hide Forgot
Description of problem: The first test in oo-diagnostics checks that the first DNS server in /etc/resolv.conf is working properly. It checks for an NXDOMAIN response on a bogus domain. There are other valid responses that would not indicate a problem. For now it seems best to just validate that the server responds at all. Steps to Reproduce: 1. Install an OSE system including BIND 2. Reconfigure BIND /etc/named.conf with "recursion no;" instead of "yes". 3. Run oo-diagnostics Actual results: Fails because server returns "REFUSED", not "NXDOMAIN". Expected results: Test should pass. Additional info: Other servers could also respond with other valid codes. The best we can do in the general case is test that the server is at least responding, as the server being down or unreachable is the most common cause of problems. We could do better validating the actual app domain on brokers or nodes, but save that for a later update.
origin-server: commit e3e29eb1e9b40d275b0d4a6bd78544416f741c73 Author: Luke Meyer <lmeyer> Date: Fri Nov 22 11:34:08 2013 -0500 <oo-diagnostics> loosen DNS test - bug 1033701 enterprise-1.2.z: commit c2b71ca01ebb6eb0839b83f8fceb6e73b679918b enterprise-2.0: commit 90b1a61113635e4e8fa1db667ac039228b048092
Verify this bug on rubygem-openshift-origin-common-1.17.2.2-1.el6op.noarch. After configuring /etc/named.conf with "recursion no", run "oo-diagnostics" . No error was thrown out.