Unknown error 243 while upgrading SRM or VRMS appliances to 9.0.1 or 9.0.2

Products

• VMware Live Recovery
• VMware vSphere ESXi 8.0

Issue/Introduction

This is a known issue affecting VRMS and SRM upgrades to 9.0.1 and 9.0.2 and has been fixed as of the 9.0.2.1 release 24404698 

ERROR Operation Failed, failed to install update: Unknown error 243

You could also hit this error if you are updating from VR 9.0.0.1, 23690274 > VR 9.0.2, 24171210.

Failed to install update: Operation not permitted: The connection was closed by the remote end during handshake.

 

Environment

vSphere Replication 9.0.1, 9.0.2

Site Recovery Manager 9.0.1, 9.0.2

Cause

In most situations, the gpgkey is missing or not validated for one of the upgrade packages

In vSphere replication appliance /opt/vmware/support/logs/dr/drconfig.log

In SRM appliance /opt/vmware/support/logs/dr/drconfig.log

Failed to install update: 'N7Vmacore15SystemExceptionE Unknown error 243 (243)

--> Error processing package: /mnt/cdrom/update/package-pool/vmware-jre-21.0.3-10.x86_64.rpm
--> Error(1523) : gpgkey entry is missing for this repo. please add gpgkey in repo file or use --nogpgcheck to ignore.

Resolution

ALERT: This issue has been fixed in the release 9.0.2.1

vSphere Replication 9.0.2.1 | 04 DEC 2024 | Build 24404698
VMware Live Site Recovery 9.0.2.1 | 04 DEC 2024 | Build 24401766

Follow the below steps to upgrade to 9.0.1 or 9.0.2:

  

    Upgrade vSphere replication to 9.0.0.1 | 19 APR 2024 | Build 23690274 and then proceed with the following workaround when the appliance is on 9.0.0.1

    Upgrade SRM to 9.0 | 19 MAR 2024 | Build 23464738 and then proceed with the following workaround when the appliance is on 9.0.

    

1. Take a normal snapshot of the appliance 
   
   
2. Copy the attached RPM into the appliance /tmp directory using WinSCP or a similar program
   
   
3. SSH into the SRM or VRMS appliance as admin
   
   
4. Run command su - and enter the root password
5. Run the command: rpm -Uvh --nodeps /tmp/dr-configurator-9.0.1-76796489.x86_64.rpm
   
   
6. Reload services by running the command - systemctl daemon-reload
   
   
7. Power OFF and power ON the appliance. Check /var/tmp/upgrade directory and make sure it is empty and remount the ISO.
   
   
8. Log into VAMI interface and proceed to upgrade to 9.0.1 using ISO

 

This issue has been fixed in 9.0.2, but it will only work for upgrades from 9.0.0.1 (VR) or 9.0 (SRM) to higher versions. For example, if you have an issue in upgrading from 9.0.1 > 9.0.2, you still have to patch the dr-configurator following this KB.

Additional Information

In vSphere Replication appliance /opt/vmware/support/logs/dr/drconfig.log

In SRM appliance /opt/vmware/support/logs/dr/drconfig.log

Failed to install update: 'N7Vmacore15SystemExceptionE Unknown error 243 (243)

--> Error processing package: /mnt/cdrom/update/package-pool/vmware-jre-21.0.3-10.x86_64.rpm
--> Error(1523) : gpgkey entry is missing for this repo. please add gpgkey in repo file or use --nogpgcheck to ignore.



Alternative option is to upgrade from 9.0 release straight to 9.0.2 release follow these instructions (by skipping resolution part using rpm 9.0.1-76796489.x86_64.rpm)


1. Take a snapshot of the appliance
2. Mount 9.0.2 ISO to VRMS/SRM appliance
3. Access VAMI interface, navigate to the update tab and select "cdrom"
4. SSH into appliance and su into root account and run the following commands:
5. cp /mnt/cdrom/update/package-pool/dr-configurator-9.0.2-24170200.x86_64.rpm /tmp
6. rpm -Uvh --nodeps /tmp/dr-configurator-9.0.2-24170200.x86_64.rpm
7. systemctl daemon-reload
8. Perform a graceful shutdown of the appliance and power back on 
9. Perform upgrade as normal