### Description of problem ### Customer have made some local changes to be used by the pods in resolv.conf and added "options timeout:2" since the default timeout of 5 seconds is not suitable for them. This addition however is not added to pods as they are created. ### Version-Release number ### openshift-ansible-3.7.42-1.git.2.9ee4e71.el7.noarch ### Steps to Reproduce: ### 1. cat /etc/resolv.conf > /etc/origin/node/resolv.new.conf 2. echo "options timeout:2" >> /etc/origin/node/resolv.new.conf 3. - name: Update /etc/origin/node/node-config.yaml. insertafter: '^kubeletArguments:' resolv-conf: - '/etc/origin/node/resolv.new.conf' 4. systemctl restart atomic-openshift-node 5. Start pod on node 6. oc rsh <pod_name> 7. In pod: cat /etc/resolv.conf * Actual results: Is not working. * Expected results: The pod should contain "options timeout:2"
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.