search

f5devcentral / f5-journeys

F5 Journeys Migration Utility - migrate or upgrade BIG-IP into new F5 platforms
Apache License 2.0
74 stars 17 forks source link

[BUG] #111

Closed peckmz closed 1 year ago

peckmz commented 1 year ago

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. My initial suspicion was that the vs is uncompliant if not all dependancies (like policies, profiles, etc. are have been found by Journeys, but then I saw the same absence of some of the dependancies in other virtuals that were marked green/compliant.

To Reproduce Steps to reproduce the behavior:

  1. Import a ucs file into Journeys and you will see this message as soon as the ucs is processed.

Expected behavior Some sort of explanation of what exactly Journeys was unhappy about would be nice.

Screenshots If applicable, add screenshots to help explain your problem.

Context

azahajkiewicz commented 1 year ago

Journeys supports LTM migrations. If there are any dependent objects missing in the virtual servers' configuration, please open a bug for that.

Please see documentation: https://github.com/f5devcentral/f5-journeys#journey-application-service-migration Uncompliant objects (that cannot be converted to AS3 format) should be highlighted in the editor after saving/verifying config.

peckmz commented 1 year ago

My question was not the missing objects. That was just an unconfirmed guess that turned out to be false. The issue was that Journeys marks a large number of virtual servers uncompliant without providing a reason.

azahajkiewicz commented 1 year ago

My question was not the missing objects. That was just an unconfirmed guess that turned out to be false. The issue was that Journeys marks a large number of virtual servers uncompliant without providing a reason.

The reason is that f5-acc-config-converter cannot convert some of the virtual server's objects to AS3 format - there is no AS3 support for those objects.

azahajkiewicz commented 1 year ago
Screenshot 2023-07-31 at 15 50 02