-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.11.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
PRP（https://docs.engineering.redhat.com/pages/viewpage.action?spaceKey=CATALOG&title=rhel-prp） jira aubot token rhel-process-autobot-token is changed to an unexpected token which may be an obsoleted one.
Version-Release number of selected component (if applicable):
OpenShift version4.11.43View release notesKubernetes versionv1.24.14+38b1413Channelstable-4.11Cluster ID0a3e1193-d23e-4ced-99c7-492aa3251d2fAPI serverhttps://api.ocp-c1.prod.psi.redhat.com:6443
How reproducible:
non-reproducible
Steps to Reproduce:
In https://console-openshift-console.apps.ocp-c1.prod.psi.redhat.com/k8s/ns/jenkins-csb-rhelwfautomation/secrets/prod-casc-secret, prp jira bot account token rhel-process-autobot-token is changed to an unexpected token(Maybe the obsoleted token.), then all of the PRP process failed from https://prod-jenkins-csb-rhelwfautomation.apps.ocp-c1.prod.psi.redhat.com/job/rhel-prp-rhel9/78562/ So I request the audit log about the secret change for prod-casc-secret:rhel-process-autobot-token 17 hours ago, the audit logs shows here: https://redhat.service-now.com/surl.do?n=INC2703827 It says 'There were no logs about deletion/update of the mentioned secret for the date of August 16, 2023.', but 'The closest is what seems a deletion of the replication controller', this is the splunck log: https://rhcorporate.splunkcloud.com/en-US/app/rh_paas/search?earliest=1692144000&latest=1692230373&q=search%20prod-casc-secret%20index%3Drh_linux&display.page.search.mode=smart&dispatch.sample_ratio=1&workload_pool=standard_perf&sid=1692824298.634685_A084D307-A89F-4441-9ECB-B680DE310467 Could you help me understand what happened here? Thanks.
Actual results:
Expected results:
Jira auto token is correct
Additional info:
This affects the PRP prod environment https://prod-jenkins-csb-rhelwfautomation.apps.ocp-c1.prod.psi.redhat.com/, lots of RHEL Package Requests were blocked by this. But now, PRP works well now after our team updated the autobot token by automation and the token came back, in fact we didn't provide the unexpected token above, this happened for the first time during I take over PRP for about 3 years.
Basically I'm not sure which component it belongs to, pls correct it if I'm wrong, thanks.