11.3 Beta1 update changes current train

Description

Hi, not sure if this is by design but while running 11.3 Beta1, if i check the update tab with the 11.3 train selected, it suggests moving off the 11.3 train and back to a stable version - 11.2u6.

Thanks

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Dru Lavigne November 13, 2019 at 12:03 AM

thank you for the confirmation.

You're correct, it is due to the CLI command. 11.2-U7 will have code to correct this for users still on the 11.2 train. For now, we've added the correction command to the release notes.

Andrew McCann November 12, 2019 at 10:36 PM

ok, ran the  command, it returned TRUE

midclt call update.set_train FreeNAS-11.3-BETA

 

Checked update again, and it fixed the problem. This may be relevant, I manually updated from 11.2u5 to 11.3Beta from the command line, running the command  freenas-update -T FreeNAS-11.3-BETA update

 

Dru Lavigne November 12, 2019 at 2:01 PM

do these instructions resolve the issue?

After rebooting into the updated system, run this command from the FreeNAS shell to ensure the update train displays correctly:

midclt call update.set_train FreeNAS-11.3-BETA

Andrew McCann November 12, 2019 at 2:11 AM

sorry let me re-word that;

You should not receive updates from different train versions unless you specifically select a different train. Even if its a Beta train I don't think the update should default to previous train version unless you specifically set it to.

 

Thanks

Andrew McCann November 12, 2019 at 2:03 AM

Hi Erin

No, what I think the issue is (if its a issue), if you are on the 11.3 Beta1 train, see screenshot, it should not prompt you to downgrade to the previous and different 11.2 train. To update to 11.2 you should select a different train from the train menu, hope that makes sense.

Thanks

Duplicate

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created November 11, 2019 at 11:41 PM
Updated July 1, 2022 at 4:43 PM
Resolved November 13, 2019 at 12:03 AM