package.jsonhowever should be just a normal npm file. I am using npm on a regular basis with that file. The project is kind of very very early but I am working on implementing the XMLRPC API currently: cobbler/cobbler-web#14
GEtting this error when trying to import RHEL-8.5
cobbler01 ~]$ sudo cobbler import --name=RedHat-8.5-x86_64 --breed=redhat --os-version=rhel8 --path=/mnt/iso1
task started: 2021-12-07_084759_import
task started (id=Media import, time=Tue Dec 7 08:47:59 2021)
running python triggers from /var/lib/cobbler/triggers/task/import/pre/*
running shell triggers from /var/lib/cobbler/triggers/task/import/pre/*
shell triggers finished successfully
Exception occurred: <class 'cobbler.cexceptions.CX'>
Exception value: 'Command failed'
File "/usr/lib/python3.9/site-packages/cobbler/remote.py", line 98, in run
rc = self._run(self)
File "/usr/lib/python3.9/site-packages/cobbler/remote.py", line 289, in runner
File "/usr/lib/python3.9/site-packages/cobbler/api.py", line 1461, in import_tree
utils.run_this(rsync_cmd, (spacer, mirror_url, path), self.logger)
File "/usr/lib/python3.9/site-packages/cobbler/utils.py", line 890, in run_this
die(logger, "Command failed")
File "/usr/lib/python3.9/site-packages/cobbler/utils.py", line 103, in die
!!! TASK FAILED !!!
I have a question regarding the use of mkgrub.sh.
I am establishing an AlmaLinux 8.5 Cobbler server to auto install CentOS 7 machines - legacy boot, EFI boot and EFI with Secure Boot enabled each on bare metal and on HyperV.
I can't get grub.0 or grubx64.efi to get past loading the NBP , they just load it and bomb out to the grub> prompt.
I've installed the grub2 modules for the legacy and EFI scenarios - grub2-pc-modules and grub2-efi-x64-modules (efibootmgr is already present and I havent got to shim yet so forget that right now)
mkgrub does make the necessary -o output files (I don't care about other architectures)
My questions are
Should I be running it on a centos7 machine (target) or on the AlmaLinux server? Presently I am running on the AlmaLinux server as I figured that were probably close enough and it appears to be trying to work.
Secondly while the $SYSLINUX dir in the script default is fine , the $GRUB2_MOD_DIR default is not present in AlmaLinux (usr/share/grub2) only /usr/share/grub , however strangely the script as I said does work even so. Should I install some other modules?
Pardon my ignorance. Not a developer, a sysadmin (grey line these days)