SUSE Image - Getting prompted for SMT username and password

[Richard Craig]

Anybody else run into this issue?

What steps will reproduce the problem?
1. login via SSH to SUSE VM
2. run 'sudo zypper install python'

What is the expected output? What do you see instead?

It should install python. This is what I'm seeing:

richard_ubusha_co_za@onaware-lab-ags:~> sudo zypper install python
Authentication required for 'http://smt-gce.susecloud.net/repo/$RCE/SLE11-SDK-SP3-Pool/
sle-11-x86_64?credentials=NCCcredentials'
User Name: guest
Password: 
Login failed. (http://smt-gce.susecloud.net/repo/$RCE/SLE11-SDK-SP3-Pool/sle-11-x86_64/
repodata/repomd.xml?credentials=NCCcredentials): The requested URL returned error: 401
Abort, retry, ignore? [a/r/i/? shows all options] (a): 

What version of the product are you using? On what operating system?

naware-lab-ags:~> cat /etc/SuSE-release 
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3

Please provide any additional information below.

Initial when I deployed the VM I could install software. Now I'm getting this issue.

I also created a new SUSE image but when I run 'sudo zypper repos' it tells me there are no repos.

richard_ubusha_co_za@test-smt:~> sudo zypper reposNo repositories defined. Use the 'zypper addrepo' command to add one or more repositories.

---

Ubusha Technologies is a member of the Aptronics Group

See:  http://www.aptronicsgroup.com/

View disclaimer at http://www.ubusha.co.za/Home/terms-and-conditions/maildisclaimer

---

[Kevin Peter Gade]

Hi,
I am having the same issue.
I could install and update software when I initially set up my instance.

Now I am getting this:
Login failed. (http://smt-gce.susecloud.net/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials): The requested URL returned error: 401

Kind Regards,
Kevin

[Robert Schweikert]

On Wednesday, October 1, 2014 4:07:38 AM UTC-4, Richard Craig wrote:

Anybody else run into this issue?

What steps will reproduce the problem?
1. login via SSH to SUSE VM
2. run 'sudo zypper install python'

What is the expected output? What do you see instead?

It should install python. This is what I'm seeing:

richard_ubusha_co_za@onaware-lab-ags:~> sudo zypper install python
Authentication required for 'http://smt-gce.susecloud.net/repo/$RCE/SLE11-SDK-SP3-Pool/
sle-11-x86_64?credentials=NCCcredentials'
User Name: guest
Password: 
Login failed. (http://smt-gce.susecloud.net/repo/$RCE/SLE11-SDK-SP3-Pool/sle-11-x86_64/
repodata/repomd.xml?credentials=NCCcredentials): The requested URL returned error: 401
Abort, retry, ignore? [a/r/i/? shows all options] (a): 

What version of the product are you using? On what operating system?

naware-lab-ags:~> cat /etc/SuSE-release 
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3

Please provide any additional information below.

Initial when I deployed the VM I could install software. Now I'm getting this issue.

Is this an issue that occurs in an instance that was started prior to last Saturday or is this a brand new instance?

If the instance is a bit older you may have run into a problem that was created by changes to the SUSE update mirrors. Re-registering the image should do the trick. Use the following steps (as root):

-> suse_register -E

remove the last 2 lines from /etc/hosts

-> /etc/init.d/guestregister start

If all goes well the repositories will be restored and you should be back in business.

[Robert Schweikert]

On Wednesday, October 1, 2014 4:42:07 PM UTC-4, Kevin Peter Gade wrote:

Hi,
I am having the same issue.
I could install and update software when I initially set up my instance.

Now I am getting this:
Login failed. (http://smt-gce.susecloud.net/repo/$RCE/SLES11-SP3-Updates/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials): The requested URL returned error: 401

Kind Regards,
Kevin

Yes, basically would be the same problem, please try the re-registration steps.

[Richard Craig]

Hi Robert

Thank you for your response.

I tried the steps listed below. Sadly it does not seem to be working. Please see the following output:

Let me know if there is any other information I can provide.

Kind regards

Richard

[Robert Schweikert]

On Thursday, October 2, 2014 3:57:50 AM UTC-4, Richard Craig wrote:

Hi Robert

Thank you for your response.

I tried the steps listed below. Sadly it does not seem to be working. Please see the following output:

---

---

Hi Richard,

That the guest verification fails is most likely due to the fact that you end up at the wrong update server. Please post the the last line of /etc/hosts and let me know which region you are running the instance in.

Thanks,
Robert

[Richard Craig]

Hi Robert 

The zone for the server is europe-west1-a.

Please find the contents of the hosts file below:

#

# hosts         This file describes a number of hostname-to-address

#               mappings for the TCP/IP subsystem.  It is mostly

#               used at boot time, when no name servers are running.

#               On small systems, this file can be used instead of a

#               "named" name server.

# Syntax:

#    

# IP-Address  Full-Qualified-Hostname  Short-Hostname

#

127.0.0.1       localhost

# special IPv6 addresses

::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix

ff02::1         ipv6-allnodes

ff02::2         ipv6-allrouters

ff02::3         ipv6-allhosts

# Added by SMT registration do not remove

192.158.29.172  smt-gce.susecloud.net   smt-gce

~                                        

[Robert Schweikert]

Hi,

On Thursday, October 2, 2014 6:20:47 AM UTC-4, Richard Craig wrote:

Hi Robert 

The zone for the server is europe-west1-a.

Please find the contents of the hosts file below:

#

# hosts         This file describes a number of hostname-to-address

#               mappings for the TCP/IP subsystem.  It is mostly

#               used at boot time, when no name servers are running.

#               On small systems, this file can be used instead of a

#               "named" name server.

# Syntax:

#    

# IP-Address  Full-Qualified-Hostname  Short-Hostname

#

127.0.0.1       localhost

# special IPv6 addresses

::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix

ff02::1         ipv6-allnodes

ff02::2         ipv6-allrouters

ff02::3         ipv6-allhosts

# Added by SMT registration do not remove

192.158.29.172  smt-gce.susecloud.net   smt-gce

~                                        

This is correct, you are pointing at the update server in that region. But for some reason the API that verifies that you are running a SUSE released instance is telling me you are not. This is something I cannot investigate from my end and will have to be double checked in the Cloud Framework. I'll see if I can get someone to look at that. We'll need the external IP address of the instance.

Thanks,
Robert


 

     

---

 

 

[Robert Schweikert]

Investigation into the issue continues Google and SUSE are working together to find the root cause of the problem. The problem only occurs in the europe region and at this point appears to be permission related.

Hopefully this issue can be resolved soon, sorry for the inconvenience.

Will keep you posted as things progress.

[Robert Schweikert]

Hi,

The issue is now resolved.

The root cause was a permission issue in accessing an API provided by Google. This permission issue was triggered by a missing command line argument when the update servers had to be rebuilt and restarted recently.

Sorry that this took a while to figure out.

[Kevin Peter Gade]

I can confirm that it is working again here.

Thank you.

Kind Regards,
Kevin