Hi,

I realize this is from 3 years ago, but is this still the current update infrastructure?

I have inherited a few servers that are SLES 11 SP2 and I am getting the following error for all repositories that use "default-ec2-update.susecloud.net". I think the update script has not been run on the affected servers, would it still work or have there been additional changes, etc?

"
Warning: Disabling repository '{insert repo name}' because of the above error.
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/{insert repo name}/sle-11-x86_64/repodata/repomd.xml':
Error code: Connection failed
Error message: Couldn't resolve host 'default-ec2-update.susecloud.net'
"

Third party repositories refresh ok -- Nvidia (http://download.nvidia.com/novell/sle11sp2) and the "server-monitoring" (http://download.opensuse.org/reposit...ng/SLE_11_SP3/)


repos with error:
SLE11-SDK-SP1
SLE11-SDK-SP1-Pool
SLE11-SDK-SP1-Updates
SLE11-SDK-SP2-Core
SLE11-SDK-SP2-Updates
SLE11-SDK-SP3-Pool
SLE11-SDK-SP3-Updates
SLE11-SP1-Debuginfo-Pool
SLE11-SP1-Debuginfo-Updates
SLE11-SP2-Debuginfo-Core
SLE11-SP2-Debuginfo-Updates
SLE11-SP2-WebYaST-13-Pool
SLE11-SP2-WebYaST-13-Updates
SLE11-SP3-Debuginfo-Pool
SLE11-SP3-Debuginfo-Updates
SLE11-WebYaST-SP1
SLE11-WebYaST-SP1-Updates
SLE11-WebYaST-SP2-Pool
SLE11-WebYaST-SP2-Updates
SLES11-Extras
SLES11-SP1
SLES11-SP1-Pool
SLES11-SP1-Updates
SLES11-SP2-Core
SLES11-SP2-Extension-Store
SLES11-SP2-Updates
SLES11-SP3-Extension-Store
SLES11-SP3-Pool
SLES11-SP3-Updates

Repo location
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/install/SLE11-SDK-SP1/sle-11-x86_64/media.1/media':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP2-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Pool/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP1-Debuginfo-Pool/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP1-Debuginfo-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP2-Debuginfo-Core/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP2-Debuginfo-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP2-WebYaST-1.3-Pool/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP2-WebYaST-1.3-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP3-Debuginfo-Pool/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-SP3-Debuginfo-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/install/SLE11-WebYaST-SP1/sle-11-x86_64/media.1/media':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP1-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP2-Pool/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP2-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-Extras/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/install/SLES11-SP1/sle-11-x86_64/media.1/media':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP1-Pool/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP1-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP2-Extension-Store/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP2-Updates/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP3-Extension-Store/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP3-Pool/sle-11-x86_64/repodata/repomd.xml':
Download (curl) error for 'http://default-ec2-update.susecloud.net/repo/update/SLES11-SP3-Updates/sle-11-x86_64/repodata/repomd.xml':



Quote Originally Posted by rjschwei View Post
We are happy to announce that a new SUSE update infrastructure is in place in Microsoft Azure. The update infrastructure operated and maintained by SUSE provides updates to instances launched from SUSE released SUSE Linux Enterprise Server on demand images in Microsoft Azure.

Those using the latest images, released on 2014-11-06 or thereafter, will automatically connect to the new infrastructure. Those that have running instances started from images released prior to this date need to switch the instances to the new infrastructure. To switch a running instance follow these simple steps:

-> wget http://104.45.147.201/instanceInfraUpgrade.noarch.rpm

Then as root

# zypper --no-refresh --non-interactive in instanceInfraUpgrade.noarch.rpm
# instanceInfraUpgrade
# rm instanceInfraUpgrade.noarch.rpm

After the update to the new infrastructure "zypper lr" will point to repositories starting with "SMT"

The old infrastructure server will be disabled on June 30, 2015.

-- July 29, 2015 --
I added the '--no-refresh' option to the zypper command to prevent zypper from trying to refresh the repositories. The old update infrastructure was removed on June 30th, as announced. Anyone trying to follow the procedure that still has the old update infrastructure configured will run into issues if the '--no-refresh' option is not used.