[Fleet][Nginx]: Unable to upgrade Nginx integration policy from v0.2.4 to v0.7.0.

[amolnater-qasource]

Kibana version: 7.15.0 BC-1 Kibana Cloud environment

Host OS and Browser version: All, All

Build details:

Build: 43636
Commit: d791226d9385122f33f4a5ca38fa5369012fbec3

Preconditions:

1. 7.15.0 BC-1 Kibana Cloud environment should be available.
2. Lower version Nginx integration should be available, say 0.2.4.

Steps to reproduce:

1. Login to Kibana environment.
2. Add Lower version Nginx integration to Default Policy.
3. Observe v0.2.4 version Nginx added to Default Policy.
4. Upgrade Nginx integration from Settings, i.e, v0.7.0.
5. After successful upgrade navigate to Default Policy and click [Upgrade] button available in front of Policy.
6. Observe below warnings:

Review field conflicts
This integration has conflicting fields from version to Review the configuration and save to perform upgrade. You may reference your previous configuration for comparison.

What's working fine:
We are successfully able to upgrade Apache v0.5.0 to v0.8.1

Expected Result:
User should be able to upgrade Nginx integration from v0.2.4 to v0.7.0

Screen Recording:

2_unable.to.upgrade.mp4

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Reviewed & assigned to @jen-huang

CC: @EricDavisX

[joshdover]

cc @kpollich

[EricDavisX]

@dikshachauhan-qasource @amolnater-qasource adding to high impact list.

[jen-huang]

@amolnater-qasource @hop-dev This might be expected behavior. This is part of the feature, if a package has too many changes between versions and we cannot upgrade the policy automatically, it is expected for the user to be redirected to the policy editor with a warning, see PR description: #107171

@EricDavisX I would not consider this high impact based on the above. Note that this does not block upgrade of the package itself. This deals with upgrading the policy.

Due to the near infinite possible combinations of upgrading from a particular version to another, we cannot provide a list of what is expected to yield an automatic upgrade vs this manual upgrade with conflict message.

[EricDavisX]

we can re-test this in the BC and with the next snapshot to confirm it is fixed - thanks all.