Lessons Learned: OPDK 4.51 + AWS LTS + NEWUI (for DEVOPS/SRE)

Audience: Devops/SRE

Issue: Strange/Phantom errors during install of  4.51 on AWS LTS (Amazon2)  for OPDK.    During the install, I noticed strange errors with the installer, it would randomly fail at different points.  I tried a single conf file and separated configuration file for sso and new-ui

Layout:   AWS ALB for MGMT / UI,  AWS NLB (network load-balancer) for api traffic,   single region(single planet)

 

Resolution #1 -  AWS ALB defaults to HTTP/2.     Apigee installer is hardcoded for HTTP1.1, and doesn't work for HTTP/2.  The installer doesn't check for HTTP/2, and thinks an error occurred.  

Fix:   In terraform,  please change load-balancer to http/1.1 only. Disable HTTP/2.   NOTE:  If you api traffic is running via ALB, please consider creating two ALB - mgmt vs api-traffic.

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#enable_http2

 

Code:   In terraform, explicitly set to false 

apigee-newui-terraform.png

 

HARDCODED  HTTP.1.1 

apigee-451-newui_http11-code.png.png

 

 

Resolution#2 -  Strange errors with "too many redirect" error with new-ui

Fix:  

  1. Please restart SSO & new-ui in the correct sequence.   With automated shutdown, you need to startup components in correct order.   Not conclusive, but starting cass/zk & db first seems to resolve login issues with new-ui

 

0 0 131
0 REPLIES 0