Automatic agent deploy to Oracle Linux failing

[bhnelson]

Support case 04277492. Veeam B&R 10p1

When deploying the linux agent via protection group to an Oracle Linux 7 machine (UEK kernel) the action fails due to missing kernel headers. The kernel-uek-devel package is available in yum, but the 'veeaminstaller' does not even attempt to install it. It does however install numerous other dependencies, such as gcc, dkms, etc.

This worked as expected in 9.5u4. The veeaminstaller would install kernel-uek-devel itself and the agent deployment would work without interaction. It seems to have stopped working in Veeam 10.

Support is telling me 'working as intended' (as usual) but that seems bonkers. Having to manually touch potentially 100's of machines defeats the whole purpose of protection groups!

Note there are multiple issues in my case which would all be nice to have fixed, but this is the primary one.

Thanks

[bhnelson]

No help from the forums here.

Support reiterated 'working as intended'. So, I guess RFE for the non-broken behavior from Veeam 9.5.4b.

Thanks

[HannesK]

Hello,

No help from the forums here.

sometimes it takes some time to investigate, please stay tuned.

Best regards,
Hannes

[HannesK]

Hello,
short update without solution: the issue also exist in 10a and it seems to be not intended behavior.

A general hint: case #04277492 ended in tier 1. If something worked before an upgrade, then it is a good reason to escalate the case via my.veeam.com ("talk to a manager")

Best regards,
Hannes

[PTide]

@bhnelson,

Was that an Agent upgrade (from v3 to v4), or clean install of the agents?

Veeam doesn't manage installation of dependencies.

Why it worked in 9.5?

Because VBR 9.4 attempted to install kernel-uek-devel that matches the currently installed kernel version ( can be obtained via 'uname -r') from oracle repository.
That is, "linux-headers-$(uname -r)" worked just fine.

Why it stopped working?

Because Oracle changed the format for headers packages so that the trick with uname does not work anymore so it has been remove from the installer.

However, it seems that Oracle is back to a proper naming.

We'll check how it works and will make a decision on when we will include it in VBR.

Thanks!

[PTide]

@bhnelson,

Could you re-open the case or open a new one? In order to start developing the fix we need to have a support case in an "open" state, but it seems that case # 04277492 is already closed.

Thanks!

[bhnelson]

@PTide,

Sorry it's been a while since I've checked forums! I opened a new case for this issue, #04406868.

To answer your previous question, this was a fresh install of the VAL on a new VM.

Thanks!
Brian