Age | Commit message (Collapse) | Author | Files | Lines |
|
Armband requires a custom kernel on baremetal nodes (kvm, cmp).
However, the repos (configured as part of `linux.system` high state)
were added before installing the kernel only for cmp nodes.
Change-Id: Ie8d6e9cf4eaa84c459a70112ef002d09be9c4cf4
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Id4b6c37d6814458600e2554f96e4580b126f1b63
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Iaaea7494b960b05c4e409eb52daa6b0fa6414e12
Signed-off-by: Charalampos Kominos <Charalampos.Kominos@enea.com>
|
|
The Salt way to pin the kernel version is via its reclass model, by
defining system.kernel.version. However, this only works with
explicit kernel package names and not with meta package names
(e.g. linux-image-4.13.0-9916-generic is expected instead of
linux-image-generic-hwe-16.04-edge, which would break the
`linux_kernel_old_absent` state).
For now, let's explicitly call `pkg.install` for the kernel and
headers packages, using the meta package name to ensure automatic
fallback to Ubuntu packages if Armband repos are missing,
respectively to automatically pick up new kernel package names
in case of meta + kernel packages bump later.
JIRA: ARMBAND-280
Change-Id: I5448df1de1b3c211583708402b5c7497df92fc16
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|