[SERVER-11170] ipv6_connection_string_validation.js failing on MCI Linux 64-bit Created: 14/Oct/13  Updated: 11/Jul/16  Resolved: 15/Oct/13

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.5.3

Type: Bug Priority: Major - P3
Reporter: Matt Kangas Assignee: Ernie Hershey
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

ae9897079d21 Linux 64-bit slow_nightly_tests
http://buildlogs.mongodb.org/mci_0.9_linux_64/builds/1367/test/slow_nightly_tests_1/ipv6_connection_string_validation.js

2013-10-14T03:05:05.735+0000 shell: started program /data/mci/git@github.commongodb/mongo.git/master/mongod --port 31000 --ipv6 --dbpath /data/db/jstests_slowNightly_ipv6_connection_string_validation --setParameter enableTestCommands=1
 m31000| 2013-10-14T03:05:05.774+0000 [initandlisten] MongoDB starting : pid=13983 port=31000 dbpath=/data/db/jstests_slowNightly_ipv6_connection_string_validation 64-bit host=ip-10-149-20-90
...
 m31000| 2013-10-14T03:05:06.247+0000 [initandlisten] Assertion: 15863:listen(): invalid socket? errno:97 Address family not supported by protocol

Last green at 6a70c219c629 committed Fri Oct 11.

Hard to tell whose this is. I cannot repro on Ubuntu 12.04.

Shaun?



 Comments   
Comment by auto [ 15/Oct/13 ]

Author:

{u'username': u'ehershey', u'name': u'Ernie Hershey', u'email': u'ernie.hershey@10gen.com'}

Message: SERVER-11170 don't disable ipv6 on linux-64 ec2 build hosts
Branch: master
https://github.com/10gen/mci/commit/d50f5cb818670176fca07dcc43edbd1878420c3e

Comment by Shaun Verch [ 14/Oct/13 ]

Yeah, it seems like ipv6 is not supported (this was run using the spawn script with linux-64 as the distro):

[root@ip-10-149-2-34 mongo]# cat /proc/net/if_inet6
cat: /proc/net/if_inet6: No such file or directory
[root@ip-10-149-2-34 mongo]# modprobe ipv6
[root@ip-10-149-2-34 mongo]# cat /proc/net/if_inet6
cat: /proc/net/if_inet6: No such file or directory
[root@ip-10-149-2-34 mongo]# lsmod | grep ipv6
[root@ip-10-149-2-34 mongo]# ping6 -c2 ::1
socket: Address family not supported by protocol

Comment by Matt Kangas [ 14/Oct/13 ]

I'm thinking this is an MCI configuration issue, not a code issue. Example:

Failed on 3f2c4c4afd01 Linux 64-bit DUR OFF slow_nightly_tests, host ec2-107-22-12-158.compute-1.amazonaws.com
Success on ae9897079d21 Linux 64-bit DUR OFF slow_nightly_tests, host mci-exec@build.nj1.10gen.cc:2218

These commits are immediately adjacent. So I'm thinking failure is correlated on the host, not the commit. Also note the failure message:

Assertion: 15863:listen(): invalid socket? errno:97 Address family not supported by protocol

Perhaps (some) EC2 MCI boxes are running without an IPv6 stack enabled, but the nj1 boxes are?

ian@10gen.com - convert this to an MCI ticket?

Comment by Shaun Verch [ 14/Oct/13 ]

This is the first commit where the test failure is "uncovered": https://github.com/mongodb/mongo/commit/ae9897079d2139bb451d2c2183bfe4a96f879899

http://mci.10gen.com/ui/task/mongodb_mongo_master_linux_64_ae9897079d2139bb451d2c2183bfe4a96f879899_13_10_14_01_37_06_slow_nightly_tests_linux_64

Comment by Shaun Verch [ 14/Oct/13 ]

I don't think anything I did since then could cause this, but I'll try to reproduce it.

Changed mongobridge only, and this test doesn't use the "bridge()" jstest helper in replsettest.js:
https://github.com/mongodb/mongo/commit/a428f58a6fd4f9497b60b10fa749e5cf2eec7b7c

Changed the appendSetParametersArgs helper in servers.js. This seems like the only thing that could affect this, but I'm not sure how it would break anything. Basically it just makes sure that the argument is a string type before trying to call "indexOf".
https://github.com/mongodb/mongo/commit/db089e849ad5a67dfb5d26c697f83205d2363c0f

Changed time_support_test.cpp only:
https://github.com/mongodb/mongo/commit/c1a09966ff05c42c184870715e7a7383d02c477d

(I have another commit there, but I reverted it so these are the only three in since then)

Generated at Thu Feb 08 03:25:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.