Dell OpenManage in LXC container

[TomTomGo]

Hi,

As there is a big lack of support from DELL to provide fresh OpenManage for Debian, i've tried to install the OpenManage for Ubuntu's version in a LXC container. But installation failed because of some missing privileges i presume.

Jul 18 11:36:43 management systemd[1]: Started User Manager for UID 0.
-- Subject: Unit user@0.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit user@0.service has finished starting up.
--
-- The start-up result is RESULT.
Jul 18 11:36:58 management systemd[1]: Reloading.
Jul 18 11:36:58 management systemd[1]: system-postfix.slice: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: keyboard-setup.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: dbus.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: systemd-networkd.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: user.slice: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: console-getty.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: systemd-journal-flush.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: systemd-logind.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: system-container\x2dgetty.slice: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: systemd-user-sessions.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: accounts-daemon.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: rsyslog.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: networkd-dispatcher.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: ssh.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: dev-hugepages.mount: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: console-setup.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: systemd-tmpfiles-setup.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: postfix.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: systemd-sysctl.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: system-getty.slice: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: cron.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: systemd-journald.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permitted
Jul 18 11:36:58 management systemd[1]: Failed to set devices.allow on /system.slice/systemd-resolved.service: Operation not permitted
Jul 18 11:36:58 management systemd[1]: ufw.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: systemd-update-utmp.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: instsvcdrv.service: Failed to reset devices.list: Operation not permitted
Jul 18 11:36:58 management systemd[1]: Starting Systems Management Device Drivers...
-- Subject: Unit instsvcdrv.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit instsvcdrv.service has begun starting up.
Jul 18 11:36:58 management systemd[1]: instsvcdrv.service: Control process exited, code=exited status=155
Jul 18 11:36:58 management systemd[1]: instsvcdrv.service: Failed with result 'exit-code'.
Jul 18 11:36:58 management systemd[1]: Failed to start Systems Management Device Drivers.
-- Subject: Unit instsvcdrv.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit instsvcdrv.service has failed.

How could we authorize this container to get access to the host hardware in order to manage RAID controller, DRAC, .... ? Or maybe it's not a good idea or there are better solutions ...

Best regards,

 

[Vladimir Bulgaru]

Hey!

AFAIK OpenManage need to have access to bare metal, therefore it needs to be installed atop of Proxmox, i presume.
For the Proxmox 5 here's the cheatsheet:

echo 'deb http://linux.dell.com/repo/community/openmanage/iSM/340/stretch stretch main' | tee -a /etc/apt/sources.list.d/linux.dell.com.sources.list && \
apt install dirmngr && \
gpg --keyserver pool.sks-keyservers.net --recv-key 1285491434D8786F && \
gpg -a --export 1285491434D8786F | sudo apt-key add - && \
apt update && \
apt install dcism && \
service dcismeng start

 

[TomTomGo]

Hi,

Yes of course this is what we are doing at the moment with Proxmox 5.X. Full versions of srvadmin and dcism are available and works fine.
We are able to manage servers through the OpenManage web GUI, including storage management (RAID), and monitoring servers with Nagios check_open_manage plugin through snmp.
BUT version is old (june 2018, 9.1.0) and does not support Debian 10, i.e Proxmox 6.
And DELL does not seem to support Debian anymore.
Ubuntu versions are more recent and have better support / ugrades.

 

[TomTomGo]

BTW, nesting is enabled and unprivileged container is off ...