• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Updating VCSA and hitting the error Test RPM transaction failed

Duncan Epping · Aug 26, 2021 ·

I was updating my environment to vCenter Server 7.0 U2c, while going through the process I got this error that says “Test RPM transaction failed”. Below is the screenshot of the error. if you click “resume” you then, unfortunately, get stuck in an infinite loop. The only way to get out of the loop is by removing a file via SSH on vCSA called “/etc/applmgmt/appliance/software_update_state.conf”.

So now what if you want to update? We resolved it as follows, and let me include the deletion of the state file as well:

rm /etc/applmgmt/appliance/software_update_state.conf

Then we rebooted the VCSA:

reboot

Then we went into the appliance shell via SSH and ran the installer from the appliance:

appliancesh
software-packages install --url --acceptEulas

After which the installation was completed correctly.

Related

Server vcenter, vcsa, VMware

Reader Interactions

Comments

  1. @davedunaway says

    27 August, 2021 at 06:47

    Love it when I run into an issue and find that you have a fresh blog article with the answer.

    • @davedunaway says

      27 August, 2021 at 07:42

      Although, running that “software-packages install –url –acceptEulas” command tells me that my appliance is already running the latest build, which isn’t true. I’m still running 7.0.2.00200

      • Duncan Epping says

        27 August, 2021 at 09:12

        I staged the upgrade first and then tried to install, and when that failed I ran it via the command. Could it be that the install hasn’t been staged yet in your case?

      • Duncan Epping says

        27 August, 2021 at 09:13

        you can check what is currently stage using the following command:

        software-packages list --staged

  2. @davedunaway says

    28 August, 2021 at 23:29

    The update was still staged in the GUI, but the CLI said nothing was staged. I noticed that my /log drive on the VCSA was full, so I cleaned that up, extended it, rebooted and tried the CLI method again. It would not install or stage, regardless of whether the update was staged in the GUI. I staged and installed from the web GUI and it worked. I have two separate appliances that both behaved this way. Do appreciate your help!

    • Stas says

      6 September, 2021 at 18:16

      After I got that RPM error, I followed the first part of that guide (deleting the conf file and rebooting). Then cleaned the log partition, unstaged the update (from ui), staged the update (from ui) and clicked install (from ui). Finished successfully .

    • AdminWillie says

      22 September, 2021 at 16:25

      This was my issue as well. Appreciate the info Duncan and Dave!

  3. Lewis says

    27 September, 2021 at 09:30

    How do you enable SSH if you have already tried to run the update and it failed?
    The 5480 portal is stuck in the installation failed loop.

    • JL says

      14 October, 2021 at 03:08

      Hope you took a snapshot…

  4. Steve says

    21 October, 2021 at 17:55

    remove the end of the URL

  5. dmorse says

    18 June, 2022 at 00:46

    I ran into this today upgrading vCSA 7.0 U2 to 7.0 U3!! Had to increase the /storage/log partition per KB 2145603 as well as the steps in this article and comments (unstage, stage and install). Much appreciated!

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist in the Office of the CTO in the Cloud Infrastructure Business Group (CIBG) at VMware. Besides writing on Yellow-Bricks, Duncan co-authors the vSAN Deep Dive book series and the vSphere Clustering Deep Dive book series. Duncan also co-hosts the Unexplored Territory Podcast.

Follow Me

  • Twitter
  • LinkedIn
  • Spotify
  • YouTube

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2023 · Log in