Login error 950f26c6 2026-09-29 - confirmar o descartar contra MOVILBA-616

Sub-tickets

Activity

• audit-mba-l-cc created · 2w ago
• coder03-mba-l-cc assigned · 2w ago
  db04-mba-l-ca / db
• db04-mba-l-ca blocked · 2w ago
  db04-mba-l-ca 2026-10-01 09:34 ART. Exact requestId 950f26c6-d466-41ad-aaf0-4a4d6859313c was absent from movilba_dev.public.app_logs by request_id and by message/data search. App log has no rows within 18:31:24-18:35:24 UTC around the 18:33:24.968 UTC report, so absence there cannot confirm or exclude the cause. oc whoami returned Unauthorized; two oc login attempts using existing local OCP variables exited 1, second classified authentication rejected. Pod log was NOT read. MOVILBA-616 remains an unconfirmed temporal hypothesis; neither Cliente no encontrado nor unauthorized_client is established. Blocked on an already-authorized OpenShift log reader obtaining the pod log for this exact requestId; no password reset requested. Evidence: /data-lezama/movilba/evidencia/MOVILBA-623/2026-10-01-login-request-950f26c6.md.
• db04-mba-l-ca progress · 2w ago
  db04-mba-l-ca 2026-10-01 10:14 ART. Correction to prior blocker: coder03-mba-l-cc reports ocp4-dev OIDC metadata advertises authorization_code and implicit grants only. Therefore my oc login -u/-p 401 was an unsupported-password-grant result, NOT evidence that the stored password is wrong. Do not retry password or request reset. proxy-mba-w-cc is arranging an OAuth token from whey; once available, use it on Lezama to inspect movil-ba-dev pod logs and prior pod if rotated for exact requestId 950f26c6-d466-41ad-aaf0-4a4d6859313c. Until those logs are read, MOVILBA-616 remains unconfirmed. Evidence file corrected: /data-lezama/movilba/evidencia/MOVILBA-623/2026-10-01-login-request-950f26c6.md.
• db04-mba-l-ca blocked · 2w ago
  db04-mba-l-ca 2026-10-01 10:30 ART. OpenShift access is now working through an authorized OAuth session, but the 2026-09-29 18:33:24.968Z pod log is unavailable from oc: all four current MovilBA application pods were created 2026-10-01 13:23Z, all older ReplicaSets have 0 pods, exact requestId 950f26c6-d466-41ad-aaf0-4a4d6859313c was absent from current pod logs, and --previous returned no prior containers. DEV app_logs also has no row at that time. This is absence of retained evidence, NOT evidence the request did not occur or that MOVILBA-616 caused it. Neither Cliente no encontrado, unauthorized_client nor invalid_client was observed for this request. Blocked only on a central archived log containing this exact requestId, if retained. Evidence: /data-lezama/movilba/evidencia/MOVILBA-623/2026-10-01-login-request-950f26c6.md.
• db04-mba-l-ca unblocked · 2w ago
  cleared: db04-mba-l-ca 2026-10-01 10:30 ART. OpenShift access is now working through an authorized OAuth session, but the 2026-09-29 18:33:24.968Z pod log is unavailable from oc: all four current MovilBA application pods were created 2026-10-01 13:23Z, all older ReplicaSets have 0 pods, exact requestId 950f26c6-d466-41ad-aaf0-4a4d6859313c was absent from current pod logs, and --previous returned no prior containers. DEV app_logs also has no row at that time. This is absence of retained evidence, NOT evidence the request did not occur or that MOVILBA-616 caused it. Neither Cliente no encontrado, unauthorized_client nor invalid_client was observed for this request. Blocked only on a central archived log containing this exact requestId, if retained. Evidence: /data-lezama/movilba/evidencia/MOVILBA-623/2026-10-01-login-request-950f26c6.md.
• db04-mba-l-ca completed · 2w ago
  db04-mba-l-ca 2026-10-01 21:53 ART — Investigación agotada: el requestId 950f26c6-d466-41ad-aaf0-4a4d6859313c del 29/09 no aparece en public.app_logs DEV (tampoco hay filas en la ventana exacta); los cuatro pods actuales nacieron 01/10 13:23Z, los ReplicaSets anteriores tienen 0 pods, oc logs de los actuales no contiene el ID y --previous no ofrece contenedor previo. El log del pod que atendió el hecho ya no se recupera por oc; no se observó mensaje que confirme ni descarte MOVILBA-616, por lo que la causa queda indeterminada, no atribuida a 616. El cluster expone APIs de ClusterLogForwarder/LokiStack, pero este usuario no puede listar sus recursos a nivel cluster; en movil-ba-dev no hay objetos locales. Por ello NO está demostrado que no exista archivo central, sólo que ningún log accesible a este carril retiene la solicitud; no se abre un defecto de retención sin esa prueba. Evidencia: /data-lezama/movilba/evidencia/MOVILBA-623/2026-10-01-login-request-950f26c6.md. Sin cambios de credenciales ni datos.