Update to 13.0-U2 does not Appear on All Servers

[eewiz]

I have two servers running 12.0-U8.1.
One looks like this:

The other looks like this:

I have to change the Train on the other server to get this:

Which produces this ominous warning:
This is not a production release, and should only be used for testing.

Does anyone know why I get different behavior from the two servers?
As can be seen above, both servers are running 12.0-U8.1.

Thank You

 

[eewiz]

Well, now, today, the other server has changed to offering the upgrade up-front just like the first server.
So, at this point, I have to assume that iX has captured some kind of serial number from each installed server.
It appears that they stagger release of upgrades to each individual server serial number.
And, only so many servers per day.

For those that rely on Truenas as an appliance, that is supposed to work reliably.
Having anomalous behavior between two different servers as described above, is extremely confusing.

All for now.

 

[morganL]

Well, now, today, the other server has changed to offering the upgrade up-front just like the first server.
So, at this point, I have to assume that iX has captured some kind of serial number from each installed server.
It appears that they stagger release of upgrades to each individual server serial number.
And, only so many servers per day.

For those that rely on Truenas as an appliance, that is supposed to work reliably.
Having anomalous behavior between two different servers as described above, is extremely confusing.

All for now.

One was running TrueNAS CORE

I think the other was running TrueNAS Enterprise.

We delay automatic updates on Enterprise. THey are available manually, but not automatically. THe primary reason is that Enterprise is regularly used in mission-critical environments and needs more field testing.

 

[eewiz]

Hello morganL,

I'm sorry to contradict, but both servers are identical.

Thank you very much for replying.
At this point, this question is probably moot.
I will now better recognize this behavior if it is again seen in the future.
Now, my next burning question is.
How to upgrade these to 13 while maintaining the integrity of passphrase encrypted datasets.
I have posted another thread presenting that question.

Thank You