[Fleet]: Inappropriate error message on editing preinstalled integration that is no longer compatible.

[amolnater-qasource]

Kibana version: Upgraded 8.0.1 BC-2 Kibana cloud environment

Host OS and Browser version: All, All

Build Details:
BUILD: 49348
COMMIT: 28c513e

Preconditions:

1. Upgraded 8.0.1 BC-2 Kibana cloud environment should be available.
2. Cyberark integration should be added to a policy before upgrade from 7.17>8.0.1

Steps to reproduce:

1. Upgrade 7.17 to 8.0.1 Kibana environment.
2. Navigate to Agent Policies and observe cyberark integration available.
3. Click Edit cyberark integration and observe inappropriate error message.
4. Click on CyberArk integration which navigates to the overview page and observe not so descriptive message.

Expected Result:
Detailed message should be there on editing preinstalled integration that is no longer compatible.

Suggestion:

• CyberARK integration is not compatible with current kibana version. message could be used.

Screenshots:
Edit Cyberark integration:

Overview page for cyberark integration:

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Secondary Review is Done for this ticket

[joshdover]

Setting to impact:low since these packages are deprecated and were never GA, and the impact is localized to these packages.

@amolnater-qasource would you be able to test whether or not this is reproducible after upgrading to 8.2.0-SNAPSHOT? We've made some improvements in that version around this.

[amolnater-qasource]

Hi @joshdover
We have attempted to validate on 7.17.1 upgrade to 8.2.0-Snapshot and we had below observations:

• Installed cyberark integration and upgraded kibana to 8.2.0.

Screenshots for Edit cyberark integration and Integration overview page:

Build details:
BUILD: 50714
COMMIT: 556d0d0

Please let us know if anything else is required.
Thanks!

[amolnater-qasource]

Hi Team
We have revalidated this issue on upgraded 8.2 BC4 Kibana cloud environment and found this issue still reproducible.

• Inappropriate error message on editing preinstalled integration that is no longer compatible(Cisco).

Build details:
VERSION: 8.2.0 BC4
BUILD: 52005
COMMIT: 9a5003d

Screenshot:

Thanks

[jen-huang]

@joshdover I wonder if this might be resolved with the fix from #129999? The situation feels similar: the already-installed package is not available from registry (due to version constraints), so we fallback to building it from ES. I mocked this scenario on main and did not run into the error, logs say the missing package was retrieved from ES:

[2022-04-27T15:46:10.796-07:00][DEBUG][plugins.fleet] retrieved installed package cisco-0.12.5 from ES

[jen-huang]

@amolnater-qasource Could you re-validate this on a 8.2.1 build? I suspect a fix was merged.

[amolnater-qasource]

Hi @jen-huang
We have revalidated this issue on upgrading 7.17.4 to 8.2.1 BC2 Kibana cloud environment and found this issue fixed now.

• Edit integration page and Integration overview page is now available without any errors for deprecated integrations:
  • CyberARK
  • Cisco Logs

Screenshots for CyberARK:

Build details:
BUILD: 52192
COMMIT: d4427fa

Hence we are closing this issue and marking it as QA:Validated.
Thanks