Skip to content
This repository has been archived by the owner on May 8, 2021. It is now read-only.

PLAT-139 Use OpsManager version 3.4 instead of 2.0 #7

Merged
merged 2 commits into from
Jun 8, 2017

Conversation

exAspArk
Copy link
Contributor

@exAspArk exAspArk commented Jun 6, 2017

No description provided.

@exAspArk exAspArk force-pushed the PLAT-139_bump_opsmanager_version branch from 7bb5c43 to 1490889 Compare June 6, 2017 16:03
@exAspArk exAspArk merged commit 4151706 into master Jun 8, 2017
@exAspArk exAspArk deleted the PLAT-139_bump_opsmanager_version branch June 8, 2017 15:50
@@ -179,8 +179,8 @@ fi
# Automation Agent (requires OpsManager available)
#
if [ "${role_node}" == "true" ]; then
curl -k -OL http://${opsmanager_subdomain}:8080/download/agent/automation/mongodb-mms-automation-agent-manager_2.5.16.1552-1_amd64.deb
DEBIAN_FRONTEND=noninteractive dpkg --install mongodb-mms-automation-agent-manager_2.5.16.1552-1_amd64.deb
curl -k -OL http://${opsmanager_subdomain}:8080/download/agent/automation/mongodb-mms-automation-agent-manager_3.2.12.2107-1_amd64.deb
Copy link
Contributor Author

@exAspArk exAspArk Jun 8, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@adammeghji I re-terraformed all opsmanager nodes with these changes.

But role_node is enabled for mongodb data nodes, I updated the mongodb-mms-automation-agent-manager package manually on each staging / production mongodb node for now. It was faster, safer and easier than terraforming each node one by one (I'm sure it'll work too though).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant