at the moment, I am looking at the automated kickstart and PXE boot functionality. My boot is stuck somewhere but I cannot spot anything in the logs or what/where something is supposed to happen. Can you please assist me in troubleshooting?
This is where I am at (CentOS Uyuni Server):
1. Kickstartable tree is downloaded (via reposync).
2. Distribution is set up via WebUI. (Tree path=/var/spacewalk/rhn/kickstart/1/centos8-baseos-x86_64 and it exists on the file system for apache:apache).
3. Basic Profile created via WebUI ("kickstart-profile", OS seems OK, "Available tree" as in 2., software URL: /ks/dist/org/1/centos8-baseos-x86_64 )
4. DHCP set up
Now starting up a server:
5. PXE picked up DHCP.
6. PXE loaded the blue Cobbler menu
Here, I can chose "kickstart-profile:1:test"
7. Now, whenever that entry is selected, the blue screen flashes and I am pretty much at the same place as 6.
Pressing tab to see the boot details, these lines are shown:
/images/centos8-baseos-x86_64:1:test/vmlinuz initrd=/images/centos8-baseos-x86_64:1:test/initrd.img ks=http://dev2.bluhm-de.com/cblr/svc/op/autoinstall/profile/kickstart-profi… BOOTIF=01-00-0a-21-31-56-34
wget http://dev2.bluhm-de.com/cblr/svc/op/autoinstall/profile/kickstart-profile:… BOOTIF=01-00-0a-21-31-56-34
All download content. Also firewall is disabled.
So I am not really sure what exactly is supposed to happen when you press [enter] at step 6 above. What would be the real next step? Download a file? Boot an already downloaded file?
Any hints for debugging would be great.
Thank you and best wishes,
Lana from the docs team here. We're planning to do some work on the Uyuni documentation in the new year, and we'd like to get your feedback on what you would like to see. We've got a short survey up for you to fill out:
Make sure you get your responses in, so that we can include your suggestions.
At the moment, the Uyuni documentation is largely created from the same source as SUSE Manager documentation, but we know that that doesn't always work as well as it could. We specifically want to hear from you on what content you think is required for Uyuni that might be different to what is required for SUSE Manager.
Technical Writer - SUSE Manager
"The question is," said Alice, "whether you
can make words mean so many different things."
Hello, me again...
I tried to run reposync on CentOS with Zypper and DNF as backend. In both cases, I get these messages
for http links:
[Errno 14] curl#1 - "Protocol "b'http" not supported or disabled in libcurl".
for https links:
[Errno 14] curl#1 - "Protocol "b'https" not supported or disabled in libcurl".
curl cli can download the sources without issues. I also tried a minimal pycurl script and it can download a https rpm file without issues. So it is not a setup issue.
Not sure if i am at the right place but I cannot identify any potential issues in spacewalk/satellite_tools/download.py. The Urls seem to be passed properly.
Are you aware of these issues or can pinpoint me where to look? Maybe the exact place that is calling/configuring pycurl to see what is passed?
Thank you and best wishes,
I'm about to create the appointments for the next months and I was wondering if last Friday of the month, 4pm CET is still the best time.
What are your thoughts? Would you prefer some other week of the month, day or time?
Pau Garcia Quiles
SUSE Manager Product Owner & Technical Project Manager
Phone: +34 91 048 7632
SUSE Software Solutions Spain
you can find the same text Github Discussions.
I've just pushed a first draft of a goss server description to the
master-goss-branch. Goss is a YAML based serverspec alternative tool
for validating a server’s configuration. Means you are able to check if
services are configured correctly, if they are running, if users are
there and in the right group, if configs are there and if settings are
missing, if pkgs are installed, aso.
Wouldn't it be nice to just run one command on a Uyuni server to see if
something is wrong? To some extend this could be done with goss. But I
need help. I'm pretty sure that I missed a lot of things that need to be
added to the goss.yaml file. Would be really awesome if I could get some
input and help there.
To get started you can either go install goss or head over to
systemsmanagement/goss and install it from there. Then change the
domain in gossvars.yaml and start the validation via 'goss --vars
To add additional things to check head over to the manual and take a
look at the examples. Should be pretty self explanatory.
I would be very happy to see PRs coming to master-goss!
SUSE Software Solutions Germany GmbH
(HRB 36809, AG Nürnberg)
Managing Director: Felix Imendörffer