The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal.
Hey @sat could you please explain why the SHA256 for HostOS and SetupOS is not provided in the payload of the proposal now that the script displays results for them?
At the time of this comment on the forum there are still 2 days left in the voting period, which means there is still plenty of time for others to review the proposal and vote independently.
We had several very good reviews of the Release Notes on these proposals by @Zane, @cyberowl, @ZackDS, @massimoalbarello, and @ilbert. The IC-OS Verification was also performed by @Gekctek and @tiago89. I recommend folks talk a look and see the excellent work that was performed on these reviews by the entire CodeGov team. Feel free to comment here if you have any questions or suggestions.
There were no major concerns identified with these proposals, but there were a few comments left on GitHub for the change owner of each respective commit as recommended last week by @christian (thank you for the suggestion)… Suggestion by @Zane Question by @ilbert Question by @ilbert Typo found by @ilbert
All 14 System Canister Management proposals were verified and reported here by @ZackDS this week. These proposals included upgrades to the NNS canister, internet identity, the NNS dApp, ICP Index canister, ckBTC minter canister, ckBTC KYT canister, ckBTC Ledger canister, ckBTC Archive canister, Governance canister, SNS-wasm canister, cycles-minting canister, and SNS swap canister as described elsewhere on the forum here and here.
@ilbert Upgrade process supports both .gz (gzip) and .zst (Zstandard - Real-time data compression algorithm). It was like this for a while but we never switched the guest (replica) upgrades to zst since we considered it to be a risk. However, most of our tests are now using .zst primarily and we also fully tested HostOS upgrades with .zst and not with .gz. So having an upgrade image with .zst was actually less risk (for a change). We’ll probably switch the guest (replica) upgrades to zst as well, in the near future, so that we have less difference between upgrades.
@wpb, it’s a bug in the dashboard, I’ll forward the question to the public dashboard team.
The sha256 sum is showing as expected on the NNS UI: Internet Computer Loading
EDIT: nope, scrap that. I rushed to mark it as a bug. The sha256 sum of the HostOS upgrade package is actually showing well in the proposal
For the SetupOS, however, there is no proposal. So it’s only a wording issue in the verification script. The SetupOS image is downloaded by Node Providers when they want to onboard a new node. So there is no community approval process for this, every node provider decides for him/herself which version they want to install initially. Subsequent node upgrades go through the NNS proposals.
Thanks for the clarification. So I think that the repro-check.sh script needs to be updated accordingly to run checks on .zst files instead of .gz, at least for HostOS.
