Then you should have a stable appliance id from one install to the next.
The appliance id (derived from product_uuid or hostid if product_uuid non unique) is akin to a user name while the activation code is like a password so they are a set. Hence my question on if this is a re-install.
If you product_uuid and consequent appliance id has changed then you can get your subscription ‘moved over’ via an email request to firstname.lastname@example.org containing your old and new appliance id. I’m afraid I can’t tend to this myself however.
Much apologies for the inconvenience caused but we depend on subscriptions to aid in maintaining Rockstor’s sustainable stance (at least currently) and it’s usually a fairly smooth process, bar the known hick-up with re-installs on fake product_uuid motherboards.
If you have suspicions about the uniqueness of your product_uuid, and it’s not one of those listed, then you can always private message me here on the forum.
Only one install on this box done over a year ago. The key was purchased on 6/2017 (3-yr key) and it’s been receiving stable channel updates since. This past week is the first time I’ve seen a failure when connecting to the repository and the update checker for the OS runs daily.
I will check on the info you posted above once I get home. But unless this is a recent development (as in problem) I suspect that something else is going on with my subscription.
It may very well be product_uuid related though I have not reinstalled the software so it shouldn’t have changed. If my appliance ID = product_uuid, which is not unique, could someone else with the same fake_uuid receive their own subscription activation code that would in turn invalidate mine?
The code purposefully intends not to use the ‘fake’ non unique product_uuids due to their nature and generates instead a one time unique ‘install specific’ product id but this is of course far less convenient for re-installs due to the major inconvenience of having to request an activation code transfer. But of course we may not have an exhaustive list. And on that note I’ll reply in kind to your:
Thanks again for reporting and helping to work through this one. I suspect we are nearly at it’s cause.