- Release Notes >
- Automation Agent Changelog
Automation Agent Changelog¶
Automation Agent 2.5.22.1876
¶
Released with Ops Manager 2.0.7 on 2016-11-03
- MongoDB data and log files will have a
umask
of027
. Requires new package install.
Automation Agent 2.5.20.1755
¶
Released with Ops Manager 2.0.6 on 2016-08-18
- Improve logging on authentication failures.
- Fixed setting clusterAuthMode on sharded clusters.
Automation Agent 2.5.19.1732
¶
Released with Ops Manager 2.0.5 on 2016-07-14
- Substantial optimization in state-gathering.
- Configurable timeout for connections to MongoDB processes.
- Fixed problem verifying success when creating text indexes in rolling index builds.
Automation Agent 2.5.18.1647
¶
Released with Ops Manager 2.0.4 on 2016-05-20
- Agent no longer downloads restore data for arbiters.
- Fixed some cases where CSRS conversion could get stuck.
- Fixed agent unable to restart a config server if all config servers were down.
- Fixed issue validating MongoDB versions when a cluster was on mixed operating systems.
Automation Agent 2.5.17.1604
¶
Released with Ops Manager 2.0.3 on 2016-03-24
- Fixed import of arbiter using a different keyfile then existing configuration.
- Allow specifying a temporary port for use during a CRSR upgrade.
Automation Agent 2.5.16.1552
¶
Released with Ops Manager 2.0.2 on 2016-03-01
- Added support for managing MongoDB on SUSE12.
- Added support for rolling upgrades to config servers as a replica set. See Convert Config Servers to a Replica Set.
Automation Agent 2.5.15.1526
¶
Released with Ops Manager 2.0.1 on 2016-01-21
- Stability and performance improvements for restores via automation.
- Added optimization to prioritize replica set reconfiguration actions over index builds.
- Improved index building mechanism: index builds are no longer performed in a rolling fashion for 2-node replica sets, but instead are built in the background.
- Added optimization to not compare unsupported index options when determining whether or not an index already exists.
- Fixed issue with importing existing deployments that include arbiters running with authentication.
- Fixed issue with rolling storage engine conversion for replica sets to ensure a super majority is always up.
- Fixed issue with creating custom roles on sharded clusters running MongoDB 3.2 with config server replica sets.
Automation Agent 2.5.11.1484
¶
Released with Ops Manager 2.0.0 on 2015-12-08
- Added aupport for MongoDB 3.2.0 clusters with config servers as replica sets.
- Added aupport for automated restores via the Automation Agent.
- Added aupport for rolling index builds.
- Added aupport for configuring WiredTiger encrypted storage for MongoDB 3.2.
- Added aupport for rolling conversion to X-509 member authentication.
- Improved handling of sharded clusters with members running on both Linux and Windows-based operating systems.
- Added optimization when starting a new Monitoring or Backup Agent to ensure that the process is running before achieving Goal State.
- Fixed
glibc
incompatibility issue on RHEL5 and RHEL6. - Fixed bug where failed Automation Agent automatic updates can cause surge in configuration calls from the Automation Agent.
Automation Agent 2.0.14.1398
¶
Released with Ops Manager 1.8.2 on 2015-10-20
- Fixed Agent from not recognizing RHEL Workstations as RHEL.
Automation Agent 2.0.12.1238
¶
Released with Ops Manager 1.8.1 on 2015-08-17
- Fixed managing an existing deploy with user that has “root” privileges.
- Fixed case where storage engine conversions could get stuck if replica set contained an arbiter.
- Fixed updating credentials after failed attempt to manage an existing deployment.
Automation Agent 2.0.9.1201
¶
Released with Ops Manager 1.8 on 2015-06-23
- Added support for managing SSL-enabled deployments.
- Added support for managing deployment using Kerberos, LDAP, and x.509 Client Certificate authentication.
- Added support to import an existing mongos with a config file.
- Added support for importing an existing deployment that contains authenticated arbiters on which the hostname does not resolve locally to the loopback interface.
- Added the ability to upgrade the
authSchemaVersion
when auth is not enabled. - Added support to change the storage engine for replica sets with more than one data node.
- Enabled storage engine conversions for single-node replica sets and standalones.
- Added more detailed logging of when MongoDB, the Monitoring Agent, or the Backup Agent rotate their logs.
- Added support for distribution-specific MongoDB Community Edition builds.
- Added up-front validation to ensure that MongoDB processes are running as the same user as the Automation Agent.
- Added functionality to delete MongoDB binaries on disk that are not used by a managed process.
- Added optimization where Ops Manager assumes success when starting a forked MongoDB process, rather than waiting for EOF.
- Improved algorithm for balancing mongod processes across cores.
- When deleting directories, symlinks are no longer deleted.
- Fixed issue importing credentials for
MONGODB-CR
users fromSCRAM-SHA-1
deployments. See: MMS-2612 for more details. - Fixed issue with deriving the default port for config servers
started with the
--configsvr
option but with no port specified. See: MMS-2489. - Fixed issue with configuring oplog sizes greater than 1TB.
- Fixed issue where the Automation Agent interfered with manually-created replica set tags.
- Ensured that the Automation Agent fails gracefully when an expected user does not exist during an initial import.
Automation Agent 1.4.18.1199-1
¶
Released with Ops Manager 1.6.3 on 2015-06-23
- Added support for importing an existing deployment that contains authenticated arbiters on which the hostname does not resolve locally to the loopback interface.
- Fixed logic used for performing a rolling restart.
- Fixed issue with deriving the default port for config servers
started with the
--configsvr
option but with no port specified. See: MMS-2489.
Automation Agent 1.4.16.1075
¶
Released 2015-04-28
- Fixed an issue with updating users created on MongoDB 2.4.
- Fixed an issue with config server repair that occurred if the third config server was out of sync.
Automation Agent 1.4.15.999
¶
Released 2015-03-26
- Fixed a rare edge-case that prevented the Automation Agent from successfully enabling authentication.