container-suseconnect doesn't do any caching of registration

[fcrozat]

When running SLE Base Image (15 SP3) on a SLES host:

each zypper call results to a container-suseconnect call to "register" the container against SCC. This takes usually between 15 to 20s. This call is not cached at all, even if the repositories were properly added to the container.

For instance, starting from new container:

• zypper lr => wait 20s
• all SLE 15 SP3 repositories are properly added to the container
• zypper in iptables
• container-suseconnect is called again and spend 20s to re-register the container (while it is still registered)
• then packages are downloaded and installed.

It seems there is no caching of registration, unlike on a regular SLE system.

Those delays are not visible at all when container-suseconnect is disabled, which is bad as user experience for our customers.

[alexandrevicenzi]

In my test (SP5) the service refresh for container-suseconnect is fast (< 1s).

Caching introduces a potential issue. What if the host system license expires or is revoked? We still need to validate every time container-suseconnect is invoked, which is a call to SCC API and might take a while.