Skip to main content

Log - Sprint 7 🛫

· 2 min read

Date​

Flight Log contain information relating to steps completed on 06/06/2023

Key Accomplishments​

  • Successfully edited the CR with our certificate secret.  The Ingress needs to have a certificate in its trust store, so we forced it to redo and recreate secrets to include the certificate. To do this we used the Ingress secret ‘filenet-poc-tls’ that we created before and added it to the CR at the line ‘sc_ingress_tls_secret_name’. We also added it to the trusted certificate list within the CR.
  • Deleted and recreated the ‘fncmdeploy-fncm-custom-ssl-secret’ and ‘fncmdeploy-ban-custom-ssl-secret’.
  • We edited the resource quota and upgraded it from ‘large’ to ‘x-large’.  Edited the Value.yaml through GitHub and sent in a PR with the change (could not change it from command line because we got authorization issues).
  • We set the replica count of the Navigator back to 2 and all pods were up and running.

Challenges​

  • We initially received an error when trying to visit the ACCE URL. This was fixed after we added the certificate secret to the CR and reapplied it.
  • We are still having issues logging in to ACCE and Navigator even after applying the certificate secret to the CR and redeploying pods.

Action Items​

  • We followed the steps laid out by IBM Dev team but are still running into the Ingress issue of having a blank page after logging into ACCE and not being able to login to the Navigator.  We exported Ansible logs and will bring it back to the IBM Dev team to see what the issue could be.

Tracking​