Fixes from the changes that introduced non-LUKS encryption support

[alexgg]

---

Contributor checklist

• Changes have been tested
  • Covered in automated test suite
  • Manual test case recorded
• Change-type present on at least one commit
• Signed-off-by is present
• The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

[alexgg]

This seems to still not work in my testing, though it could be unrelated to these changes.

Nov 27 23:40:55 0c2afc1 bash[9627]: ++ get_part_number_by_label vda resin-boot
Nov 27 23:40:55 0c2afc1 bash[9627]: ++ DEVICE=vda
Nov 27 23:40:55 0c2afc1 bash[9627]: ++ LABEL=resin-boot
Nov 27 23:40:55 0c2afc1 bash[9627]: ++ FIELD=label
Nov 27 23:40:55 0c2afc1 bash[9628]: ++ lsblk /dev/vda -nlo name,label
Nov 27 23:40:55 0c2afc1 bash[9629]: ++ grep resin-boot
Nov 27 23:40:55 0c2afc1 bash[9630]: ++ sed -e 's,^vdap\?\([0-9][0-9]*\)[ \t]*resin-boot$,\1,'
Nov 27 23:40:55 0c2afc1 bash[1097]: + efibootmgr --create --disk /dev/ --part 'resin-boot  resin-boot' --label balenaO>
Nov 27 23:40:55 0c2afc1 bash[9631]: invalid numeric value resin-boot  resin-boot
Nov 27 23:40:55 0c2afc1 bash[1097]: + fail 'Failed to run secureboot post installation steps.'
Nov 27 23:40:55 0c2afc1 bash[1097]: + error 'Failed to run secureboot post installation steps.'
Nov 27 23:40:55 0c2afc1 bash[1097]: + PRIORITY=3
Nov 27 23:40:55 0c2afc1 bash[1097]: + log ERROR 'Failed to run secureboot post installation steps.'

@jakogut please try again with the latest changes - re-running tests also now

[alexgg]

New test run