Hi Bernd, is the hpe add-on enabled? I just had a similar issue with a different product, running smt-repos <PRODUCT> -e resulted in a message like “0 repositories enabled”. Although the registration code was valid, for an unknown reason I couldn’t enable it and so I also was unable to mirror the repo. I deregistered the product and retried, this time it all worked. I can’t tell you a reason, but maybe a retry works for you, too.
Like in your case, enabling the Helion repos failed. Unlike you, I am not successful deregistering and re-registering the product. I can try a few times more.
Unfortunately, I don’t have a Helion subscription available, so I can’t reproduce it exactly. But maybe you get it working with de- and re-registering, or someone else can shed some light on HPE cloud repos, maybe there’s something else going on.
That would be very weird and not practical at all, also in the past few years I can’t remember that it ever took days. It could be related to the splitting of SUSE from Micro Focus, I can imagine impacts on the IT infrastructure, but I don’t have enough information for such an assumption. Anyway, it’s great that it works now!
That would be very weird and not practical at all, also in the past few
years I can’t remember that it ever took days. It could be related to
the splitting of SUSE from Micro Focus, I can imagine impacts on the IT
infrastructure, but I don’t have enough information for such an
assumption. Anyway, it’s great that it works now! ;-)[/color]
This has nothing to do with the split of SUSE from Micro Focus as
this is all SUSE-related, just likely to have needed
time.
Another note on this topic: make sure you’re using suiting organization credentials for SCC, they have to match the organization for which you enabled the product subscription in SCC. This only applies if you have multiple organizations enabled, of course.