[BUG]

[peckmz]

Describe the bug
Getting the following message when attempting Journeys per-app migration:

"Some of the Virtual Servers are not compliant with AS3. Only Tenants with all green Applications/VS' can be later converted to AS3 and deployed to a BIG-IP instance.
Please drill down to uncompliant VS' and fix unsupported configurations using the editor provided."

It does not explain why or how or why the uncompliant virtuals are not compliant. There is no noticeable difference between the "compliant" and "uncompliant" virtual servers.

To Reproduce
Steps to reproduce the behavior:

Import a ucs file into Journeys and you will see this message as soon as the ucs is processed.
Expected behavior
Need to understand the reason why some virtual servers are marked red.

Please specify, app version:
Version 3.3.5

And Platform version of the system you want to migrate.
Migrating from iSeries to rSeries platform - both 15.1.8 version of TMOS

[peckmz]

I drilled down to the uncompliant virtual servers a little more, and noticed that they all have two things in common:

1. They all have a seem to be irrelevant snippet of bigip_base.conf file included
2. They all have been previously created by an iApp, not manually.

[peckmz]

So, the question is: can we rely on Journeys to be able to process iApp created apps? Or migrating them manually is the only option?

[wojtek0806]

There is a misunderstanding, I do not think we support iApp created Virtuals yet, per-app migration is for the user to group up their resources and bring them over into AS3 on BIG-IP configuration. Resources need to be created outside of iApps.
As far as higlighting the problematic config, we have an open enchantment request for this to help users determine non-compliant config: #104