Description of problem:
A 4.2 CI run failed with "Not all desired DNS DaemonSets available".
Version-Release number of selected component (if applicable):
Only seen once.
Current line of inquiry is investigating dns-default-cg574 which appears in the event log but not in the state dump.
message: 'Failed create pod sandbox: rpc error: code = Unknown desc = failed to
create pod network sandbox k8s_dns-default-cg574_openshift-dns_80dff9ab-975b-11e9-a1aa-0a349e682728_0(d64b9d47df6414e11f0ad4cbed67d6f216bc38d3aff6812670239fc22e20ec03):
netplugin failed but error parsing its diagnostic message "": unexpected end of
Lots of other SDN errors for the pods that do exist before they finally got created.
Still looking around, just wanted to communicate some notes.
dns-default-cg574 is stuck ContainerCreating.
Is our status reporting here correct? We're reporting degraded, which seems appropriate.
All evidence so far points to some transient SDN issue. If this is still happening, feel free to re-open against SDN.
New bug filed in bug 1751246. Marking this one as a dup of the new one so they have a structured Bugzilla connection ;)
*** This bug has been marked as a duplicate of bug 1751246 ***
This is definitely not a duplicate of the other bug - loopback is coredumping
Jun 25 15:12:12 ip-10-0-155-42 systemd-coredump: Process 2642 (loopback) of user 0 dumped core.
Stack trace of thread 2642:
#0 0x00007f61c09960d3 _dl_relocate_object (/usr/lib64/ld-2.28.so)
#1 0x00007f61c098e1af dl_main (/usr/lib64/ld-2.28.so)
#2 0x00007f61c09a3b00 _dl_sysdep_start (/usr/lib64/ld-2.28.so)
#3 0x00007f61c098c0f8 _dl_start (/usr/lib64/ld-2.28.so)
#4 0x00007f61c098b038 _start (/usr/lib64/ld-2.28.so)
It looks like another instance of https://bugzilla.redhat.com/show_bug.cgi?id=1725832
*** This bug has been marked as a duplicate of bug 1725832 ***