summaryrefslogtreecommitdiffstats
path: root/patches/fuel-astute
AgeCommit message (Collapse)AuthorFilesLines
2016-09-06Revert "EFI: Move patches to Fuel@OPNFV, upstream prep"Alexandru Avadanii1-0/+43
This reverts commit dff8f1a78db4a04dd30c2e0ac03a36cb0b198aa7. Change-Id: I317e0f6aa7665c28035307149e6e7d42fdf508f3
2016-08-28EFI: Move patches to Fuel@OPNFV, upstream prepAlexandru Avadanii1-43/+0
Now we can kill fuel-astute submodule. Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-07-18fuel-astute: Erase EFI boot entry on EFI systemsAlexandru Avadanii1-0/+43
On EFI-enabled systemd, grub-install from grub-efi-* package installs a boot entry named "ubuntu". Since this boot entry is saved in board flash memory, erasing the MBR bootloader code and/or partition signature will not clear the ubuntu boot entry, leaving it pointing to a loader on the ESP (EFI System Partition) that will try to load the kernel/initrd from an erased partition. In Fuel 8.0, the whole disk was erased, so the ubuntu EFI boot entry was skipped due to missing ESP, while for Fuel 9.0 and above we have to explicitly remove it to keep the system in a sane state. Note: efibootmgr is installed automatically on EFI systems as a dependency of grub-efi-*. Closes: ARMBAND-47 Change-Id: If715e960dfd96df807abb0e26f4b7604624ac408 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-06-12Rework: Move fuel-astute patch to post-install.Alexandru Avadanii1-31/+0
IMPORTANT: Drop `fuel-astute` submodule, and patch it instead during the Fuel Master node bootstrapping process, using an OPNFV post.d script. Luckily, this fits well with the recently added script that prepares FM for cross-building. One step closer to un-forking. Change-Id: Ia612e0ad4077b16baf54f1b9ebf9d207daca0be4 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-16Rebase: p/fuel-astute: Reduce patch context.Alexandru Avadanii1-3/+1
Change-Id: Ic11f7c4caa801df32d12461b39e10df8f07460a7
2016-05-16Fix improperly exported patchesStanislaw Kardach1-0/+0
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
2016-05-10Increase maximum shell command timeout to 2hStanislaw Kardach1-0/+33
Since `execute_shell_command` mcagent is used for building the target image and the timeout provided in the astute task is just respected on the Astute level (on mcollective level this timeout is actually a minumum between value provided and ddl value) we need to increase it for Armband operation. Because Armband builds the target image via `qemu-debootstrap`, it can take more than 1 hour to finish the building. Therefore aside of increasing the timeout in the Astute task, the maximum timeout value for mcagent has to be increased. Change-Id: Iab94e794e36bb7e887e8f334daa46e82fe0c6f94 Signed-off-by: Stanislaw Kardach <stanislaw.kardach@caviumnetworks.com>