Package image://31.1.1-9122-20250127.143602/controller.pkg does not exist in [node1.controller.local]
Article ID: 405078
Updated On:
Products
VMware Avi Load Balancer
Issue/Introduction
The restore of Avi Load Balancer config fails in 30.2.x and 31.1.x version with the error controller.pkg does not exist in [node1.controller.local]
[admin:####]: > restore configuration file /path/to/backup/<backup_file>.json skip_warnings
Please enter the passphrase for the configuration:+---------------+--------+---------------+---------------------------+--------------+-----------------------------+-------+----------------------------------------------------------+
| Name | Tenant | Cloud | State | Operation | Image | Patch | Reason |
+---------------+--------+---------------+---------------------------+--------------+-----------------------------+-------+----------------------------------------------------------+
| cluster-0-1 | admin | - | UPGRADE_PRE_CHECK_WARNING | EVAL_RESTORE | 31.1.1-9122-20250127.143602 | - | Use 'show upgrade status detail filter pre_check_status' |
| Default-Group | admin | Default-Cloud | UPGRADE_FSM_INIT | None | 31.1.1-9122-20250127.143602 | - | - |
+---------------+--------+---------------+---------------------------+--------------+-----------------------------+-------+----------------------------------------------------------+The output below points to the missing upgrade image for 31.1.1 and the patch file 2p3.
[admin:####]]: > show upgrade status detail filter pre_check_status
+-----------------------+----------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+----------------------------------------------------------------------------------+
| uuid | cluster-######-####-####-####-######## |
| name | cluster-0-1 |
| node_type | NODE_CONTROLLER_CLUSTER |
| upgrade_readiness | |
| state | |
| state | UPGRADE_PRE_CHECK_ERROR |
| last_changed_time | Thu Jul 31 11:31:33 2025 ms(170712987) UTC |
| checks[1] | |
| check_code | SYSERR_MC_CONFIG_IMAGES_ERR |
| description | Required images are missing in the controller. |
| details[1] | Image(s): 31.1.1-9007-2p3-20250523.113042 are missing on the controller. Please |
| | upload them. |
| state | UPGRADE_PRE_CHECK_ERROR |
| start_time | 2025-07-31 11:31:15 |
| end_time | 2025-07-31 11:31:15 |
| duration | 0 sec |
| checks[2] | |
| check_code | SYSERR_MC_CONTROLLER_PACKAGE_ERR |
| description | 'System package does not exist.' |
| details[1] | Package image://31.1.1-9122-20250127.143602/controller.pkg does not exist in [no |
| | de1.controller.local] |
| state | UPGRADE_PRE_CHECK_ERROR |
| start_time | 2025-07-31 11:31:15 |
| end_time | 2025-07-31 11:31:15 |
| duration | 0 sec |Environment
Avi Controller version 30.2.x / 31.1.x and later versions
Cause
- The backup and restore flow has changed in versions 30.2.3 and later.
- Starting with Avi Version 30.2.3, the restore has been moved to the upgrade module.
- Once a fresh controller is deployed, the upgrade and patch file needs to be uploaded.
Resolution
The following are the steps to restore the backup config on the controller.
1) Show the available image on the controller
[admin:######]: > show image
+-----------------------------+--------------------------------------------+-------------------+---------------------+
| Name | UUID | Type | State |
+-----------------------------+--------------------------------------------+-------------------+---------------------+
| 31.1.1-9122-20250127.143602 | image-#######-####-####-####-####### | IMAGE_TYPE_SYSTEM | IMAGE_FSM_COMPLETED |
+-----------------------------+--------------------------------------------+-------------------+---------------------+
2) Download the upgrade and the patch file from https://support.broadcom.com.
Example: If the controller is on 31.1.1, download the upgrade package for 31.1.1
Example. If the config was backed up in 31.1.1-2p3, upload the 2p3 package before continuing with the restore.
3) Upload the upgrade package to the controller.
[admin:######]: > upload image filename /path/to/upgrade/file/controller-31.1.1-9122.pkg
4) Upload the patch file if the backup was taken on a patched version. eg: 31.1.1-2p3
[admin:######]: > upload image filename /path/to/patch/file/avi_patch-31.1.1-2p3-9007.pkg4) [admin:######]: > show image
+---------------------------------+--------------------------------------------+-------------------+---------------------+
| Name | UUID | Type | State |
+---------------------------------+--------------------------------------------+-------------------+---------------------+
| 31.1.1-9122-20250127.143602 | image-#######-####-####-####-####### | IMAGE_TYPE_SYSTEM | IMAGE_FSM_COMPLETED |
| 31.1.1-9007-2p3-20250523.113042 | image-#######-####-####-####-####### | IMAGE_TYPE_PATCH | IMAGE_FSM_COMPLETED |
+---------------------------------+--------------------------------------------+-------------------+---------------------+
5) Validate if the controller.pkg exists.
root@######:# cd /host/pkgs/31.1.1-9122-20250127.143602/
root@######:/host/pkgs/31.1.1-9122-20250127.143602# ls -ltr
total 5721576
-rw-r--r-- 1 root root 4275365322 Jul 31 11:43 controller.pkg
-rw-r--r-- 1 root root 71079266 Jul 31 11:44 azure.pkg
-rw-r--r-- 1 root root 165 Jul 31 11:44 VERSION
-rw-r--r-- 1 root root 1512431202 Jul 31 11:44 se.pkg
6) Restore the backup file
[admin:####] restore configuration file /path/to/backup/<backup_file>.json skip_warnings[admin:####]]: > show upgrade status
+---------------+--------+---------------+----------------------------+-----------+-----------------------------+---------------------------------+--------+
| Name | Tenant | Cloud | State | Operation | Image | Patch | Reason |
+---------------+--------+---------------+----------------------------+-----------+-----------------------------+---------------------------------+--------+
| cluster-0-1 | admin | - | UPGRADE_FSM_WAITING : (0)% | RESTORE | 31.1.1-9122-20250127.143602 | 31.1.1-9007-2p3-20250523.113042 | - |
| Default-Group | admin | Default-Cloud | UPGRADE_FSM_INIT | None | 31.1.1-9122-20250127.143602 | - | - |
+---------------+--------+---------------+----------------------------+-----------+-----------------------------+---------------------------------+--------+
[admin:####]]: > show upgrade status
+-------------+--------+-------+---------------------------------+-----------+-------+-------+--------+
| Name | Tenant | Cloud | State | Operation | Image | Patch | Reason |
+-------------+--------+-------+---------------------------------+-----------+-------+-------+--------+
| cluster-0-1 | - | - | UPGRADE_FSM_IN_PROGRESS : (12)% | RESTORE | - | - | - |
+-------------+--------+-------+---------------------------------+-----------+-------+-------+--------+
7) The controller should reboot once the restore is complete.
[admin:10-91-5-38]: > show upgrade status
+----------------+--------+---------------+---------------------------+------------+-----------------------------+---------------------------------+----------------------------------------------------------+
| Name | Tenant | Cloud | State | Operation | Image | Patch | Reason |
+----------------+--------+---------------+---------------------------+------------+-----------------------------+---------------------------------+----------------------------------------------------------+
| cluster-0-1 | admin | - | UPGRADE_FSM_COMPLETED | RESTORE | 31.1.1-9122-20250127.143602 | 31.1.1-9007-2p3-20250523.113042 | - |
| Default-Group | admin | Default-Cloud | UPGRADE_PRE_CHECK_WARNING | EVAL_PATCH | 31.1.1-9122-20250127.143602 | - | Use 'show upgrade status detail filter pre_check_status' |
| SE311-se-cuxwt | admin | Default-Cloud | UPGRADE_FSM_INIT | None | 31.1.1-9122-20250127.143602 | - | - |
+----------------+--------+---------------+---------------------------+------------+-----------------------------+---------------------------------+----------------------------------------------------------+Feedback
Yes
No
Powered by
