Bug #18033 IM: Server_ID not reported

Description:
Release build of 5.0.19

-------------------------------------------------------
*** r/im_utils.result
--- r/im_utils.reject
***************
*** 16,22
  language      VALUE
  character-sets-dir    VALUE
  basedir       VALUE
- server_id     VALUE
  skip-stack-trace      VALUE
  skip-innodb   VALUE
  skip-bdb      VALUE
--- 16,21
***************
*** 36,42
  language      VALUE
  character-sets-dir    VALUE
  basedir       VALUE
- server_id     VALUE
  skip-stack-trace      VALUE
  skip-innodb   VALUE
  skip-bdb      VALUE
--- 35,40
-------------------------------------------------------

cane-5.0-max.log   normal
hp3750-5.0-standard.log   normal
hpita2-64bit-5.0-debug.log   normal
hpita2-64bit-5.0-pro-gpl.log   normal

In 5.0.15, 5.0.16, 5.0.18, and 5.1.6, there were similar failures on SCO (not reported),
in a 5.0.19 test build, it occurred on RHAS3(x86).

How to repeat:
Test suite.

It seems the cause of the bug is the same as for BUG#14106.

This bug is expected to be fixed by a patch for BUG#14106.
Please, re-verify it again.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Sorry for the delay - we did not manage to report all test failures in between.

Bad news: The bug still occurs in 5.0.24 (also in 20, 21, 22, and 23).

The sources for 5.0.24 do contain two patches for bug#14106.

A patch for this bug:
http://lists.mysql.com/commits/10998

See BUG#21331 for more info.

Merged into 5.0 tree, currently tagged 5.0.25;
merged into 5.1 tree, currently tagged 5.1.12-beta.

Test suite change. No changelog entry needed.