Open cr0cdev opened 3 days ago
Hi @cr0cdev,
Thanks for your detailed explanation!
The API schema of "/um/image/upgrade/ext" in FNDN is outdated. The possible JSON request format should be:
{
"method": "exec",
"params": [
{
"url": "/um/image/upgrade/ext",
"data": {
"devices": [{
"image": "7.2.9-b1688",
"name": "YOUR_DEVICE_NAME"
}],
"create_task": "enable",
// "flags": <a number> // must be given in numeric code, see flags number below.
"adom": "root"
}
}
],
"session": "{{fortimanager_session}}",
"id": 6,
"verbose": 1
}
Flags number:
"f_boot_alt_partition" : 1
"f_skip_retrieve" : 2
"f_skip_multi_steps" : 4
"f_skip_fortiguard_img" : 8
"f_preview" : 16
The GUI still uses the older API endpoint "/um/image/upgrade/". For now, please still use fortinet.fortimanager.fmgr_um_image
to upgrade images.
I will update "fmgr_um_image_ext" once its API is updated in FNDN.
Thanks, Dux
Hi!
I'm testing device upgrade using
fmgr_um_image_upgrade_ext
module and it is not creating a task and when looking at the API call in GUI it shows that it also sendsadom
parameter when upgrade is initiated via GUI. Here is the task:Returns:
No task is created for the device upgrade. When I add
bypass_validation: true
andadom: "{{ adom_name | lower }}"
underum_image_upgrade_ext
then the task returns no devices as status under response_data: Task:Response:
Now if I use the older module which uses the older API endpoint everything works as expected. The upgrade task is created under FortiManager and the device is being upgraded. Task:
Response: