You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default the plugin will do an autoattach. If this fails, the plugin just prompts again for a username and password, giving the wrong impression about why the registration failed.
Long version:
So when doing a "vagrant up" I get prompted for username and password, and then after a longish pause I get "Invalid username/password. Try again". I type it again, and after another pause get prompted again...
To see what was going on I ssh-ed in to may vagrant box and I could subscribe manually, but if I do subscription-manager attach --auto I get
"Unable to find available subscriptions for all your installed products."
And this I got after a pause that was more or less the same duration as I got earlier.
So I assume that this is what is causing the registration to fail.
So my conclusion is that the registration failed because autoattach failed. In that case it would be nice if the plugin would respond with a better error message.
The text was updated successfully, but these errors were encountered:
By default the plugin will do an autoattach. If this fails, the plugin just prompts again for a username and password, giving the wrong impression about why the registration failed.
Long version:
So when doing a "vagrant up" I get prompted for username and password, and then after a longish pause I get "Invalid username/password. Try again". I type it again, and after another pause get prompted again...
To see what was going on I ssh-ed in to may vagrant box and I could subscribe manually, but if I do subscription-manager attach --auto I get
"Unable to find available subscriptions for all your installed products."
And this I got after a pause that was more or less the same duration as I got earlier.
So I assume that this is what is causing the registration to fail.
Adding:
config.registration.auto_attach = false
config.registration.pools = ['']
to my vagrant file made the problem go away.
So my conclusion is that the registration failed because autoattach failed. In that case it would be nice if the plugin would respond with a better error message.
The text was updated successfully, but these errors were encountered: