MySQL Bugs: #76832: The resukts from dryrun are not in the log file

Bug #76832	The resukts from dryrun are not in the log file
Submitted:	24 Apr 2015 17:59	Modified:	22 Feb 2016 17:31
Reporter:	Andrew Morgan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster Manager: Documentation	Severity:	S3 (Non-critical)
Version:	1.3.4	OS:	Any
Assigned to:	Daniel So	CPU Architecture:	Any

Description:
The documentation at http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-using-import-cluster-create-conf... indicates that the proposed config changes are written to MCM's log file whereas in fact the log file just contains the name/location of a file that contains the proposed confif changes.

How to repeat:
Run the example and check the log file

Suggested fix:
Update doc

Either the behaviour changed, or this feature was not implemented according to spec provided to Docs team. Please determine which occurred, and if so, when this happened.

Thanks.

This is a duplicate of Bug# 22280689 on the Oracle bug system, and the issue has already been fixed. This is the entry for the fix in the changelog for MySQL Cluster Manager 1.4.1 (forthcoming).

"The success messages returned by the autotune --dryrun and import config
--dryrun commands referred users to the agent log file for the proposed
settings to be applied to the cluster, but the settings were not actually in
the file. The success messages now give the path to the .mcm script file that
contains the settings."