[MWCI-221] Setup appropriate certificate expiration warning probes for internal services Created: 27/Feb/20 Updated: 06/Jul/23 |
|
Status: | Reopened |
Project: | Continuous Integration Infrastructure for Middleware Development |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | Priority: | Blocker |
Reporter: | Andrea Ceccanti | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
Today at 12 the ci.cloud and repo.cloud certficates have expired, after 3 years. Unfortunately we didn't have any probe warning us of this. This issue will be used to track corrective actions to ensure that we have a proper warning system in place to watch for certificate expiration, until we move to let's encrypt for as many services as possible |
Comments |
Comment by Andrea Ceccanti [ 13/Sep/21 ] |
Today we found out that chnet had an expired certificate (and that we do not have a probe for the problem). But chnet was in the list of services to be monitored (see comments above). How comes no warning was in place for chnet? |
Comment by Marcelo Vilaça Pinheiro Soares [X] (Inactive) [ 06/Oct/20 ] |
Checked Uchiwa dashboard |
Comment by Marcelo Vilaça Pinheiro Soares [X] (Inactive) [ 05/Oct/20 ] |
Followed procedure described in:
|
Comment by Marcelo Vilaça Pinheiro Soares [X] (Inactive) [ 05/Oct/20 ] |
Added iam-eosc, iam-mvm, iam-super, iam-demo, iam-chnet to /mw-devel/puppet-site/profiles/sensu_server.pp and the respective URLs
|
Comment by Andrea Ceccanti [ 02/Oct/20 ] |
I don't see the subscriptions, i.e. the probes are not run |
Comment by Marcelo Vilaça Pinheiro Soares [X] (Inactive) [ 02/Oct/20 ] |
Added to /mw-devel/sensu-mw-devel/mwdevel_sensu/manifests/setup/checks.pp # EOSC # MVM # SUPER # DEMO ## CHNET |
Comment by Andrea Ceccanti [ 28/Sep/20 ] |
10:30 $ sh utils/show-iam-deployed-versions.sh chnet/chnet-iam-759cc56549-8rzfc: indigoiam/iam-login-service:v1.4.0-latest, |
Comment by Andrea Ceccanti [ 28/Sep/20 ] |
Verify that a probe is in place for all IAM instances: |
Comment by Andrea Ceccanti [ 07/Sep/20 ] |
Ensure we have probe in place for all services on the K8S cluster |