Rollback 6.1–6.2.x → previous 6.x
The rollback steps are the same whether you are rolling back from 6.1.0 to 6.0.0, 6.2.0 to 6.1.0, 6.2.0 to 6.0.0, or 6.2.1 to 6.2.0.
Effective Dec 2025, AWS no longer supports the aws email configuration. Ensure you do not use aws when rolling back from Boomi Cloud API Management - Local Edition 6.2.0 or any earlier 6.x version.
Before you begin rollback, ensure the upgrade from the target rollback version to the current version is fully complete. For example, when rolling back:
- 6.1.0 → 6.0.0: confirm upgrade 6.0.0 → 6.1.0 is complete.
- 6.2.0 → 6.1.0: confirm upgrade 6.1.0 → 6.2.0 is complete.
- 6.2.0 → 6.0.0: confirm upgrade 6.0.0 → 6.2.0 is complete.
- 6.2.1 → 6.2.0: confirm upgrade 6.2.0 → 6.2.1 is complete.
Procedure
-
Run the following command to check Helm history and retrieve the available revisions.
[ec2-user@ip-10-0-0-174 deploy]$ helm history apim
REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION
1 Tue Nov 12 09:31:17 2024 superseded apim-6.0.0 1.0 Install complete
2 Tue Nov 12 09:43:29 2024 deployed apim-6.1.0 1.1.0 Upgrade complete -
Run the following Helm rollback command to go back to the previous version.
[ ec2-user@ip-10-0-0-174 deploy]$ helm rollback apim 1
W1112 09:56:15.248721 589371 warnings.go:70] unknown field "spec.template.spec.containers[1].imagePullSecrets"
Rollback was a success! Happy Helming! -
Verify the Helm history status again to confirm whether the rollback was successful. The following is the status of a successful rollback:
[ec2-user@ip-10-0-0-174 ~]$ helm history apim
REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION
1 Tue Nov 12 09:31:17 2024 superseded apim-6.0.0 1.0 Install complete
2 Tue Nov 12 09:43:29 2024 superseded apim-6.1.0 1.1.0 Upgrade complete
3 Tue Nov 12 09:56:14 2024 deployed apim-6.0.0 1.0 Rollback to 1 -
After a successful rollback, run the following command to verify if all pods are up and running.
[ec2-user@ip-10-0-0-174 ~]$ oc get pods
NAME READY STATUS RESTARTS AGE
cache-deploy-b5cbc56f5-4dr2k 2/2 Running 0 11m
cache-deploy-b5cbc56f5-82pxk 2/2 Running 0 11m
cache-deploy-b5cbc56f5-sxq6n 2/2 Running 0 11m
cacheloader-deploy-797f564d4f-nzfhk 2/2 Running 0 11m
configui-deploy-75d6c7c9-n7fkd 2/2 Running 2 (11m ago) 11m
loader-job-delta-28856760-k5qwq 0/1 Completed 0 7m45s
platformapi-deploy-67f4c8d6f8-cfvrg 2/2 Running 1 (5m29s ago) 11m
startup-cacheloader-job-v6-0-0-hf3dbr-30-lrn2n 0/1 Completed 0 11m
trafficmanager-deploy-84d88fd484-fngxt 2/2 Running 0 11m
[ec2-user@ip-10-0-0-174 ~]$ oc get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
cache-svc ClusterIP 172.30.70.134 <none> 8080/TCP,10800/TCP 36m
cacheloader-svc ClusterIP 172.30.9.162 <none> 8082/TCP 11m
configui-svc LoadBalancer 172.30.77.52 ad2d1af94096f40dfa9138249c5ae604-496219647.us-east-1.elb.amazonaws.com 80:32135/TCP,443:30763/TCP 36m
kubernetes ClusterIP 172.30.0.1 <none> 443/TCP 25h
openshift ExternalName <none> kubernetes.default.svc.cluster.local <none> 25h
openshift-apiserver ClusterIP 172.30.197.219 <none> 443/TCP 25h
openshift-oauth-apiserver ClusterIP 172.30.83.34 <none> 443/TCP 25h
packageserver ClusterIP 172.30.57.0 <none> 443/TCP 25h
platformapi-svc LoadBalancer 172.30.121.203 a90185491cf5e4d75850af2c1367f30e-1148528155.us-east-1.elb.amazonaws.com 7080:31156/TCP,7443:31337/TCP 36m
trafficmanager-svc LoadBalancer 172.30.60.201 a77c076c3f1574c8b866f05e59e94f42-2083634759.us-east-1.elb.amazonaws.com 80:30656/TCP,443:32203/TCP,1443:31184/TCP,8083:32758/TCP 36m -
Run the following command to verify if the unprotected curl call is working fine.
[ec2-user@ip-10-0-0-174 ~]$ curl -v -H 'Host: calypsoqa.api.mashery.com' 'http://a77c076c3f1574c8b866f05e59e94f42-2083634759.us-east-1.elb.amazonaws.com/testeng1589?api_key=123'
`* Trying 52.2.69.32...
`* TCP_NODELAY set
`* Connected to a77c076c3f1574c8b866f05e59e94f42-2083634759.us-east-1.elb.amazonaws.com (52.2.69.32) port 80 (#0)
> GET /testeng1589?api_key=123 HTTP/1.1
> Host: calypsoqa.api.mashery.com
> User-Agent: curl/7.61.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: Mashery Proxy
< X-Mashery-Responder: trafficmanager-deploy-84d88fd484-fngxt
< Date: Tue, 12 Nov 2024 10:09:13 GMT
< Content-Type: application/json
< Connection: keep-alive
< Server: gunicorn/19.9.0
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Credentials: true
< Content-Length: 349
<
{
"args":
{
"api_key": "123"
},
"headers":
{
"Accept": "*/*",
"Host": "httpbin.org",
"User-Agent": "Mashery Proxy",
"X-Amzn-Trace-Id": "Root=1-67332949-116b42a5182ccee45b302552",
"X-Original-User-Agent": "curl/7.61.1"
},
"origin": "100.64.0.2, 54.204.50.223",
"url": "http://httpbin.org/get?api_key=123"
}
`* Connection #0 to host a77c076c3f1574c8b866f05e59e94f42-2083634759.us-east-1.elb.amazonaws.com left intact [ec2-user@ip-10-0-0-174 ~]$
