MySQL Bugs: #60511: 5.5: Tests without ipv6 failing

Bug #60511	5.5: Tests without ipv6 failing
Submitted:	17 Mar 2011 12:50	Modified:	26 Apr 2012 18:59
Reporter:	Harald Reindl	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Tests	Severity:	S3 (Non-critical)
Version:	5.5.10	OS:	Linux (Fedora 13/14 x86_64)
Assigned to:		CPU Architecture:	Any

Description:
With MySQL 5.5 (x86_64) on Fedora with ipv6 totally disabled
and kernel-module unloaded there are some test failing

"Can't create IP socket: Address family not supported by protocol" sounds
for me like the tests are using ipv6 instead of be skipped
_______________

/bin/su -c 'cd /usr/share/mysql-test; ./mysql-test-run.pl --parallel=1 --max-test-fail=0 --skip-ndb --force' mysql

Completed: Failed 14/1617 tests, 99.13% were successful.
Failing test(s): 
* rpl.rpl_ip_mix 
* rpl.rpl_ip_mix2 
* rpl.rpl_ipv6 main.ipv6 
* main.mysql_locale_posix 
* main.mysqladmin 
* main.mysqlhotcopy_archive 
* main.mysqlhotcopy_myisam
_______________

rpl.rpl_ip_mix2 'stmt'                   w2 [ retry-fail ]
Test ended at 2011-03-17 12:28:45

Server log is:
110317 14:28:43 [Note] Plugin 'FEDERATED' is disabled.
110317 14:28:43 InnoDB: The InnoDB memory heap is disabled
110317 14:28:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110317 14:28:43 InnoDB: Compressed tables use zlib 1.2.3
110317 14:28:43 InnoDB: Using Linux native AIO
110317 14:28:43 InnoDB: Initializing buffer pool, size = 8.0M
110317 14:28:43 InnoDB: Completed initialization of buffer pool
110317 14:28:43 InnoDB: highest supported file format is Barracuda.
110317 14:28:43  InnoDB: Waiting for the background threads to start
110317 14:28:44 InnoDB: 1.1.5 started; log sequence number 1595675
110317 14:28:44 [Warning] /usr/libexec/mysqld: unknown variable 'loose-debug-sync-timeout=300'
110317 14:28:44 [ERROR] Can't create IP socket: Address family not supported by protocol
110317 14:28:44 [ERROR] Aborting

110317 14:28:44  InnoDB: Starting shutdown...
110317 14:28:45  InnoDB: Shutdown completed; log sequence number 1595675
110317 14:28:45 [Note] /usr/libexec/mysqld: Shutdown complete

How to repeat:
/bin/su -c 'cd /usr/share/mysql-test; ./mysql-test-run.pl --parallel=1 --max-test-fail=0 --skip-ndb --force' mysql

These tests (some of them at least, based on test name) are checking if IPV6 support in MySQL works properly. Why shouldn't they fail if IPV6 usage is disabled at OS level?

because myasld is multiple started explicitly with ipv6 and "110317 14:28:44 [ERROR] Can't create IP socket: Address family not supported by protocol
110317 14:28:44 [ERROR] Aborting" results in some hundret MB logfiles

another reason is that you are unable to run the test-suite without "--force" to run all the following tests

sorry but on an intranet-server nobody needs ipv6 the next 100 years and there are few setups out there using not 127.0.0.1 or unix-sockets and since it makes not sense crashing mysqld multiple the tests should be skipped if there is no ipv6 on os-level, with MySQL 5.0 the test-suite had no problem and did not write my filesystem full until make a seperate partition

This was fixed in latest versions: currently if no ipv6 support exists tests are just skipped, don't fail.

In 5.5.24 ipv6 based tests still fail, and it is unclear how this was "fixed", no explanation how this is detected