ISAR Quay cert is expired

[DanielFroehlich]

which renders AAP useless.

[DanielFroehlich]

@rbo , I will take care of this and create a fresh one.
Do we have some cert expiry warning meachanism where I could add https://quay.coe.muc.redhat.com to? So we dont fall into this again?

[rbo]

Added new webserver check including cert check

ssh mon@monitoring.coe.muc.redhat.com
OMD[mon@monitoring]:~$ cp   etc/naemon/conf.d/hosts/sso.cfg  etc/naemon/conf.d/hosts/quay.cfg
OMD[mon@monitoring]:~$ vim etc/naemon/conf.d/hosts/quay.cfg

content of quay.cfg

define host{
  host_name               quay.coe.muc.redhat.com
  hostgroups                      webservers
  address                 10.32.98.2
  max_check_attempts      5
  check_period            24x7
  check_command           check-host-alive
  contact_groups          coe-admins
  notification_interval   30
  notification_period     24x7
}

Reload naemon

OMD[mon@monitoring]:~$ omd reload naemon
Running naemon configuration check... OK
Reloading naemon configuration (PID: 3155)... OK
OMD[mon@monitoring]:~$

Check webui

[rbo]

@DanielFroehlich monitoring: done / ✅

[rbo]

--SERVICE-ALERT-------------------
-
- Hostaddress: 10.32.98.2
- Hostname:    [quay.coe.muc.redhat.com](http://quay.coe.muc.redhat.com/)
- Service:     Check expired date of certificate
- - - - - - - - - - - - - - - - -
- State:       OK
- Date:        2026-04-22 10:48:19 (Duration: 0d 0h 0m 0s)
- Output:      OK - Certificate '[quay.coe.muc.redhat.com](http://quay.coe.muc.redhat.com/)' will expire on Sat 17 Apr 2027 07:51:58 AM GMT +0000.

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

[DanielFroehlich]

Cert refreshed, closing this one