Bug #25656 Upgrade of enterprise binaries started database

Description:
When we upgraded the binaries with the rhel enterprise rpm (5.0.32) we saw, that the rpm started and stopped the database.
this is definitely NOT what i want on a production system.

How to repeat:
070116 17:34:11 [Note] /data01/home/mysql/oli/mysql-5.0.32/bin/mysqld: Normal shutdown

070116 17:34:11 [Note] Slave I/O thread killed while reading event
070116 17:34:11 [Note] Slave I/O thread exiting, read up to log 'prdusdbmaster01-bin.000043', position 431641489
070116 17:34:11 [Note] Error reading relay log event: slave SQL thread was killed
070116 17:34:11  InnoDB: Starting shutdown...
070116 17:34:17  InnoDB: Shutdown completed; log sequence number 3 2316012607
070116 17:34:17 [Note] /data01/home/mysql/oli/mysql-5.0.32/bin/mysqld: Shutdown complete

==> manual shutdown for upgrade
==> rpm -Uhv ...server...rpm

070116 17:38:57  InnoDB: Started; log sequence number 3 2316012607
070116 17:38:57 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.32-enterprise-gpl-log'  socket: '/var/lib/mysql/mysql.sock'  port: 23306  MySQL Enterprise Server (GPL)
070116 17:38:57 [Note] Slave SQL thread initialized, starting replication in log 'prdusdbmaster01-bin.000043' at position 431641489, relay log '/usr/local/mysql/data/prdusdbslave03-relay-bin.000379' position: 201747598
070116 17:38:57 [Note] Slave I/O thread: connected to master 'news_slave@10.33.54.236:23306',  replication started in log 'prdusdbmaster01-bin.000043' at position 431641489
070116 17:38:59 [Note] /usr/sbin/mysqld: Normal shutdown

070116 17:38:59 [Note] Slave I/O thread killed while reading event
070116 17:38:59 [Note] Slave I/O thread exiting, read up to log 'prdusdbmaster01-bin.000043', position 440045783
070116 17:38:59 [Note] Error reading relay log event: slave SQL thread was killed
070116 17:38:59  InnoDB: Starting shutdown...
070116 17:39:05  InnoDB: Shutdown completed; log sequence number 3 2318134086
070116 17:39:05 [Note] /usr/sbin/mysqld: Shutdown complete

Suggested fix:
stop that

Thank you for the report.

But for what you upgrade server and not use it?

Hi Sveta

I surly want to use the binaries. But I do NOT want that installer is doing anything else than installing binaries. NOT starting database (NOT starting just warning)...

Oli,

imagine what happens if running mysqld load reinstalled dynamic library? If case this dynamic library wasn't loaded before reinstallation?

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".

See also bug #27072 http://bugs.mysql.com/bug.php?id=27072

Seems these 2 bug reports are same.

So I mark this as duplicate of Verified one. If you not agree, just reopen the bug report.