Kubernetes Control M Agent example doesn't work with EM 9.20.0

[controlm]

Kubernetes Control M Agent example doesn't work with EM 9.20.0

[codytrey]

It looks like you don't have the Agent install media on the EM in the AUTO_DEPLOY directory. The following section of a similar example details the steps you need to follow:
https://github.com/controlm/automation-api-community-solutions/blob/master/3-infrastructure-as-code-examples/scaling-control-m-agent-host-group-with-a-dynamic-workload/deploy.md#control-menterprise-manager-setup

[codytrey]

@anshul07 I'm going to go ahead close. If you're still having issues with this I'd recommend opening a case directly with BMC Support

[maryplaya]

In "RUN ctm provision image Agent.Linux" I guess there is still the old agent-version mentioned, which results that it wants to install: DRKAI.9.0.00_Linux-x86_64.tar.Z
DRKAI.9.0.00 is Control-M Agent Version 9.0.00 which is very old.

In /usr/app/ctmem/ctm_em/etc/emweb/automation-api/downloads/descriptors you need to have the json file with the correct version:
cat Agent_20.Linux.json
{
"OS": "Linux-x86_64",
"Installers":
[
"DRKAI.9.0.20.100_Linux-x86_64.tar.Z"
]
}

And then you need to have the DRKAI.9.0.20.100_Linux-x86_64.tar.Z in /usr/app/ctmem/ctm_em/AUTO_DEPLOY/.

Same works also with older version 9.0.19.200 and lower, but you need to have the correct json and SW in place.

[JoeGoldberg]

The action described by maryplaya will bypass the problem. But in my opinion, the "Agent." image, without a specific version qualifier, should point to the current version of the agent that matches the version of the Enterprise Manager. If that view is accepted, the correction for this issue requires a change on the Enterprise Manager side to make the Agent.Linux image in the Enterprise manager to point to 9.0.20 and for that image to also be provided in the AUTO_DEPLY directory.