OS Installation difference between Ansible and Intersight GUI

[kebrant]

There seems to be an issue leveraging the OS install feature of Intersight using Ansible. The issue seems to be that the vmedia (ESXi ISO) does not eject/disconnect after OS install completion (server boots to installation ISO on every subsequent reboot). This works fine via Intersight GUI using the same boot policy, OS config file, SCU link, and OS image link. I'm trying to identify if there's a difference in the API calls when this process is done through the Intersight GUI versus through Ansible/the API. Ansible playbook is attached.
Ansible_os_install-redacted.yml.txt

[dsoper2]

I've updated the os_install.yml example with requests that successfully unmount vmedia and restore boot order. I don't see any major differences from the example in this issue. What does the UI requests page show when you see the vmedia stay mounted?

[kebrant]

The last couple of executions have worked as expected. We will continue to monitor and report back, thank you.