Back to bug 1400139
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Scott Dodson | 2016-11-30 14:51:21 UTC | Keywords | UpcomingRelease | |
| Scott Dodson | 2016-12-01 20:07:10 UTC | Depends On | 1400686 | |
| Scott Dodson | 2016-12-01 20:11:59 UTC | Status | NEW | MODIFIED |
| errata-xmlrpc | 2016-12-01 20:13:32 UTC | Status | MODIFIED | ON_QA |
| Johnny Liu | 2016-12-06 08:27:43 UTC | Status | ON_QA | VERIFIED |
| Scott Dodson | 2016-12-07 16:22:20 UTC | Doc Text | Previously the dnsmasq configuration included "strict-order" which meant that dnsmasq would iterate through the host's nameservers in order. This meant that if the first nameserver had failed a lengthy timeout is observed while dnsmasq waits before moving on to the next nameserver. By removing the strict-order option dnsmasq will prefer nameservers that it knows to be up over those which are unresponsive ensuring faster name resolution. If you wish add this or any other option please use the advanced installer option 'openshift_node_dnsmasq_additional_config_file' which allows you to provide the path to a dnsmasq configuration file that will be deployed on all nodes. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Dan McPherson | 2016-12-09 19:49:31 UTC | Keywords | UpcomingRelease | |
| Dan McPherson | 2017-01-22 01:56:56 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2017-01-21 20:56:56 UTC | |||
| Dan McPherson | 2017-01-23 09:50:24 UTC | Status | CLOSED | ON_QA |
| Resolution | CURRENTRELEASE | --- | ||
| Keywords | Reopened | |||
| Dan McPherson | 2017-01-23 09:57:05 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2017-01-24 18:14:51 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-01-24 21:09:41 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-01-21 20:56:56 UTC | 2017-01-24 16:09:41 UTC |
Back to bug 1400139