[2.3] When a machine fails and the oauth token gets expired, it may traceback
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned |
Bug Description
A machine failed to access the repository, it was marked as 'Failed commissioning' and after that the logs show the following (my guess is that maas tried to save cloud-init messages but the oauth token had already expired).
This is really bad because it leads the user to believe that there's a nasty failure in MAAS when in reality it is not a failure.
2018-03-27 13:17:44 regiond: [info] 100.99.5.14 POST /MAAS/metadata/
2018-03-27 13:17:44 regiond: [info] 100.99.5.14 POST /MAAS/metadata/
2018-03-27 13:17:45 maasserver: [error] #######
2018-03-27 13:17:45 maasserver: [error] #######
2018-03-27 13:17:45 maasserver: [error] Traceback (most recent call last):
File "/usr/lib/
consumer, token, parameters = self.validate_
File "/usr/lib/
return oauth_server.
File "/usr/lib/
token = self._get_
File "/usr/lib/
raise OAuthError('Invalid %s token: %s' % (token_type, token_field))
piston3.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
response = wrapped_
File "/usr/lib/
return view_atomic(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
response = upcall(request, *args, **kwargs)
File "/usr/lib/
response = func(*args, **kwargs)
File "/usr/lib/
actor, anonymous = self.authentica
File "/usr/lib/
if not authenticator.
File "/usr/lib/
raise OAuthUnauthoriz
maasserver.
Changed in maas: | |
milestone: | none → 2.4.0beta2 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
milestone: | 2.4.0beta2 → 2.4.0beta3 |
Changed in maas: | |
milestone: | 2.4.0beta3 → 2.4.0rc2 |
Changed in maas: | |
milestone: | 2.4.0rc2 → 2.5.x |
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team