re-enable full CI

24 jobs for aws-integration in 23 minutes and 30 seconds (queued for 5 seconds)
Status Name Job ID Coverage
  Build
passed compile-and-unit-test #532481
osdu-medium

00:08:41

passed osdu-gcp-helm-charts #532482
osdu-small

00:00:07

 
  Containerize
passed aws-containerize #532484
osdu-medium

00:02:49

passed azure_containerize #532483
osdu-medium

00:01:34

passed osdu-gcp-containerize-gitlab #532485
osdu-medium

00:02:50

 
  Scan
passed bandit-sast #532489
osdu-medium

00:05:17

passed fossa-analyze #532486
osdu-medium

00:10:54

passed gemnasium-maven-dependency_scanning #532487
osdu-medium

00:07:36

passed gemnasium-python-dependency_scanning #532488
osdu-medium

00:07:24

passed license_scanning #532492
osdu-medium

00:04:43

passed semgrep-sast #532490
osdu-medium

00:06:57

passed spotbugs-sast #532491
osdu-large

00:14:40

 
  Deploy
failed aws-update-eks #532494
osdu-medium

00:05:44

passed azure_deploy #532493
osdu-medium

00:03:27

passed ibm-deploy #532495
osdu-medium

00:09:28

failed ibm-deploy-devpri #532496
osdu-medium

00:07:18

passed osdu-gcp-deploy-configmap #532497

00:00:50

passed osdu-gcp-deploy-deployment #532498

00:00:26

 
  Integration
skipped aws-test-java #532500
osdu-medium
passed azure_test #532499
osdu-medium

00:08:50

passed ibm-test #532501
osdu-medium

00:04:02

passed osdu-gcp-test #532502
osdu-medium

00:04:34

 
  Attribution
failed fossa-check-notice #532503
osdu-small

00:00:59

passed fossa-report #532504
osdu-small

00:01:15

 
Name Stage Failure
failed
fossa-check-notice Attribution
You can download the NOTICE file from this job's artifacts and directly commit it to the repository to resolve
this. Before doing so, review the differences to make sure that they make sense given the changes that you have
made. If they do not, reach out to a maintainer to help diagnose the issue.
Uploading artifacts for failed job
Uploading artifacts...
public: found 2 matching files and directories

Uploading artifacts as "archive" to coordinator... ok
id=532503 responseStatus=201 Created token=r2gn1LDb
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
aws-update-eks Deploy
Added new context arn:aws:eks:us-east-2:198931730835:cluster/glosdu-green-main to /tmp/kubeconfig-28803.yaml
$ chmod 644 $KUBECONFIG
$ kubectl -n osdu-services rollout restart deployment/${AWS_EKS_DEPLOYMENT_NAME}
deployment.apps/os-entitlements restarted
$ kubectl -n osdu-services rollout status -w deployment/${AWS_EKS_DEPLOYMENT_NAME} --timeout=300s
Waiting for deployment "os-entitlements" rollout to finish: 1 old replicas are pending termination...
error: timed out waiting for the condition
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
ibm-deploy-devpri Deploy
NAME           TYPE     FROM     LATEST
entitlements Source Binary 18
$ oc start-build $CI_PROJECT_NAME --from-dir=. --follow
Uploading directory "." as binary input for the build ...
............................................................
Uploading finished
Error from server (BadRequest): unable to wait for build entitlements-19 to run: timed out waiting for the condition
Cleaning up file based variables
ERROR: Job failed: exit code 1