Bug ID 899609: Deployment of an imported Existing Application SSL Orchestrator topology may fail from BIG-IQ

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IQ SSL Orchestrator(all modules)

Known Affected Versions:
7.1.0, 7.1.0.1, 7.1.0.2, 7.1.0.3, 7.1.6, 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2, 7.1.8, 7.1.8.1, 7.1.8.2, 7.1.8.3, 7.1.8.4, 7.1.8.5, 7.1.9, 7.1.9.7, 7.1.9.8, 7.1.9.9, 8.0.0, 8.0.0.1

Opened: Apr 15, 2020

Severity: 3-Major

Symptoms

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.

Impact

You cannot deploy an imported 'Existing Application' SSL Orchestrator topology from BIG-IQ.

Conditions

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.

Workaround

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.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips