Looking for new updates are failing after update to 13.1

[mikkeland]

Hi,

I just updated a VSA based Veeam install from 13.0.2 to 13.1 (i think?).
The updrade went smoot and all backup jobs run as expected.

However, subsequent searches for updates just gives an error
It attempts to connect to this site https://repository.veeam.com/vsa/9.6/vb ... repomd.xml

Code: Select all

Failed to update package cache: Errors during downloading metadata for repository 'veeam-backup-mandatory':
  - Status code: 404 for https://repository.veeam.com/vsa/9.6/vbr/13.0/mandatory/repodata/repomd.xml (IP: 18.238.4.106)
Error: Failed to download metadata for repo 'veeam-backup-mandatory': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

Entering the URL in my browser gives a 404 error - are anybody else experiencing the same thing?

/Mikkel

[vnikiforov]

Hello, Mikkel,

It should actually show that repo URL. Notice 13.1 path... Maybe just restart the appliance?
I'd recommend to open a support case, and provide Host Manager Console logs

[mikkeland]

Case created - i'll make sure to add any relevant info to this post in case its user-fixable

/M

[mikkeland]

Just a short update on this one - Veeam support had me edit a repo file to point to the correct repository and clear the dnf cache

Code: Select all

From: https://repository.veeam.com/vsa/9.6/vbr/13.0/mandatory/repodata/repomd.xml
To: https://repository.veeam.com/vsa/9.6/vbr/13.1/mandatory/repodata/repomd.xml

After this change updates were working as expected, and my install is not at 13.1.1.18 and everything looks to be working as expected

/M

[vnikiforov]

Hello, Mikkel,

Thank you for the update. Great to hear it is working now.

[BusterRox]

Any chance you'd share which repo file had to be edited or the support case ID so we can reference it? We had a client with the same issue early last week that was directed by Veeam Support to redeploy his VSA. This took a few hours due to a slow connection and after all was said and done, the update still fails because it's looking at the old path: https://repository.veeam.com/vsa/9.6/vb ... repomd.xml.

[vnikiforov]

Hello Justin,

Please avoid manual edits on your Veeam Software Appliance. I would not take a chance without investigating full logs to advise what's wrong. If you suspect Veeam support engineer might be wrong with their assumptions, please use Talk to manager button and describe what you suspect is wrong.

[BusterRox]

Understood, but being able to reference the OPs support case ID when we respond to the original engineer in our open case or click Talk to Manager would likely expedite the process, wouldn't you agree?

[vnikiforov]

Hello Justin,

You may refer to internal KB0077386, but that might be absolutely non applicable in your case and a wrong article to begin with, as I said - it is not possible to tell what is the issue, despite it is perceived like an identical one and support management won't be able to resolve the issue right away, there will be extra time taken.