Fixes #18549 - Don't rebuild already correct DNS entries #4297
Conversation
If we do so and try to recreate them right away ecreate_dns_record might still see a valid entry due to zone transfer slowness or other caching issues. In this case we'd end up without a DNS entry after all. So intead do nothing if the entry is already good. Signed-off-by: Guido Günther <agx@sigxcpu.org>
|
@agx, thanks for your PR! By analyzing the history of the files in this pull request, we identified @ohadlevy, @isratrade and @timogoebel to be potential reviewers. |
| @@ -42,7 +42,7 @@ def rebuild_dns | |||
| results = {} | |||
|
|
|||
| DnsInterface::RECORD_TYPES.each do |record_type| | |||
| del_dns_record_safe(record_type) | |||
| dns_record(record_type).nil? || dns_record(record_type).valid? || del_dns_record_safe(record_type) | |||
There was a problem hiding this comment.
The first check for .nil? is already done on del_dns_record_safe on app/model/concerns/dns_interface.rb.
Could you move the .valid? check to that method, and add a test on test/models/orchestration/dns_test.rb for rebuild_dns with an already correct DNS record?
There was a problem hiding this comment.
@dLobatog wouldn't that obfuscate the meaning of del_dns_record_safe? It'd rather add a del_incorrect_dns_record
|
Thank you for your contribution, @agx! This PR has been inactive for 6 months, closing for now. |
If we do so and try to recreate them right away ecreate_dns_record might
still see a valid entry due to zone transfer slowness or other caching
issues. In this case we'd end up without a DNS entry after all. So
intead do nothing if the entry is already good.
This is a forward port from a fix I applied to a local 1.10.x instance.
Signed-off-by: Guido Günther agx@sigxcpu.org