Choose of OneAgent Version on a Maintenance Windows

[opera_admin]

Hello Community

It would be great to choose the OneAgent version when creating an Update Maintenance Window, instead of the last version is forced.

[ChadTurner · Accepted solution]

You should be able to set that via the maintenance window scheduler and the OneAgent upgrade by selecting the standard version:

[gilles_tabary]

Hello.

To my understanding this is not a solution to the issue raised.

[gilles_tabary]

The requirement as I understand it (at least my requirement) is : at that time, update OneAgent to that version. So I use OneAgent Update Maintenance Windows for the "that time". Fine. But it offers me no solution as to the "that version" : actually whatever latest OneAgent installer version is available (dynamically disctirbuted by Mission Control into my cluster) get's installed.

It would be usefull to be able to specify target wanted version.

Regards.

[gilles_tabary]

Hello.

AFAIU this should be un-tagged as a solution. This is *not* the neither a solution.

Regards.

[Juwei_Zhang1]

not true

version can be selected, but minor is not

we need control both version and minor

you should have function  Automatic Update at GIVEN VERSION MINOR, not earlist, because PROD and LOWER env has timing gap, earlist version setting will push earlist version without tested into PROD. i believe you overlooked the issue in whole design and test. it causes issue

[Juwei_Zhang1]

I raised the issue as well as below

Dynatrace Should not push latest minor release mandatorily - Dynatrace Community

[gilles_tabary]

There is an RFE: OneAgent Update Maintenance Windows should allow me to specify a target version
https://community.dynatrace.com/t5/Product-ideas/RFE-OneAgent-Update-Maintenance-Windows-should-allo...

[tijust1]

@gilles_tabary Any update on this as still I am seeing no option to choose OneAgent version in Maintenance Window?

[Juwei_Zhang1]

my doing is to lock version at first in "OneAgent Default version", and create schedule without OA version specified. this meet all my need.

if allow schedule to pick version as well, we shall lose central management of OA version and create new issue.

so Lock version and Scheduling make up the OA version control, if you truely need such schedule.

if update OA along with Unix Patching, it need only Version lock and updating happen accordingly/automatically.

I choose to Lock and Manual Update, the third way, this make me less risk in case OA jar failed in transmission to target hosts and I capture in time in system notification.

Hope this help you some.

[gilles_tabary · Accepted solution]

Forgot to say : it works for a while now :

1. define a OneAgent Update Windows
2. on a given host == OneAgent settings
   1. select "Automatic updates during maintenance windows"
   2. then one can set Target version and Revision
3. Fine !

Thanks.