Agent Client Collector Selective Upgrade does not upgrade to latest minor version - rounds down to x.y.0 (2.9.0 vs. 2.9.2 / 2.10.0 vs. 2.10.1) - Known Error

Agent Client Collector Selective Upgrade does not upgrade to latest minor version - rounds down to x.y.0 (2.9.0 vs. 2.9.2 / 2.10.0 vs. 2.10.1) Description ACC Upgrade happens, but does not upgrade to the current app minor version. The ACC upgrades to version x.y.0, instead of the x.y.z minor version expected. e.g. Upgrade of Upgrade of <2.10 to 2.10.1 - the ACC is told to only upgrade to 2.10.0

To confirm the problem: - The sn_agent_upgrade_history table will have the expected "To" value - e.g. 2.9.2 - but the log entries in that table will show the "About to download MSI file from..." URL has the wrong filename. - The ecc_queue MonitoringProbe/on_demand_request payload will show the check command including the wrong version too. e.g. "command":"runUpgrade.rb -v 2.9.0"

Steps to Reproduce

These steps could be used for any upgrade, but there are other known problems that might get in the way before you get to this problem. The 2 examples given have been seen on a customer instance.

Upgrade the ACC-F app from 2.8 to 2.9.2, (or from 2.9.2 to 2.10.1) Click Upgrade Agent on an existing ACC install Check the sn_agent_upgrade_history record states it will upgrade To 2.9.2 Look at the payload of the ecc_queue record created: It will include "runUpgrade.rb -v 2.9.0", instead of 2.9.2. e.g.

{"auto_binding":true,"clients_cis":{"77a196f3e535aad7":{"b49f9889975d551009d530ffe153af13":{}}}, "checks":[{"name":" Agent Upgrade - MSI ","command":" runUpgrade.rb -v 2.9.0 ", "interval":"60","timeout":600000,"id":"ddbe7e4997d1591009d530ffe153af9b_5f74fe90533d45100112ddeeff7b1229","exec_mode":"shell","params_background":false,"assets":"acc-f-upgrade-msi,acc-f-commons","check_type_id":"b69143c853a901100112ddeeff7b125b","instance_script":"true","params":{"upgrade_seq":"51be7e4997d1591009d530ffe153af99"},"priority":"1","requestId":"ddbe7e4997d1591009d530ffe153af9b"}]}

The sn_agent_upgrade_history records show the MSI version actually used as well: (this example is 2.9 to 2.10.1, and 2.10.0 is wrongly used).

Agent upgrade validation successful. Upgrade will now start and may take up to 30 minutes depand on the OS. Check results: Success! Log: # Logfile created on 2022-08-22 19:13:03 +0200 by logger.rb/v1.4.2 I, [2022-08-22T19:13:03.760180 #6168] INFO -- : Checking if nt authority\system is an admin? I, [2022-08-22T19:13:03.760292 #6168] INFO -- : SYSTEM account is admin! I, [2022-08-22T19:13:04.139444 #6168] INFO -- : About to download MSI file from https://install.service-now.com/glide/distribution/builds/package/app-signed/ agent-client-collector-2.10.0-windows-x64.msi I, [2022-08-22T19:13:23.622869 #6168] INFO -- : Download completed I, [2022-08-22T19:13:23.625191 #6168] INFO -- : Creating a new schedule using command: "schtasks /create /XML C:\ProgramData\ServiceNow\agent-client-collector\cache\acc-f-upgrade-msi\bin\acc_upgrade_task.xml /tn "ACC Upgrade" /f /ru system " I, [2022-08-22T19:13:23.795273 #6168] INFO -- : Scheduler task creation output: SUCCESS: The scheduled task "ACC Upgrade" has successfully been created.

I, [2022-08-22T19:13:23.795385 #6168] INFO -- : Running scheduler task with command: "schtasks /run /tn "ACC Upgrade"" I, [2022-08-22T19:13:23.832649 #6168] INFO -- : Scheduler task run output: SUCCESS: Attempted to run the scheduled task "ACC Upgrade".

Workaround This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.

A workaround in Script Include AgentVersionFieldStyle is possible, by changing line 69 from return AgentVersionFieldStyle.getAgentVersion(accfVer, true, '0'); to return accfVer;

Please import and commit this update set to make it easier to track and eventually revert the customisation: PRB1598028_sys_remote_update_set_4be1b9231b2191100054fdd2cd4bcbbb.xml