sure! Basically I added some Gen9 blades part of C7000 enclosures managed by HPE Oneview, into a standalone Ironic installation.
Following a clean-up of the node, I discovered that Ironic failed during clean-up, and I opened https://storyboard.openstack.org/#!/story/2008717 to track this.
The reason for the failure is Ironic trying to wipe read only file systems such as the VID.
To work around Ironic clean-up, I am deactivating, through HPE Oneview, the VID setting. The "exact step" I followed to deactivate VID was to run an Ansible playbook to deactivate the server profile, using parameter:
```
bios: manageBios: true overriddenSettings:
- id: VirtualInstallDisk value: Disabled
...
```
At this point I tried to provide the node, but it failed and I opened this ticket.
However, missing from this ticket: I think at this step the server was in bad shape and "lost" somehow, its configuration. It needed a few reboots and the server profile to be forced (re applied?) again from Oneview.
Following the re-application of the server profile, the blade works just fine.
I think I have only a couple of blades configured with VID enabled.
sure! Basically I added some Gen9 blades part of C7000 enclosures managed by HPE Oneview, into a standalone Ironic installation. /storyboard. openstack. org/#!/ story/2008717 to track this.
Following a clean-up of the node, I discovered that Ironic failed during clean-up, and I opened https:/
The reason for the failure is Ironic trying to wipe read only file systems such as the VID.
To work around Ironic clean-up, I am deactivating, through HPE Oneview, the VID setting. The "exact step" I followed to deactivate VID was to run an Ansible playbook to deactivate the server profile, using parameter:
manageBios : true
overridden Settings:
value: Disabled
```
bios:
- id: VirtualInstallDisk
...
```
At this point I tried to provide the node, but it failed and I opened this ticket.
However, missing from this ticket: I think at this step the server was in bad shape and "lost" somehow, its configuration. It needed a few reboots and the server profile to be forced (re applied?) again from Oneview.
Following the re-application of the server profile, the blade works just fine.
I think I have only a couple of blades configured with VID enabled.