This may not be proper solution, but you can script post trigger as a work
around.
https://cobbler.github.io/manuals/2.6.0/4/4/1_-_Triggers.html
Anay
sent from my phone. Sory fer eny typeos
On Fri, Sep 27, 2019, 5:38 PM Jeff Beaird wrote:
> Hi.
>
> I'm trying to modify the "local" boot
Hi.
I'm trying to modify the "local" boot settings.
This because "LOCALBOOT 0" does not work for me, but
this does:
"kernel chain.c32
append hd0 0".
I can set /var/lib/tftpboot/pxelinux.cfg/default to be what I want, but
it's overwritten when Spacewalk restarts or "cobbler sync" runs.
I
If I understand it right, the name of your server within your certificate was
wrong and all the clients are running with the wrong fqdn name. Right?
So you know want to fix this and created a new certificate with the Fqdn fixed.
Right?
Has this certificate been generated (and signed) by the
On Sep 27, 2019, at 1:20 PM, Weiner, Michael
mailto:wein...@ccf.org>> wrote:
Thank you for your response, Dean. I didnt do the let's encrypt cert, will that
be a problem?
No, my cert isnt either…. The steps in the guide show specifics for LE certs,
but you can apply the specific steps for
Thank you for your response, Dean. I didnt do the let's encrypt cert, will that
be a problem?
From: spacewalk-list-boun...@redhat.com on
behalf of Peirce, Dean
Sent: Friday, September 27, 2019 12:02 PM
To: spacewalk-list@redhat.com
Subject: [BULK][EXT] Re:
Hi! Anyone know what the problem is here? Am I not formatting the date
correctly? I've tried shaving off the seconds and milliseconds, but still
no luck. Any thoughts would be appreciated.
[2019-09-27 09:45:24,900] INFO - REQUESTED FROM: 172.18.8.207 CALL:
actionchain.create_chain(svc_acct,
Hi Michael,
I followed the instructions in the link below, when I had to change my cert. I
had to work around a couple of the steps, since we use a static ssl
certificate, and not a Let’s Encrypt cert.
Hope this helps.
I have a need to regenerate and redistribute the SSL certificate for my
instance of spacewalk. When i set it up originally, the FQDN was not correct so
the cert is now wrong that got distributed to workstations/servers, and i need
to correct it now that the FQDN is correct. I have been googling
