Last Modified: May 03, 2021
See more info
BIG-IQ SSL Orchestrator
Known Affected Versions:
7.1.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 7.1.6, 184.108.40.206, 7.1.7, 220.127.116.11, 18.104.22.168, 7.1.8, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 7.1.9, 18.104.22.168, 22.214.171.124, 126.96.36.199, 8.0.0, 188.8.131.52
Opened: Apr 15, 2020
A deployment of an SSL Orchestrator topology can fail if that topology is an Existing Application type topology, and if the configuration was imported from a managed BIG-IP to the BIG-IQ.
You cannot deploy an imported 'Existing Application' SSL Orchestrator topology from BIG-IQ.
For this condition to occur, an Existing Application topology must be deployed in BIG-IP and then imported back to BIG-IQ. After this, any redeployment of this imported topology which uses the Existing Application configuration type may fail.
Currently, there is no direct workaround to redeploy the imported topology without a deployment failure. Instead, you can delete the topology that is failing and deploy a new Existing Application topology with the same configuration.