...
- The MINI ISO and RPMs and SMUs are merged to create a GOLDEN ISO. We see the correct file pointers in the sysadmin VM: sysadmin-vm:0_RSP0# run Thu Mar 12 09:03:52.619 UTC sysadmin-vm:0_RSP0:~]$cd tftpboot/ sysadmin-vm:0_RSP0:~/tftpboot]$ls -la total 3578900 drwxrwxrwx 3 root root 4096 Mar 12 09:03 . drwxr-xr-x 10 root root 4096 Mar 12 07:58 .. -rw-r--r-- 1 root root 1978871808 Mar 12 07:37 asr9k-goldenk9-x64-6.5.3-0 <<<<<< Current active image -rwxr-xr-x 1 root root 1684977664 Mar 11 15:52 asr9k-goldenk9-x64-6.6.3-0 <<<<<<<< inactive image drwxr-xr-x 3 root root 4096 Mar 10 13:58 boot -rwxr-xr-x 1 root root 637 Mar 12 08:47 grub.cfg -rwxr-xr-x 1 root root 916590 Mar 12 08:01 grub.efi lrwxrwxrwx 1 root root 28 Mar 12 08:47 system_image.iso -> ./asr9k-goldenk9-x64-6.5.3-0 <<<<<<<<< correct file linkage -rwxrwxrwx 1 root root 0 Mar 11 16:12 zapdisk.log - In the above outputs, we see both image files are ending with version "0" which is causing the issue and the remove command thinks the active/committed GISO has to be removed as well. - When the "install remove inactive" is executed in the XR-VM we see that the 'current active image' ISO file also gets removed while the file pointer remains: RP/0/RSP0/CPU0:lab11#install remove inactive Thu Mar 12 10:04:39.018 CET Mar 12 10:04:41 Install operation 55 started by user: install remove inactive Mar 12 10:04:42 Install operation will continue in the background RP/0/RSP0/CPU0:lab11#admin Thu Mar 12 10:04:51.496 CET sysadmin-vm:0_RSP0# run Thu Mar 12 09:04:53.710 UTC Mar 12 10:04:53 Install operation 55 finished successfully sysadmin-vm:0_RSP0:~]$cd tftpboot/ sysadmin-vm:0_RSP0:~/tftpboot]$ls -la total 912 drwxrwxrwx 3 root root 4096 Mar 12 09:04 . drwxr-xr-x 10 root root 4096 Mar 12 07:58 .. drwxr-xr-x 3 root root 4096 Mar 10 13:58 boot -rwxr-xr-x 1 root root 637 Mar 12 08:47 grub.cfg -rwxr-xr-x 1 root root 916590 Mar 12 08:01 grub.efi lrwxrwxrwx 1 root root 28 Mar 12 08:47 system_image.iso -> ./asr9k-goldenk9-x64-6.5.3-0 <<<<<<<<<< This file is here but the corresponding image file is removed -rwxrwxrwx 1 root root 0 Mar 11 16:12 zapdisk.log sysadmin-vm:0_RSP0:~/tftpboot]$exit exit
- The issue is observed on ASR9K 64-bit platform. - The GISO is created while merging the MINI ISO and SMUs.
- There are 2 potential workarounds: 1) One workaround would be to remove the inactive packages individually by "install remove " OR "install remove disk0:.*6.6.3" for example. 2) Another workaround, to "install remove inactive" which removes the file and afterwards execute " install add source /disk2:/boot asr9k-goldenk9-x64-6.5.3-0.iso", i.e. re-copy the ISO afterwards again. In this case also "install remove inactive" does not do any harm.
- The issue is present in 6.5.3 and newer releases. However, some earlier eXR releases may be affected as well.