You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DTS doesn't allow updating to the latest community version when credentials with access to heads firmware are loaded
How reproducible
No response
How to reproduce
Install outdated Dasharo on a platform, which has a more recent community version as well as Heads (e.g. MS-7D25)
Load DPP keys with access to Heads fw
Select 2) Update Dasharo Firmware
Answer n to Would you like to switch to Dasharo heads firmware? (Y|n)
Expected behavior
You should be able to update to the latest community version
Actual behavior
No update available for your machine
Press Enter to continue
Credentials need to be removed in order to update to community version.
Screenshots
No response
Additional context
Before updating, DTS chooses the appropriate firmware version to be installed. However, it only chooses one version with Heads being the priority. That is why no other available versions are displayed.
Component
Dasharo Tools Suite
Device
other
Dasharo version
No response
Dasharo Tools Suite version
v2.1.3
Test case ID
No response
Brief summary
DTS doesn't allow updating to the latest community version when credentials with access to heads firmware are loaded
How reproducible
No response
How to reproduce
MS-7D25
)2) Update Dasharo Firmware
n
toWould you like to switch to Dasharo heads firmware? (Y|n)
Expected behavior
You should be able to update to the latest community version
Actual behavior
Credentials need to be removed in order to update to community version.
Screenshots
No response
Additional context
Before updating, DTS chooses the appropriate firmware version to be installed. However, it only chooses one version with Heads being the priority. That is why no other available versions are displayed.
https://github.com/Dasharo/dts-scripts/blob/983f6bf79d73b4622989160d59b2deb04fbfbe0b/scripts/dasharo-deploy#L204-L217
Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: