Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin busybox version for nslookup #8157

Merged
merged 1 commit into from
Jul 26, 2018

Conversation

hickeng
Copy link
Member

@hickeng hickeng commented Jul 26, 2018

Busybox ping exhibited intermittent failures some time back so we had
switched to using the debian image for ping testing, however we are now
seeing intermittent failures in the busybox nslookup results as well.
This appears to be dependent on the order in which A and AAAA record query
results are returned as those queries appear to be issued in parallel.

The debian nslookup does not issue an AAAA query by default and does not
exhibit this problem however is not available in the base image. As such we've
pinned the busybox version to 1.28.4 until the bug is fixed.
See docker-library/busybox#48

Also updates all images used in the test to use the image variable rather than
hardcoded names so we use the local mirrors if configured.

[specific ci=1-24-Docker-Link]

@hickeng hickeng requested a review from a team as a code owner July 26, 2018 20:55
@hickeng hickeng force-pushed the busybox-nslookup-link-alias branch from 05359c1 to d8935be Compare July 26, 2018 20:56
Busybox ping exhibited intermittent failures some time back so we had
switched to using the debian image for ping testing, however in the recent
past we are now seeing intermittent failures in the busybox nslookup
results as well.

This appears to be dependent on the order in which A and AAAA record query
results are returned as those queries appear to be issued in parallel.
The debian nslookup does not issue an AAAA query by default and does not
exhibit this problem however nslookup is also not available in the base
image. As such we're pinning the busybox version to one with a functioning
nslookup until https://bugs.busybox.net/show_bug.cgi?id=11161 is
addressed.
@hickeng hickeng force-pushed the busybox-nslookup-link-alias branch from d8935be to b5919ac Compare July 26, 2018 21:27
@hickeng hickeng changed the title Use debian for nslookup and ping utilities Pin busybox version for nslookup Jul 26, 2018
@hickeng hickeng merged commit 24af8e8 into vmware:master Jul 26, 2018
zjs pushed a commit to zjs/vic that referenced this pull request Jul 27, 2018
Busybox ping exhibited intermittent failures some time back so we had
switched to using the debian image for ping testing, however in the recent
past we are now seeing intermittent failures in the busybox nslookup
results as well.

This appears to be dependent on the order in which A and AAAA record query
results are returned as those queries appear to be issued in parallel.
The debian nslookup does not issue an AAAA query by default and does not
exhibit this problem however nslookup is also not available in the base
image. As such we're pinning the busybox version to one with a functioning
nslookup until https://bugs.busybox.net/show_bug.cgi?id=11161 is
addressed.

(cherry picked from commit 24af8e8)
zjs added a commit that referenced this pull request Jul 27, 2018
Busybox ping exhibited intermittent failures some time back so we had
switched to using the debian image for ping testing, however in the recent
past we are now seeing intermittent failures in the busybox nslookup
results as well.

This appears to be dependent on the order in which A and AAAA record query
results are returned as those queries appear to be issued in parallel.
The debian nslookup does not issue an AAAA query by default and does not
exhibit this problem however nslookup is also not available in the base
image. As such we're pinning the busybox version to one with a functioning
nslookup until https://bugs.busybox.net/show_bug.cgi?id=11161 is
addressed.

(cherry picked from commit 24af8e8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants