The reboot_notify provider needs to check for more edge cases

Description

I've been unable to repeat the issue, but we have had reports of reboot_notify failing in post_resource_eval without providing any useful information.

I've taken a look at the code and there are a few places where we could be more defensive and provide messages to the users when something doesn't work correctly. The resource should not ever fail without us understanding why and letting the user know what is going on.

Acceptance Criteria

None

Labels

None

Epic Link

None

Story Points

2

Components

Sprint

None

Affects versions

Priority

Medium
Configure