This may be related to a bug we had in earlier Rock-on code where we always pulled, unintentionally actually, the ‘latest’ tag. This however was fixed in more recent code. Both the YouTrack and the Jenkins rock-ons are based on specific ‘non latest’ docker images. Hence my suggestion that you may be facing this bug.
Jenkins Rock-on definition:
and the YouTrack official rock-on definition:
This bug was fixed in Stable channel release: 3.9.2-49 in October last year:
Also note that there have been a few other Rock-on related fixes, also listed in that Changelog thread.
I see you have just found a work around, well done. As per the original post in the above Announcements Stable Channel thread we no longer release to the testing channel for our CentOS based offerings. But we do for our pending transition to the ‘Built on openSUSE’ effort. So given you are ‘handy’ at finding the ‘bugs’ you might like to have a look at the following thread:
Hope that helps and thanks for sharing your work around. However the ‘official’ fix was detailed in the referenced issue and pull request from Feb 2019.
Our older Web-UI unfortunately leads one to believe that running Testing channel on the CentOS variant is actually ‘latest’ when in fact it’s over 2 years old now. Again this is something that has been fixed and detailed in that first Announcements thread. We are sort of heading for a re-lanuch with our ‘Built on openSUSE’ effort and so things are a little out of kilter currently. The newer Web-UI now links to our official docs subsection here:
Which is far more up-to-date. But as yet does not mention the ‘early adopters’ availability as it’s really only intended for folks, such as yourself, who can contribute fixes as apposed to just finding them . Then when we have a feature parity with our CentOS Stable channel offering we can embark on moving all our ‘supporters’ and all new users over to the new effort.
Incidentally there was also a bug, way back then, in the testing channel for those moving from that channel to the Stable channel. This was bad as it indicated you were running 3.9.2-* when in fact you were not. See the other Announcement post on this here:
My rockstor version was indeed 3.9.1 as I was not a suscriber yet (and the UI led me to think it was the latest version).
I just suscribed for my physical server, and started the updates, it should be fine then.
One of the main reasons I choose Rockstor for my NAS is because it was CentOs based, which I’m used to work with.
But from minutes of research, it seems openSUSE is not too different. If I can get some time for another new project, I think looking into Rockstor is appealing.