09-01-2021 06:47 AM
FAILED: install_add_activate_commit : Super package already added. Add operation not allowed. 'install remove inactive' can be used to discard added packages
So, I was upgrading a switch last evening to 16.12.05b using the following command:
install add file:flash:cat3k_caa-universalk9.16.12.05b.SPA.bin activate commit
The switch ran through the process to the last step which was to reboot. I inadvertently selected no reboot. I then attempted the upgrade process again and now I receive this error. I ended up just installing the upgrade using BUNDLE mode.
I've already run 'install remove inactive' and then attempted another INSTALL mode install and no change.
What do I need to do to fix this.
Thanks,
Andrew
Solved! Go to Solution.
10-04-2022 08:23 AM - edited 10-04-2022 08:25 AM
I'm back!
Here's what I found to resolve the issue - it's a little overkill but it's the method that we followed on the TAC call yesterday and it worked. Retried it a handful of times afterward (9300, 3850) with nothing but success.
1. Remove the target version file from the flash if you have it copied (annoying yes, but appears necessary to remove super package error)
2. Remove boot statement (conf t, no boot system)
3. Point boot statement to packages.conf (conf t, boot system flash:packages.conf)
4. Remove inactive packages (install remove inactive, yes)
5. Copy target image bin file
6. Do an MD5 verify (never hurts :D: verify /md5 flash:{imageName} {expectedSignature})
7. OPTIONAL: Setup a label for your current image that way you can rollback easily after committing new image (install label {preferredIDnumber} label-name {currentVersionLabel}). Pro-tip, do a quick check of any current existing rollback point IDs to make sure you dont overwrite (show install rollback)
8. Add, activate, and commit new image with automatic reload: (install add file flash:{fileName} activate commit prompt-level none)
This should resolve the super package issue - going forward you don't necessarily need to run the 'install remove inactive' command every time, I've validated this a few times. If you do decide to use it though as standard practice, make sure to copy your target image after the command otherwise you may delete the .bin file.
Good luck! Here for any questions/feedback.
03-10-2022 11:08 PM
i have same problem too, but once i erase the version with "install remove inactive", and perform install new version again. It's work fine for me on Catalyst 9200
09-02-2022 09:40 AM
Weird, I'm having the same issue and when using "install remover inactive" it doesn't change the error message? I'm currently in bundle mode trying to switch to install mode.
08-11-2023 09:02 AM
This worked for me, too! Before erasing, I used dir flash:*.bin and had the previous version on the flash as well. After running install remove inactive, I copied the file again, ran the dir command, and it only showed the latest version on the flash.
09-29-2022 12:11 AM
I am finding the same error, did you get the solution? please share
09-29-2022 12:34 AM
Hello, is there a solution?
10-02-2022 11:14 PM
Having the same problem as well, though already in install mode. Trying to upgrade to 17.03.05 from 16.12 but hitting the super package error. Going to escalate with Cisco TAC and will provide any answer I find here.
Switch current version:
Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 65 C9300-48UXM 16.12.4 CAT9K_IOSXE INSTALL
Command + error message:
"response": "install_add_activate_commit: START Mon Oct 3 05:51:58 UTC 2022\ninstall_add_activate_commit: Adding PACKAGE\ninstall_add_activate_commit: Checking whether new add is allowed ....\nFAILED: install_add_activate_commit : Super package already added. Add operation not allowed. 'install remove inactive' can be used to discard added packages"
(Writing automation logic to perform upgrade, excuse the JSON response instead of CLI format)
10-04-2022 08:12 AM - edited 10-04-2022 08:24 AM
I'm back!
Here's what I found to resolve the issue - it's a little overkill but it's the method that we followed on the TAC call yesterday and it worked. Retried it a handful of times afterwards with nothing but success.
1. Remove the target version file from the flash if you have it copied (annoying yes, but appears necessary to get rid of super package error)
2. Remove boot statement (conf t, no boot system)
3. Point boot statement to packages.conf (conf t, boot system flash:packages.conf)
4. Remove inactive packages (install remove inactive, yes)
5. Copy target image bin file
6. Do an MD5 verify (never hurts :D: verify /md5 flash:{imageName} {expectedSignature})
7. OPTIONAL: Setup a label for your current image that way you can rollback easily after committing new image (install label {preferredIDnumber} label-name {currentVersionLabel}). Pro-tip, do a quick check of any current existing rollback point IDs to make sure you dont overwrite (show install rollback)
8. Add, activate, and commit new image with automatic reload: (install add file flash:{fileName} activate commit prompt-level none)
This should resolve the super package issue - going forward you don't necessarily need to run the 'install remove inactive' command every time, I've validated this a few times. If you do decide to use it though as standard practice, make sure to copy your target image after the command otherwise you may delete the .bin file.
Good luck! Here for any questions/feedback.
10-04-2022 08:23 AM - edited 10-04-2022 08:25 AM
I'm back!
Here's what I found to resolve the issue - it's a little overkill but it's the method that we followed on the TAC call yesterday and it worked. Retried it a handful of times afterward (9300, 3850) with nothing but success.
1. Remove the target version file from the flash if you have it copied (annoying yes, but appears necessary to remove super package error)
2. Remove boot statement (conf t, no boot system)
3. Point boot statement to packages.conf (conf t, boot system flash:packages.conf)
4. Remove inactive packages (install remove inactive, yes)
5. Copy target image bin file
6. Do an MD5 verify (never hurts :D: verify /md5 flash:{imageName} {expectedSignature})
7. OPTIONAL: Setup a label for your current image that way you can rollback easily after committing new image (install label {preferredIDnumber} label-name {currentVersionLabel}). Pro-tip, do a quick check of any current existing rollback point IDs to make sure you dont overwrite (show install rollback)
8. Add, activate, and commit new image with automatic reload: (install add file flash:{fileName} activate commit prompt-level none)
This should resolve the super package issue - going forward you don't necessarily need to run the 'install remove inactive' command every time, I've validated this a few times. If you do decide to use it though as standard practice, make sure to copy your target image after the command otherwise you may delete the .bin file.
Good luck! Here for any questions/feedback.
06-05-2024 05:55 AM
I had this same exact issue and this worked perfectly for me. Thank you for posting!
06-22-2023 08:12 AM - edited 06-22-2023 08:14 AM
Hi there! Long time taker, first time contributor!
I saw the above post and thought to myself. OMG I cannot upload this file again. It took nearly 30 minutes!
So here is the fix that worked for me!
Use the: install remove file command on every file associated with the new Image EXCLUDING the "cat9k_iosxe.17.06.05.SPA.bin" file.
Then run the install add command and it will allow for the installation.
Good Luck!
install remove file flash:cat9k-guestshell.17.06.05.SPA.pkg
install remove file flash:cat9k-lni.17.06.05.SPA.pkg
install remove file flash:cat9k-cc_srdriver.17.06.05.SPA.pkg
install remove file flash:cat9k-espbase.17.06.05.SPA.pkg
install remove file flash:cat9k-rpbase.17.06.05.SPA.pkg
install remove file flash:cat9k-rpboot.17.06.05.SPA.pkg
install remove file flash:cat9k-sipbase.17.06.05.SPA.pkg
install remove file flash:cat9k-sipspa.17.06.05.SPA.pkg
install remove file flash:cat9k-srdriver.17.06.05.SPA.pkg
install remove file flash:cat9k-webui.17.06.05.SPA.pkg
install remove file flash:cat9k-wlc.17.06.05.SPA.pkg
install remove file flash:cat9k_iosxe.17.06.05.SPA.conf
!
install add file flash:cat9k_iosxe.17.06.05.SPA.bin activate commit
!
11-16-2023 04:39 PM
I did the "install remove inactive" to proceed with the upgrade. The new IOS will need to be copied again.
The root cause was a lack of free disk space.
It might be a good practise to do housekeeping before copying in the new IOS version.
04-21-2024 02:40 PM
I encountered same error after forgetting to respond to the prompt. What, I tried is to reboot the switch with the new image in Bundel mode using .bin image and once it get's upgraded to new version I ran "INSTALL REMOVE INACTIVE" which removed all the unused BIN and PKG file.
This operation may require a reload of the system. Do you want to proceed? [y/n]install_add_activate_commit: No User Response, Request Timeout
FAILED: install_add_activate_commit : Super package already added. Add operation not allowed. 'install remove inactive' can be used to discard added packages
Apr 21 18:49:35.076 %INSTALL-3-OPERATION_ERROR_MESSAGE: R0/0: install_engine: Failed to install_add_activate_commit package flash:cat9k_lite_iosxe.17.09.04a.SPA.bin, Error: install_add_activate_commit : Super package already added. Add operation not allowed. 'install remove inactive' can be used to discard added packages
After removing unused file I set boot path to packages.conf and commit new image using following command
install add file flash:cat9k_lite_iosxe.17.09.04a.SPA.bin activate commit
in this way, we won't have to uploaded the image which is a pain if the image size is big and needs to copy image from Syslog server located far from site in Data Centre.
11-26-2024 02:34 AM
We had the same problem on some of our 9200s. This was because we had forgotten during a previous update to validate that the installation uncommitted.
To do this, check the installations marked as uncommitted. (show install uncommitted)
If you see your previous installation as uncommitted, validate it. (install commit)
Then restart the installation. (install add file bootflash:file.bin)
Check if your installation is in Inactive (show install summary)
Activate the new firmware (install activate)
At the end of the installation, do not forget to check and validate the compliance of the installation. (show install uncommitted) / (install commit)
12-17-2024 03:04 AM
Thank you! All other posts were unhelpful, but this one was exactly what the problem was in my 9200 switch.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide