Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Catch-22 with failed Rock-ons #1216
It's possible to end up in nasty catch-22s when rock-ons fail.
I was trying to rig an alternative
When I corrected my json, Rockstor would not refresh because I wasn't allowed to change the port mappings of installed rock-ons and told me to uninstall first. But there was nothing to uninstall. After all, installation had failed. There seems to be no way offered out of this catch-22.
I only got myself unstuck by firing up
The simplest way to fix this would probably be to suppress these port consistency checks when Rock-on installation (as opposed to start-up) has failed. However, there may be more edge cases like this. Given the data duplication between Rockstor's state recorded in
I too had an issue with how Rockstor handles the port verification. In my case, if another rockon has a recommended port value, you cannot assign that port to your rockon. I think the user should be able to use any port regardless of recommendations (as long as the port actually exists/does not have an existing service binding to it).