[Fleet]: Error page on clicking upgrade button for "Windows" integration with v0.8.1.

[amolnater-qasource]

Kibana version: 7.15.0 BC-2 Kibana Cloud environment

Host OS and Browser version: All, All

Build details:

Build: 43742
Commit: 113d5f2a745ab9be7d567d13ff906dfd0f5b7a9a

Preconditions:

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

Steps to reproduce:

1. Login to Kibana environment.
2. Add Lower version Windows integration to Default Policy.
3. Observe v0.8.1 version Windows added to Default Policy.
4. Upgrade Windows integration from Settings, i.e, v1.0.0.
5. After successful upgrade navigate to Default Policy and click Upgrade button in front of Windows integration.
6. Observe Error page on clicking Upgrade button.

Expected Result:
On clicking Upgrade button user should be navigated to Upgrade Windows Integration page.

Screen Recording:

New.Policy.-.Agent.policies.-.Fleet.-.Elastic.-.Google.Chrome.2021-08-26.16-09-56.mp4

Note:
This issue is also observed if we create a policy with Windows integration at 7.13.4 Kibana and then Upgrade 7.13.4 Kibana to 7.15.0 Kibana. On clicking Upgrade button user is redirected to Error page.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Reviewed & assigned to @kpollich

CC: @EricDavisX

[amolnater-qasource]

Hi @kpollich
We have found that this issue is not reproducible when Windows version 0.1.3 is upgraded to 1.0.0.

Further we have observed similar error page on upgrading Linux version v0.3.1 to latest 0.4.1. However Linux integration successfully upgrades from version 0.3.8 to 0.4.1.

Error page for Linux integration version 0.3.1:

Build details:

Build: 43742
Commit: 113d5f2a745ab9be7d567d13ff906dfd0f5b7a9a

Please let us know if anything else is required from our end.
Thanks

[EricDavisX]

can we re-test this on the next passing 7.15 snapshot build please? I expect some fixes may not have made it to BC2 - but are *I think already fixed

[amolnater-qasource]

Hi @EricDavisX
As per feedback we have revalidated these error page issues for both linux(v0.3.1) and windows(v0.8.1) integration upgrade on latest 7.15.0 Snapshot and found it still reproducible.

Build details:
Build: 43832
Commit: b7ad04c

Please let us know if anything else is required from our end.
Thanks

[ghost]

Hi @kpollich
We have observed this issue reproducible on the latest 7.17.0-BC5 build. Please find below the exact testing details:

• Error page on clicking upgrade button for "Windows" integration with v0.8.1.

Screenshot:

Build Details:
VERSION: 7.17.0-BC5
BUILD: 46534
COMMIT: 60a9838
ARTIFACT: https://staging.elastic.co/7.17.0-c7ee4c2a/summary-7.17.0.html#artifacts

Thanks!

[amolnater-qasource]

Further this issue is inconsistently reproducible on 8.0 rc-2 Kibana self-managed environment.

Build details:
BUILD: 49192
COMMIT: 57ca5e1

Screenshot:

Thanks!

[kpollich]

I'm unable to reproduce this on the main or 8.0 branches in my local environment.

Screen.Recording.2022-02-01.at.3.18.34.PM.mov

Perhaps this is fixed in a later build?

[ghost]

Hi @kpollich
We have revalidated this issue on the 7.17.0 release build and found that the issue is fixed now. Please find below the testing details:

Screen-Recording:

Windows.-.Integrations.-.Elastic.-.Google.Chrome.2022-02-02.10-30-10.mp4

Build Details:
VERSION: 7.17.0
BUILD: 46534
COMMIT: 60a9838

Thanks!

[amolnater-qasource]

Hi @kpollich
We have revalidated this issue on 8.0 rc2 BC-4 Kibana cloud build and found this issue not reproducible.

Build details:
BUILD: 49192
COMMIT: 57ca5e1

Screenshot:

As shared by @samratbhadra-qasource it is also not reproducible on released 7.17 Kibana, hence we are closing this issue.
Further we will keep track of this issue, if found it reproducible in future builds.

Thanks

[ghost]

Hi @kpollich
While performing testing on 8.0.1-BC2 build, we have observed that the same issue is still reproducible. Please find below the testing details:

Screen-Recording:

Windows.-.Integrations.-.Elastic.-.Google.Chrome.2022-02-23.13-13-55.mp4

Build Details:
VERSION: 8.0.1-BC2
BUILD: 49348
COMMIT: 28c513e
ARTIFACT: https://staging.elastic.co/8.0.1-e8a5e55a/summary-8.0.1.html

Hence, reopening this issue.

Thanks!

[kpollich]

Original issue reported was for upgrade of Windows integration v0.8.1 -> 1.0.0. The original issue reported is still working correctly on staging 8.0.1. See below:

---

The issue with upgrading from 0.1.3 -> 1.5.0 reported in #110202 (comment) is fixed in 8.1.0. It was fixed in #121628 here:

kibana/x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/components/package_policy_input_panel.tsx

Line 86 in f96af16

const errorCount = inputValidationResults && countValidationErrors(inputValidationResults);

Since 8.0.1 releases tomorrow on 2022-02-24, and there is no 8.0.2 release scheduled, I'm closing this as the issue is fixed w/ an upgrade to 8.1.0.