Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Who present in meeting
Commit
Details
Root Cause Analysis

Actions


Takeaways

...

25/09/2020 09:15

Who present in meeting
Commithttps://stash.forgerock.org/projects/OPENAM/repos/openam/commits/381841a1c83d2c0af80ff24a5ebc3274e1ab5c54
DetailsK8S stage failure
Root Cause Analysis

INFO [loop_until]: Function succeeded after 10m 12s (rc=0) - failed to find expected pattern: .*readyReplicas:1.*replicas:1.* - retry ERROR [loop_until]: Function does not return expected pattern (.*readyReplicas:1.*replicas:1.*) DEBUG --- stdout --- DEBUG map[conditions:[map[lastTransitionTime:2020-09-25T01:06:47Z lastUpdateTime:2020-09-25T01:06:47Z message:Deployment does not have minimum availability. reason:MinimumReplicasUnavailable status:False type:Available] map[lastTransitionTime:2020-09-25T01:16:48Z lastUpdateTime:2020-09-25T01:16:48Z message:ReplicaSet "am-f6cd79d56" has timed out progressing. reason:ProgressDeadlineExceeded status:False type:Progressing]] observedGeneration:1 replicas:1 unavailableReplicas:1 updatedReplicas:1]

Actions

No action, this is considered to be a flaky stage but also outside of set of stages that should be considered post mortem

TakeawaysK8s and pit1 stages do not need to be considered for post mortem or locking of master; if there was to become multiple fails in a row, then a post mortem should be considered

24/09/2020 16:37

Who present in meetingAlun, Pete R, Kevin, Rich, Andy F, Mark L
Commithttps://stash.forgerock.org/projects/OPENAM/repos/openam/commits/189386a7a5139f0ca7672f6bf2b29385f6731dfb
Detailsfailure in build stage
Root Cause Analysis[gcp-gce-jenkins-agent-1] [36mmaven_1 |[0m [INFO] [ERROR] Failed to execute goal on project basic: Could not resolve dependencies for project archetype.it:basic:jar:0.1-SNAPSHOT: Failed to collect dependencies at org.forgerock.am:openam-core:jar:7.1.0-SNAPSHOT -> org.forgerock.am:openam-idsvcs-schema:jar:7.1.0-SNAPSHOT: Failed to read artifact descriptor for org.forgerock.am:openam-idsvcs-schema:jar:7.1.0-SNAPSHOT: Could not find artifact org.forgerock.am:openam-schema:pom:7.1.0-20200924.145523-100 in forgerock-internal-snapshots (https://maven.forgerock.org/repo/internal-snapshots) -> [Help 1]

Doesn't seem from observing artifactory that that artifact does exist https://maven.forgerock.org/repo/internal-snapshots/org/forgerock/am/openam-schema/7.1.0-SNAPSHOT/

This seems to be the same issue as observed in the post mortem on 01/09/2020 15:54.


Actions

Jira
serverForgeRock JIRA
serverId45b4e541-fe03-30e2-b999-cf4e643b93ec
keyAME-18031
 is already created. Adding the DRIVE label and removing Maxwell.

Master has not been locked, we will not lock it and await the next build results as this issue is anticipated to resolve itself in the next build.

TakeawaysAbove issue should be escalated

...