Unable to change boot environment on SCALE 21.08-BETA.2 via midcli
Description
Problem/Justification
Impact
Activity
Lucas Gautier October 28, 2021 at 4:25 AM
Confirmed this issue is now fixed on 22.02-RC.1. Attached a screenshot showing successful change via midcli. This should be OK to close.
Should have waited for RC.1 but oh well!
Lucas Gautier October 28, 2021 at 4:11 AM
Just attempted to recreate 21.08-BETA.2 but this version is not available since the release of 22.02-RC.1. I will attempt to re-create the issue on 22.02-RC.1.
Lucas Gautier October 28, 2021 at 3:47 AMEdited
Update 2021-10-27 11:34PM:
This sub-issue is also resolved on 22.02-RC.1. The UI can successfully delete/activate bootenvs. The UI and zectl are now in sync (as expected).
Been trying to re-create the issue on this bug ticket - but having issues managing boot environments at /ui/system/boot - having to use zectl exclusively since the UI is not allowing the deletion of older boot environments (to free up boot pool space). My next attempt will be creating a new 21.08-BETA.2 bootenv from 21.08-BETA.1 and will retry the bootenv change via midcli (not zectl or UI).
Please let me know if a separate bug should be opened for being unable to activate or delete boot environments at /ui/system/boot on 21.08-BETA.1 - a separate issue discovered ( a debug bundle for this separate issue has been saved):
Selecting "Delete" doesn't remove the bootenv, zectl list shows the bootenv as available/existing
UI throws no errors of being unable to delete a bootenv
Selecting "Activate" does not operate reliably: some attempts display an error/stacktrace of being unable to activate a bootenv and sometimes the bootenv would successfully change (as expected)
zectl appears to be the only reliable method to manage bootenvs, the UI does not appear to reliably function
Bonnie Follweiler October 25, 2021 at 7:57 PM
Hello @Lucas Gautier,
Would you please recreate the issue and then run a debug? Thank you!
Lucas Gautier October 25, 2021 at 7:41 PM
The SCALE system was reverted to 21.08-BETA.1 and been running on this version for ~1 day to restore functionality.
Does the error need to be replicated on 21.08-BETA.2 and then request the debug file?
An error occurred with network access that caused the webUI to become lost. The system was recently upgraded to 21.08-BETA.2 via the UI. The webUI was no longer accessble and attempts to revert back to 21.08-BETA.1 bootenv via the bundled cli failed.
Steps to reproduce:
1. Access the system via direct console (networking was down, could not SSH)
2. Via the CLI: [truenas]> system bootenv activate id="21.08-BETA.1"
This exception is thrown: https://github.com/truenas/middleware/blob/master/src/middlewared/middlewared/plugins/bootenv.py#L171
A stacktrace was not captured since the system was accessed via IPMI console (no copy/paste).
Workaround Used:
1. Dropped to root shell to run zectl directly
2. truenas# zectl activate 21.08-BETA.1
3. truenas# reboot now
Successful reboot into 21.08-BETA.1 and webUI access was restored. Expected "official CLI" to be able to change the boot enviornment.