I’ve no problems with giving them room to fix it, but this should have never showed up in a major release. ZFS root on Linux has had major pushes into the consumer base over the past few years, especially so with the Ubuntu releases. I’m not directly blaming the developers because bugs do happen, but I do have problems with the poor QA that leads to a showstopper bug like this showing up in a release.
I’d call it a one off, but the vast majority of the major bugs that came with 1.8 could have been easily caught with proper testing. If you’re going to support a platform, you absolutely need to be doing the basic tests with every major distribution and probable configuration. It takes time and effort, but it reduces the lost of revenue from cancelled subscriptions.
Instead they have a portion of their paying user base stuck without the software/service for which they’ve payed, and for an extended period of time. If this were a free software/service, I’d rage a bit then shrug. But this is not an overly cheap piece of software to run, especially so for those of us who put out the chunk of change for the lifetime.
But yes, there is not much we can do other thank sit back and wait.
p.s. I come from industries where five nines uptime is the way of life, so my rage gronks are related to personal and business ideals.