Roadmap: https://github.com/cobbler/cobbler/wiki/Roadmap Meeting Room: https://meet.opensuse.org/cobbler
So I am getting a "[!] Installation Source (Error setting up software source) when I try to install rh8.3 on a new. and it was working a month ago,. Question is; where does cobbler tell me what the valid software source is? Is it in the profile report? If not there where does cobbler expect to get the 'software source' which I assume is the .iso file? I do use http://x.x.x.x/cblr/ and have tried http://x.x.x.x/cobbler as well to BaseOS, AppStream, isolinux... The install lost its way to the "software source".
I am still unable to import a custom debian kernel based on buster. >> [root@cos-pxe-00 ~]# cobbler import --name=ddn-flash-PEM-12.0.0.1-dev-debug.nojanus --breed=debian --arch=x86_64 --path=/mnt/s
task started: 2021-12-29_103227_import
task started (id=Media import, time=Wed Dec 29 10:32:27 2021)
No signature matched in /var/www/cobbler/ks_mirror/ddn-flash-PEM-12.0.0.1-dev-debug.nojanus-x86_64
!!! TASK FAILED !!!
Is there something missing from my command syntax ?
task started: 2021-12-29_103227_import
task started (id=Media import, time=Wed Dec 29 10:32:27 2021)
No signature matched in /var/www/cobbler/ks_mirror/ddn-flash-PEM-12.0.0.1-dev-debug.nojanus-x86_64
!!! TASK FAILED !!!
Is there something missing from my command syntax ?
what signature in /var/www/cobbler/ks_mirror/ddn-flash-PEM-12.0.0.1-dev-debug.nojanus-x86_64 am I trying to match? or better yet what should be there as a signature to match?
So I just upgraded my old Cobbler installation to Fedora 35, and I added some new distros and removed some folders from /var/www/cobbler/distro_mirror/. After removing the folders I reran cobbler sync, it just removed ALL the /var/www/cobbler/* folders. Basically borking my cobbler install.
So instead of trying to import the the custom debian kernel I used 'cobbler distro add' instead and it took it. It still is not completing the install but at leaset it gets to a message stating "No root device specified. Boot arguments must include a root= parameter". Not sure where I would add that .
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)
Cobbler 3.2.2 from epel-release vanilla btw, with all dnf updates
However, since then, I discovered 3.3 lacks a web interface, which is likely a show stopper for me.
and this is also a showstopper for the EPEL maintainer of cobbler
so I have 2 questions:
- Does the web interface removal impacts the use of the cobbler ansible module ? it makes use of the web API I think
- is the 3.2 branch going to have more releases ? I would consider backporting some stuff from master to 3.2 if that is the case
Check the wiki please
There is an article on how to run the tests
Sooo regarding the Web Interface... It turns out Cobbler can do more then I can handle on my own. I have put a lot of time in starting to create the XMLRPC API and the API Client in Angular but so far I am not there to present something usable. However feel free to look at the Draft PR I created...
In regard to 3.2.x releases... No I haven't planned anything there because of the huge changes I made on master I personally believe that it is not reasonable to try doing a port. I would love to see more activity in fixing bugs on master so we can finally push out the next 3.3.x release.
@egotthold:matrix.org So I guess 3.3 is definitely a nogo for me and probably others, until at least http://cobbler_host/cobbler_api is usable. And if 3.2 is frozen and won't see a new release, then I'll have to lobby the EPEL maintainer to include patches, which is less likely to happen if it's not coming from upstream SCM. I do need cobbler to be able to install CentOS 6, 7, 8 and 9 and also to be able to pilot it from ansible. None of the cobbler releases matches both criterion.
1 reply
?
Here's a link to the ansible cobbler module : https://github.com/ansible-collections/community.general/blob/c18fdb43d7ca09996773b61a882233fcd54c459c/plugins/modules/remote_management/cobbler/cobbler_system.py#L241
look for something similar in terraform
Terraform looks at url = "http://cobbler.example.com/cobbler_api" @xavierba. I think that makes it XMLRPC
so far, I think all I need atop of release32 branch is https://github.com/xavierba/cobbler/tree/32_backport
1 reply
I will give that a try on Thursday
I'll probably look into it later
But I see that the Webinterface is eagerly awaited. I will see that I put more priority in my free time onto it.
get-loaders is broken with 3.2.2, as the url from which the loaders are pulled as been removed. Unless the page has been restored since I built my new cobbler server. I had to fetch the loaders from my old cobbler server. Although I did noticed this is mentioned in a couple of places, I have not yet really looked into the discussions and patches.
@xavierba, yes I'm going to try to get v3.2.x working too for the time being, and yes main obstacle is removal of loaders. Hopefully will be as simple as changing dlcontent.py's
content_server = https://github.com/hbokh/cobbler-loaders per: https://github.com/cobbler/cobbler/issues/2660#issuecomment-859766544 I'll post if\when I get working, appreciate if you could do same
I completely understand that @egotthold:matrix.org rather want to move forward rather than backporting stuff, but with the current state of the webinterface and especially the xmlrpc, 3.3 is unsuitable for anyone in need of cobbler/terraform. Hence, the only hopefully temporary solution is to backport stuff to 3.2.
@holmesb I now see get-loaders has been patched out of the latest EPEL 8 package. But still I need to investigate/document how to properly set this up from the distro supplied loaders. And get the Fedora/EPEL package fixed if possible. Thanks for the links, it'll be useful.
@holmesb , I don't know what your own issues are, but here is a first try at it for my own purpose: https://github.com/xavierba/cobbler/tree/32_backport