[Spacewalk-list] Spacewalk's planned cert expiration in Aug (Can we simulate this?)

Jody McIvor JMcIvor at bclc.com
Fri Jul 19 14:18:01 UTC 2019


Hi All,

In preparation for Redhat's dropping of Spacewalk support (And any further certificate renewals), we have updated all of our spacewalk servers to no less than 2.6. I have been (unsuccessfully, since I'm not sure exactly which file it is) attempting to "simulate" the cert expiration by:
 - Renaming what I thought was the cert file (Pretty sure I was wrong)
 - Forcing date/time change to 2019 on Spacewalk server (Everything seemed fine, but still not convinced.

My questions are:
 - Can someone enlighten me as to which file is truly the cert that will expire next month?
 - Was changing the time on the server my best bet for testing the effects of the cert failure?

Any input on this subject is appreciated, because if this doesn't go smoothly in Aug it WILL have a massive impact on company income until resolved.

Jody McIvor
Sr. Systems Administrator, Integration
Les Services D'intégration




-----Original Message-----
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> On Behalf Of spacewalk-list-request at redhat.com
Sent: July 19, 2019 6:27 AM
To: spacewalk-list at redhat.com
Subject: Spacewalk-list Digest, Vol 134, Issue 13

Send Spacewalk-list mailing list submissions to
spacewalk-list at redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/spacewalk-list
or, via email, send a message with subject or body 'help' to
spacewalk-list-request at redhat.com

You can reach the person managing the list at
spacewalk-list-owner at redhat.com

When replying, please edit your Subject line so it is more specific than "Re: Contents of Spacewalk-list digest..."


Today's Topics:

   1. Needs-Restarting shows perpetual reboot need afterKickstart
      (bryan.norton at gmail.com)
   2. Re: Needs-Restarting shows perpetual reboot needafter
      Kickstart (bryan.norton at gmail.com)
   3. Re: Update failing for no public key (Lubbers, Nicholas)


----------------------------------------------------------------------

Message: 1
Date: Fri, 19 Jul 2019 06:11:15 +0200
From: <bryan.norton at gmail.com>
To: <spacewalk-list at redhat.com>
Subject: [Spacewalk-list] Needs-Restarting shows perpetual reboot need
afterKickstart
Message-ID: <000001d53de8$03363990$09a2acb0$@gmail.com>
Content-Type: text/plain; charset="us-ascii"

Since I couldn't get around the Internal Server Error when attempting to Profile Sync, I found a work around using spacecmd and a post script during the Kickstart process.



Everything works great, with one exception.  After the provisioning is done, and the server is accessible, it shows that it needs a reboot.  After rebooting it, it still shows a reboot is needed.  It says (amongst other
components) that the kernel has been updated, yet uname -r shows it is running the kernel that it thinks it needs to reboot to use.



Have you all seen this before?  I'm stumped.no amount of googling has produced anything close to helpful.



Thanks!

Bryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/26001fd3/attachment.html>

------------------------------

Message: 2
Date: Fri, 19 Jul 2019 10:10:45 +0200
From: <bryan.norton at gmail.com>
To: <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] Needs-Restarting shows perpetual reboot
needafter Kickstart
Message-ID: <000201d53e09$7890a1f0$69b1e5d0$@gmail.com>
Content-Type: text/plain; charset="us-ascii"

It looks like it was a date/time issue.  When the system was kickstarted, it used the default GMT.  Somewhere in the update process after install, the time was corrected to GMT+2.  After 2 hours, I rebooted it again, and no it no longer thinks it needs to reboot to load a more recent kernel, and shows the system is up to date.



From: bryan.norton at gmail.com <bryan.norton at gmail.com>
Sent: Friday, July 19, 2019 06:11
To: spacewalk-list at redhat.com
Subject: Needs-Restarting shows perpetual reboot need after Kickstart



Since I couldn't get around the Internal Server Error when attempting to Profile Sync, I found a work around using spacecmd and a post script during the Kickstart process.



Everything works great, with one exception.  After the provisioning is done, and the server is accessible, it shows that it needs a reboot.  After rebooting it, it still shows a reboot is needed.  It says (amongst other
components) that the kernel has been updated, yet uname -r shows it is running the kernel that it thinks it needs to reboot to use.



Have you all seen this before?  I'm stumped.no amount of googling has produced anything close to helpful.



Thanks!

Bryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/b913b54a/attachment.html>

------------------------------

Message: 3
Date: Fri, 19 Jul 2019 13:27:14 +0000
From: "Lubbers, Nicholas" <Nicholas.Lubbers at nsight.com>
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Subject: Re: [Spacewalk-list] Update failing for no public key
Message-ID:
<b571e9023d714bac869c8e020fea3d7e at NSWP-E2013-02.Nsight.com>
Content-Type: text/plain; charset="utf-8"

We started to see this on all our CentOS 7 servers recently as well. Were you ever able to come up with a solution? I?ve excluded this package from updates for the time being.

From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> On Behalf Of Ellis, Merphis
Sent: Wednesday, July 17, 2019 3:00 PM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Update failing for no public key

CAUTION: This email was sent from outside of Nsight or any of its affiliated companies. If you do not recognize the sender?s email address and know the content is safe, do not click on links, open attachments or respond to this email.

My updates are starting to fail the error message is ?Error while executing packages action: Public key for tzdata-2019b-1.el7.noarch.rpm is not installed [[6]]?


Making plans actionable!


Regards,




Merphis Ellis



M. +1 850 556-6313
E. merphis.ellis at us.idemia.com<mailto:merphis.ellis at us.idemia.com>
125 McAlpin Dr
Winterville, GA 30683







[Idemia]<https://www.idemia.com/>


Join us on

[Facebook]<https://www.facebook.com/IdemiaGroup/>

[Twitter]<https://twitter.com/IdemiaGroup>

[LinkedIn]<https://www.linkedin.com/company-beta/3488/>

[Youtube]<https://www.youtube.com/user/SafranMorpho/>






[www.idemia.com]<https://www.idemia.com/>




[OT-MORPHO is now IDEMIA]





________________________________

This message is only for the use of the intended recipient and may contain information that is CONFIDENTIAL and PROPRIETARY to IDEMIA. If you are not the intended recipient, please erase all copies of the message and its attachments and notify the sender immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/ea31617a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2605 bytes
Desc: image001.gif
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/ea31617a/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 1481 bytes
Desc: image002.gif
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/ea31617a/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.gif
Type: image/gif
Size: 1495 bytes
Desc: image003.gif
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/ea31617a/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.gif
Type: image/gif
Size: 1499 bytes
Desc: image004.gif
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/ea31617a/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.gif
Type: image/gif
Size: 1498 bytes
Desc: image005.gif
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/ea31617a/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.gif
Type: image/gif
Size: 2049 bytes
Desc: image006.gif
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/ea31617a/attachment-0005.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.gif
Type: image/gif
Size: 1579 bytes
Desc: image007.gif
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20190719/ea31617a/attachment-0006.gif>

------------------------------

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

End of Spacewalk-list Digest, Vol 134, Issue 13
***********************************************
________________________________
This email is intended only for the addressee. It may contain confidential or proprietary information that cannot be disclosed without BCLC's permission. If you have received this email in error, please notify the sender immediately and delete the email.




More information about the Spacewalk-list mailing list