Air Gap upgrade to .182 fails on patch_os

[mtkhayes3]

Currently running Air gap version .130 and trying to upgrade to .182
It worked in test environment but I am only using 1 x Manager VM 1 x Sensor node and 1 x Search node

Problem encountered upgrading packages. Additional info follows:
result:
Running scope as a unit run-xxxx.scope.
Error: Package: libkadm5-1.15.1-54.el7_9.x86_64 (airgap_repo)
Requires: krb5-libs(x86_64) = 1.15.1-54.el7_9
Installed: krb5-libs-1.15.1.-51.el7_9.x86_64 (@airgap_repo)
krb5-libs(x86-64) = 1.15.1.-50.el7
Error: Package: krb5-devel-1.15.1-54.el7_9.x86_64 (airgap_repo)
Requires: krb5-libs(x86_64) = 1.15.1-54.el7_9
Installed: krb5-libs-1.15.1.-51.el7_9.x86_64 (@airgap_repo)
krb5-libs(x86-64) = 1.15.1.-50.el7
stdout: you could try using --skip-broken to work around the problem
you could try running: rpm -Va --nofile --nodigest
Changes:
ID: needs_restarting
Function: module.run
Result: True
Comment: min.send: True
Summary xxxxxx
Succeeded: 1 (changed=1)
Failed: 1
Command failed with exit code 2; will try in 60 seconds then fails altogeter

[dougburks]

Did you verify the .182 ISO image?

[mtkhayes3]

Yes it was and I also redownloaded it again just in case. Should I try upgrading to .160 first then .182?

[dougburks]

Sure, you could try that.

[mtkhayes3]

Ran libkadm5-1.15.1-54.el7_9.x86_64.rpm and Found that an rpm was missing from air gap repo krb-libs(x86-64) = 1.15.1.-54.el7_9 is missing even though I used the same iso for 3 other upgrades no issues and verified the iso

[dougburks]

Strange. Did you manually add any other software to that system or make any other changes?

[mtkhayes3]

I will try it and cross my fingers

…

On Mon, Dec 19, 2022 at 6:51 AM Doug Burks ***@***.***> wrote: Sure, you could try that. — Reply to this email directly, view it on GitHub <#9402 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC3I57Q2HFPQDDYA7YSBEV3WOBD3NANCNFSM6AAAAAAS77YJNE> . You are receiving this because you authored the thread.Message ID: <Security-Onion-Solutions/securityonion/repo-discussions/9402/comments/4448217 @github.com>

[mtkhayes3]

So this is what I ended up doing and it is working now. Instead of running U upgrade I ran C to continue without upgrades which rebuilt the repo and then ran U upgrade. I am not sure why the repo was missing some rpms but when I used the same iso for other installs without any issues.

…

On Tue, Dec 20, 2022 at 10:12 AM Doug Burks ***@***.***> wrote: Strange. Did you manually add any other software to that system or make any other changes? — Reply to this email directly, view it on GitHub <#9402 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC3I57UVML72A4K2DFHUPJLWOHEETANCNFSM6AAAAAAS77YJNE> . You are receiving this because you authored the thread.Message ID: <Security-Onion-Solutions/securityonion/repo-discussions/9402/comments/4459757 @github.com>