Failure to connect to registry.local due to DNS resolution issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Jerry Sun |
Bug Description
Brief Description
-----------------
With a DNS server that takes a long time to respond to unknown domains or hosts, registry.local fails to resolve and all interaction with the local registry like pushes, pulls, and even registry commands through sysinv will fail intermittently. As a result, application deployments will also fail.
Severity
--------
Major
Steps to Reproduce
------------------
Set up a system with a DNS server that takes a long time to respond to unknown domains or hosts (registry.local)
the issue is intermittent, and is a timing issue so reproducing it will be difficult
Expected Behavior
------------------
registry.local should still resolve and interaction with the registry like pushing, pulling, and querying images through sysinv should finish successfully
Actual Behavior
----------------
Interactions with the registry fails due to hostname resolution
Reproducibility
---------------
Intermittent, uncommon
System Configuration
-------
IPv6
Branch/Pull Time/Commit
-------
Master branch, 2020-11-19
Last Pass
---------
no
Workaround
----------
remove the problematic DNS server through system commands, then lock and unlock the hosts.
stx.5.0 / medium priority - intermittent issue with a workaround