I recently setup a VM on Proxmox with the SCST modules and Houston / Cockpit with the cockpit-file-sharing module. I logged in to cockpit with a regular user who was a member of the sudo group and was able to elevate my privileges to admin privileges as expected but when I went to the iSCSI module it refused to do anything saying that you had to be logged in as root. So I logged in as root and sure enough it worked. Is this by design or should a user in the sudo group be able to manage the iSCSI config?
1 Like
Hi @mmurphy
Welcome to the forum, and thank you for reaching out.
I tested this internally and was able to log in using my âhutchâ user account, then elevate my permissions to Administrator from the top-right menu.
After doing that, I was able to view my iSCSI SCST configuration successfully.
Could you please share the steps you took to get to this point, along with any errors you are seeing? That will help me try to reproduce the issue on my side and better understand what may be happening.
Hello @Hutch-45Drives , and thank you for the response.
I have a Proxmox host with a Debian 12 VM. Initially I started with the VM running the standard kernels 6.1.0-39-amd64 and 6.1.0-43-amd64 before upgrading it to the backport kernel 6.12.57-1~bpo12+1. I had git cloned the SCST repo and compiled the SCST drivers for each of the kernels and edited the /etc/scst.conf file using nano. The goal was to use SCST to share out an iSCSI drive with some Windows clients. I was able to get that all working, the Windows initiators can see the target drive, format it, backup to it, etc. Later I found out about the 45drives file-sharing module and that it worked with SCST so I installed cockpit as well as file-sharing, identities, and navigator modules. The file-sharing module works for Samba, but when I go to the iSCSI tab, I immediately get an error message at the top right of the screen that says
Error in i: localhost: cat: â/sys/kernel/scst_tgt/targets/iscsi/iqn.2000-05.com.example.vmiscsi02:deb10g01/IncomingUserâ: Permission denied(1)
The banner at the top of the screen indicates my user account has Administrative access. Additionally, while the devices are listed on the screen, none of the targets are listed. Finally, clicking on the Export button to export the scst.conf gets the following error
ProcessError (exited non-zero)
Error in exportConfig: localhost: HoustonBashCommand: This program must run as root. (255)
So I logout of my personal account and login as root and I do not get the error message, the devices AND targets are listed as expected and the Export button works.
My userid is not mentioned in the iSCSI section of the scst.conf file, would that prevent it from being able to discover the targets? That said, my root user isnât mentioned in the scst.conf file either and it sees the targets just fine. Let me know if thereâs any other info that would be helpful.
My system is a Rocky9 VM with SCST and Houston installed, and I also just tried to export the config and received the same warning. Iâm going to pass this along to R&D, but for now, the root user should be able to do everything, right?
Everything works great if youâre the root user, seems to be anyone other than root that it wonât work. Thanks again for the reply. Have a great day.
1 Like