Unsolved
1 Rookie
•
17 Posts
0
216
OME v4.0 as OpenStack Instance - can't install plugin and update devices
Hello,
I have installed (from scratch, it's not a migration) OME v4.0 (KVM format) as an instance in OpenStack (Antelope 2023.1). It is running, but as of now I can't install plugins or update the connected devices.
EDIT: same issues on Proxmox 6.x
Plugins - The OME VM is not configured with enough disk space
When trying to install plugins, for example Power Manager, even if the instance is connected to a 830 GB volume (and the resources are available on the compute/storage/etc nodes) , there is an error:
Appliance resources are not sufficient to either install or continue to run the Power Manager plugin efficiently: The OME VM is not configured with enough disk space to support this plugin. 400 GB of disk space must be allocated to the VM to support the appliance and all plugins (including this one). The VM has 0 GB allocated, 400 GB is required for the appliance and all other installed plugins
The same setup has been used for OME 3.10 and I was able to install plugins
Updates - Mount of remote share failed.
When trying to update a device, it fails with an error about remote shares. The same happens with OME 3.10. It happens with all the devices, even if OME-iDRAC device is allowed on all ports, and with both CIFS/HTTPS Built-in Appliance Share
Jobs example
Results :Target System: REDACTEDMessages:RunningVerifying if the device Service Tag is valid.The device Service Tag is valid.Starting communication with the device.Update allowed in target, System Lockdown status = DISABLEDChecking Remote LC Services availabilityRemote LC Services are ready nowperformIDRACUpdate(): Attempting to initiate/stage iDRAC payload instance: DCIM:INSTALLED#iDRAC.Embedded.1-1#IDRACinfoInitiated Status check for Job ID : REDACTEDJob state for REDACTED is NEWJob state for REDACTED is DOWNLOADINGJob state for REDACTED is FAILEDMount of remote share failed.Task Failed. Completed With Errors.
DELL-Young E
Moderator
Moderator
•
3.9K Posts
0
November 23rd, 2023 02:26
Hello thanks for choosing Dell.
OME deployment on OpenStack is not officially supported or tested.
https://dell.to/47IZEnQ (not found here)
Even if the deployment is successful, customers may or may not encounter issues such as the one highlighted in your post.
Respectfully,
wndf
1 Rookie
1 Rookie
•
17 Posts
0
November 23rd, 2023 08:06
@DELL-Young E I know OpenStack is not explicitly supported, but deployment in KVM is - and under the hood OpenStack uses libvirt, instances are just KVM machines. If it may be of interest, I had the same issues on Proxmox 6.x, that is an interface for setting up VMs with qemu/libvirt
frigo_
1 Rookie
1 Rookie
•
22 Posts
1
January 3rd, 2024 09:30
can you try with
openstack image set --property hw_disk_bus=sata --property hw_firmware_type=uefi
(and reinstall)
damirlukic
1 Rookie
1 Rookie
•
3 Posts
0
March 11th, 2024 08:52
@frigo_ Thank you, you saved the day!
This one resolved issue when OME was not able to boot.
--property hw_firmware_type=uefi
And second command resolved issue when disk was not visible...
--property hw_disk_bus=sata
All of this can be also set in Openstack -> image settings in web, by adding them in metadata.
Best Regards,
Damir
(edited)
QuantumQuill
1 Rookie
1 Rookie
•
2 Posts
0
April 10th, 2024 08:14
Apologies to hijack this thread but we're unable to even get OME 4 running under Openstack, I was hoping someone would have any suggestions / instructions on how to launch this.
We're understanding it may not work as expected, however we have OME 3.10 working fine but 4 won't boot at all.
Thanks in advance
malbandoz
1 Rookie
1 Rookie
•
1 Message
0
July 5th, 2024 16:51
@QuantumQuill
We got the image running but we get an error saying, "Guest has not initialized the display (yet)." We currently only have the first qcow2 loaded.
The commands we ran,
openstack image create --disk-format qcow2 --container-format bare --public --file openmanage_enterprise.qcow2 openmanage
openstack image set --property hw_disk_bus=sata --property hw_firmware_type=uefi openmanage
Lastly, from the Dashboard, we launched an instance from the image, giving it Volume Size (GB) of 415.