sles12.1 repository problems

SUSE Public Cloud Azure
1

Hi,

We are working on Azure and our zypper suddenly stop working.
It seems that the directory /repo/SUSE/Updates/SLE-SERVER is missing on 104.45.147.201 (as it seems by usng a web browser) and therefore the zypper reports :

Refreshing service ‘SMT-http_smt-azure_susecloud_net’.
Refreshing service ‘cloud_update’.
Error building the cache:
[SMT-http_smt-azure_susecloud_net:SLES12-SP1-Pool|http://smt-azure.susecloud.net/repo/SUSE/Products/SLE-SERVER/12-SP1/x86_64/product?credentials=SMT-http_smt-azure_susecloud_net] Valid metadata not found at specified URL
Warning: Skipping repository ‘SLES12-SP1-Pool’ because of the above error.
Retrieving repository ‘SLES12-SP1-Updates’ metadata …[error]
Repository ‘SLES12-SP1-Updates’ is invalid.
[SMT-http_smt-azure_susecloud_net:SLES12-SP1-Updates|http://smt-azure.susecloud.net/repo/SUSE/Updates/SLE-SERVER/12-SP1/x86_64/update?credentials=SMT-http_smt-azure_susecloud_net] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository ‘SLES12-SP1-Updates’ because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data…
Reading installed packages…
No updates found.

Please advice

2

Hi,

Sorry for the trouble. We have been experiencing intermittent issues with the update infrastructure in US East. We are working to restore the service and expect this to be complete sometime today July, 12, 2016.

3

All data on the update servers has been restored and updates should work as expected.

Sorry for the trouble and thanks for your patience. We have collected data and hope to be able to find a root cause for the trouble in this region. This should eventually lead us to avoid such issues in the future.