Proxmox 8 update stuck on MACsec when rebooting

[alpha754293]

I did a fresh install of Proxmox 8 on my 4930K system (running on an Asus P9X79-E WS motherboard, with 64 GB of DDR3-1600 unbuffered, non-ECC RAM) on an Intel 520 series 512 GB SATA SSD. (Not that it really matters, but I also have a Quadro 620 for basic video output because its the only other low profile GPU that I have.)

When I ran apt update && apt upgrade -y; reboot, the system was able to grab the updates just fine, but when it reboots, it will get stuck on the MACSec part roughly 5 seconds into the booting process.

Is anybody else experiencing this issue?

For the time being, I have reverted back to using Proxmox 7.4-3 just to get my testing going (with Ceph).

Any help would be greatly appreciated.

Unfortunately through, because I am currently testing Ceph, I won't be able to pull any logs from the system nor anything like that. I might be able to try it again after my testing is complete though.

Thank you.

 

[gfngfn256]

apt upgrade

You should NOT be using upgrade but rather dist-upgrade as shown here. You can search these forums on this issue.

 

[alpha754293]

You should NOT be using upgrade but rather dist-upgrade as shown here. You can search these forums on this issue.

Four things:

1) The documentation doesn't actually say NOT to use upgrade. It only says that to run the update, to use dist-upgrade, but it makes no explicit mention prohibiting the use of upgrade.

2) Further, to (1), it doesn't say why not to use upgrade in lieu of dist-upgrade.

3) I tried searching for this issue with MACsec on the forums already. No results, hence my question.

4) Why would upgrade cause the system to hang at MACsec? This response doesn't explain why this is the case.

 

[gfngfn256]

3) I tried searching for this issue with MACsec on the forums already. No results, hence my question.

You misunderstood, I meant (as indicated clearly through the embedded link) to search the forums on the subject of NEVER using apt upgrade. Here are some more results.
This may very well be the issue you are experiencing. But not for certain.

I've dealt with all your points.

 

[alpha754293]

You misunderstood, I meant (as indicated clearly through the embedded link) to search the forums on the subject of NEVER using apt upgrade. Here are some more results.
This may very well be the issue you are experiencing. But not for certain.

I've dealt with all your points.

"You misunderstood, I meant (as indicated clearly through the embedded link) to search the forums on the subject of NEVER using apt upgrade. Here are some more results."
No. If you actually clicked on the link that you provided, the text that shows up at the bottom of the web browser CLEARLY states that it is tags/apt-upgrade.

Therefore; clicking on the link LITERALLY brings up this where within the first four results that shows up with the tag apt-upgrade, NONE of them has ANYTHING to do with NOT/never to use it.

Thus, contrary to your claims, click on a link that only pulls the tagged results does NOT point to a reference nor a resource that talks about "never" to use it.

In fact, even in your own citation of the Proxmox documentation, does the documentation NEVER say "never" use apt-upgrade. Of course, you would know that if you actually read said Proxmox documentation that you pointed me to. (Seriously, do you even click on your own links that you provide?)

So, no, the search function on these forums is inadequate to be able to pull from that.

Again, from your second search results link, this is what literally shows up:

Where the last four of the results, as shown in the screenshot that I just took, points to this thread, which wouldn't have existed a priori.

I've dealt with all your points.

No, you haven't.

4) Why would upgrade cause the system to hang at MACsec? This response doesn't explain why this is the case.

You still haven't provided an explanation as to why using upgrade would cause Proxmox to hang at MACsec when it is booting up, unless, of your, you're admitting that Proxmox/Linux is so fragile that running upgrade is sufficient to break Proxmox, which if that's the case, then that's fine. But at least have the gumption to tacitly admit or at least acknowledge that.

If upgrade can cause Proxmox to hang on boot like this, then the package that is responsible for this should be held back from said upgrade.

That still doesn't explain why it's happening in the first place, nor why it's happening at all.

Oh and by the way, you never answered this question neither:

2) Further, to (1), it doesn't say why not to use upgrade in lieu of dist-upgrade.

All you've said so far is to not use upgrade, but you never answered the question of why, thus, once again, contrary to your claims, no, you have not "dealt" with all my points, given the data and the evidence above.

 

[gfngfn256]

1. No need to get abusive to someone who was only trying to help you.

2. Yes using apt upgrade in PVE can break your system. I never said definitively that this was your situation. But I will say it again NEVER use apt upgrade on a PVE system. This issue has been raised many times & agreeably the docs should contain a more explicit warning.

3. Both links I linked to contain info that can explain the above point 2. You obviously need to sift through them to find the relevant ones. I did.

4. Not sure why you think I would have a problem admitting Proxmox is fragile (I actually don't think it is BTW). I'm not employed or linked to Proxmox Server Solutions GmbH in ANY way.

I was only volunteering my free time to try & help another user. This obviously didn't work out too well.

 

[alpha754293]

1. No need to get abusive to someone who was only trying to help you.

It's not abusive as I am only citing your own replies, back to you.

I never said definitively that this was your situation.

I've dealt with all your points.

See above^.

agreeably the docs should contain a more explicit warning.

I concur with this as well.

I think that it can be helpful as well, to explain to new(er) users why upgrade can break things as well.

Both will be useful/helpful.

(There's a plethora of tech YouTubers that would show people how to install Proxmox and then run apt update && apt upgrade -y (or some variation thereof), which means that ALL of those said tech YouTubers, would be wrong to do this.)

I did.

Congratulations???

You obviously need to sift through them to find the relevant ones.

Then...why not just send the links to the relevant topics rather than ALL threads that's tagged apt upgrade?

If you're going to tell people to use the search, and then you provide the link, I've sent you what the results of said search looks like.

If the actual point of telling people to use the search is that you have to sift through 10 pages of results (cf. below), then telling people to use the search feature really isn't particularly helpful.

Here are some more results.

For the record, Google actually does a relatively decent job of indexing these forums here.

When you search for "proxmox macsec update", this error does not show up in the results, because that is the actual issue.

Furthermore, my other, existing Proxmox systems that are running up to Proxmox 8.3.5, don't have this issue, when I ran apt upgrade.

Therefore; if upgrade is the cause for the issue, as your search results shows, I'm clearly not the only one is using/running upgrade.

But on a fresh/clean install, the moment I run this, it fails.

I actually don't think it is BTW

Precisely because of this.

I was only volunteering my free time to try & help another user.

And I appreciate that.

As I mentioned, my interim workaround for this issue is using Proxmox 7.4-19 (the update finally came through). There were a few differences in my deployment notes (because I wrote it originally on my other cluster that's running Proxmox 8.1.3, but has since been updated to Proxmox 8.3.5.)

So far, the fully virtualised Proxmox cluster, and Ceph is running on the virtual cluster now.

It was strange/odd to see a fresh/clean install of Proxmox hang on MACsec at boot. That was definitely something that I didn't expect would happen.

 

[spirit]

the problem with "upgrade" is that it's only upgrade installed packages.

if an update of a proxmox package have a depend on a new lib not yet installed, it could break it.

(This is different than debian, where the package list is fixed over the whole cycle. Proxmox can add new features and packages during the 8.X cycle)


Not sure if the macsec problem is related.

 

[alpha754293]

the problem with "upgrade" is that it's only upgrade installed packages.

if an update of a proxmox package have a depend on a new lib not yet installed, it could break it.

(This is different than debian, where the package list is fixed over the whole cycle. Proxmox can add new features and packages during the 8.X cycle)


Not sure if the macsec problem is related.

Thank you.

I was under the impression though, that apt would be able to identify any dependencies and install those as well, when needed, no?

Like when I go to run apt install -y python3, it pulls down all of the dependencies and install those as well.

(I'm trying to think of a package, like nfs-common or something like that -- something that comes pre-installed when you install Proxmox, such that when you run upgrade, that it will see that there is an update for that package, and see that there are updates to its dependencies as well, and update both. There are many times where, when I just run upgrade that it will update a whole bunch of stuff, some of which may be dependencies for other packages as well, but it also sees it as an updated version, that even if it was a dependency for something else, this package will still be updated anyways. Like if package a depends on package b, but it sees that package b has an update, then it will upgrade package b regardless of whether you're upgrading package a or not. But if you're upgrading package a, then I think that it will also, automatically, upgrade package b as well, if package b has an update as well.)

I could be wrong.

Again, so many times, I would just run upgrade so it would just upgrade everything.