[2.3] django.core.exceptions.ValidationError: ['xenial has no kernels available.']
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
I was booting an arm64 system, but I didn't have any arm64 images imported. The error I saw in the logs was the following. The error shown should not be a traceback but should be a nice message saying something alog the lines that:
"Machine XXXXX attempted to boot [<arch>], but it was not available.
Also, we should show a notification in the UI.
==> /var/log/
2017-07-13 12:15:01 provisioningser
'GetBootConfig' command. [autopkgtest:
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
f(*a, **kw)
File "/usr/lib/
self.
File "/usr/lib/
self.
--- <exception caught here> ---
File "/usr/lib/
current.result = callback(
File "/usr/lib/
key = error.trap(
File "/usr/lib/
self.
File "/usr/lib/
raise self.value.
File "/usr/lib/
result = inContext.theWork()
File "/usr/lib/
inContext.
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
return func_outside_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
None, min_hwe_kernel, '%s/generic' % arch, osystem, series)
File "/usr/lib/
raise ValidationError('%s has no kernels available.' % distro_series)
django.
description: | updated |
Changed in maas: | |
milestone: | none → 2.3.0 |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: error-surface |
Changed in maas: | |
importance: | High → Medium |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.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