- 최신
- 최다 투표
- 가장 많은 댓글
Hello,
Thank you for reaching out with this issue.
This issue occurs when the NoReboot feature is selected and the managed node is patched with a patch that is assigned a status of InstalledPendingReboot. The managed node/s is marked as Non-Compliant. After a reboot occurs and a scan operation is ran, then managed node status is then updated to Compliant status, the Pending Reboot should be cleared. You can refer to the link below for detailed information on this:
As mentioned above, the resolution to this issue is to run a scan against the nodes using the Patch Manager, below are the steps to accomplish this:
- Open AWS System Manager.
- In the navigation pane, choose Patch Manager.
- Choose Patch Now.
- For Patching operation choose Scan.
- For instances to patch ,choose “Patch only the target instances I specify”: You specify which managed nodes to target in the next step and choose your target instances.
- Choose Patch now.
After having performed the scan, you can then confirm if the nodes need are non-compliant and pending reboot.
I hope the information above helps. Thank you.
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전