Symantec Management Center do not allow to upload new software image
search cancel

Symantec Management Center do not allow to upload new software image

book

Article ID: 274863

calendar_today

Updated On:

Products

Management Center - VA

Issue/Introduction

ManagementCenter# installed-systems view
1. Version : 3.3.3.1, Release ID : 281216, Locked : true, Booted : true
Boot Status : Last boot succeeded, BuildType : Release, CreationTime : 2023-01-20T20:21:36+0100
BootTime : 2023-10-10T14:38:21.442+0200, DisplayName : Symantec Management Center 3.3.3.1
Default system to run on next hardware restart: 1
Current running system: 1
System to replace next: None
ManagementCenter# installed-systems load ?
Description: Image uri
Possible completions:
<URL> SCP or HTTP/HTTPS URL. Examples:
scp://<host>:<port>/<path>
http://<host>:<port>/<path>
password Password (optional)
username Username (optional)
ManagementCenter# installed-systems load http://x.x.x.x:8080/fs/download/ad23915794564ef6a42d92ec0826ce70
% failed
% ErrorCode : -14109
% ErrorMessage : Unable to add image. Images are either locked or default. Unable to delete the oldest image
ManagementCenter#


Tried to upload the new image via CLI or GUI. Both present the same error.

Current Version 3.3.3.1
New Image that I'm trying to upload 3.3.4.1

The issue happens after the download and the installation check. There is only one image loaded on the appliance

Environment

Management Center Virtual Appliance 3.2 and above

Cause

It's highly suspect the reported upgrade issue is caused by the boot disk (disk 1), which is not following the current sizing. You verify the allocated disk space for MC-VA via your VM host but from our internal diagnostics, we see only 2 GB resource on first disk (disk 1), while the current (recommended) sizing should be 4 GB. Please see the diag. extracts below, for reference.

  ],
            "hostname": "xxxxxxxx",
            "total_memory": "8042496",
            "disks": [
                {
                    "name": "sda",
                    "capacity": "2147483648"
                },
                {
                    "name": "sdb",
                    "capacity": "107374182400"
                }
            ],
            "cpu": [
                {
                    "cache": "30976 KB",
                    "cores": "2",
                    "hypervisor": "",
                    "model": "Intel(R) Xeon(R) Gold 6152 CPU @ 2.10GHz",
                    "vender": "GenuineIntel",
                    "speed": "2095.077"
                }
            ],
            "network_interfaces": [
             3",
                    "name": "nic0_0",
                    "mtu": "1500"
                },
                {
                    "name": "nic1_0",
                    "mtu": "1500"
                },
                {
                    "name": "docker0",
                    "mtu": "1500"
                }
            ],

Note 1: the sda boot disk capacity is currently 2.14 GB. However, the .bcsi disk image sizes are currently slightly greater than 1 GB, so MC is trying to clear out old images to make enough space for the new image to fit. However, since there's only one current image, it cannot delete the active image and throws this error.

Resolution

The only way to change the sda boot disk (disk 1) capacity is by deploying a fresh version. The default boot disk size is now 4 GB, so should easily fit both images.

Please, we recommend to follow the resolution guidance below.

1. backup MC 3.3.2.1 db/config currently running,

2. redeploy MC 3.3.2.1, with disk 1 = 4GB, Disk 2 = 100GB or higher,

3. then restore of the db backup taken from the currently running MC 3.3.2.1,

4. and then upgrade to MC 3.3.4.1.

Note 2: To activate extra space for disk 2, please refer to the detailed guidance below.

  • Virtual Appliance Management Center are consist of two (2) disks,  boot disk and data disk respectively.   
  • In earlier releases, if you increased the data disk space on an existing MC VA, you had to restore defaults on the appliance to activate the new storage. In Management Center 3.2.x and later, the storage command can be used to activate the new configuration without restoring defaults.   
  • Note that the storage command only affects if you add space to data disk (disk 2).   Increasing the boot disk (disk 1)  or adding another virtual disk (disk 3) are not supported and can not be adjusted using the storage command.     If your boot disk (disk 1)  is lower than the recommended 4 GB, we recommend to deploy new MC  instance following the Management Center Virtual Machine Sizing Guidelines.
  • It is good practice to take MC backup and offload to another file server (or download it to your desktop) prior doing any maintenance on your Management Center.

 

To increase disk space for data disk (disk 2)Take MC backup and offload or download it.

- Power-off  MC

- Increase space on disk 2  (Refer to your Host Virtualization documentation how to increase disk space in VM guest). 

- Power-on MC

- Once booted, run the following commands in MC CLI privilege (enable) mode:

#storage view

#storage activate-extra-space

 

Additional Information

Sample output:

mc19# storage view

Storage type disk VG
Storage utilized size: 104.856 GiB
Number partitions used: 1
Can be expanded
Usable space available: 314.574 GiB

mc19# storage activate-extra-space


***************************** ATTENTION ***************************
IF YOU CHOOSE TO CONTINUE ALL AVAILABLE DISK SPACE WILL BE UTILIZED
THIS OPERATION IS NOT REVERSABLE. DECREASING VM DISK SPACE WILL REQUIRE
RESTORE_DEFAULTS OPERATION DESTROYING ALL STORED DATA
*******************************************************************
Continue? [no,yes] yes

Completed.

mc19# storage view

Storage type disk VG
Storage utilized size: 419.429 GiB
Number partitions used: 2

mc19#