Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Security Solution] Error is displaying under cases tab after upgrade from 7.11.1 to 7.12.0 #92819

Closed
ghost opened this issue Feb 25, 2021 · 13 comments · Fixed by #93092
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. QA:Validated Issue has been validated by QA Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting Security Solution Threat Hunting Team v7.12.0

Comments

@ghost
Copy link

ghost commented Feb 25, 2021

Description
Error is displaying under cases tab after upgrade from 7.11.1 to 7.12.0

Build Details:

Version: 7.12.0 BC2
Build: 39000
Commit: 4f65a5a1268fa78f1af9117d12312e1cee433376
Artifacts: https://staging.elastic.co/7.12.0-37f40745/summary-7.12.0.html

Browser Details:
All

Preconditions:

  1. 7.11.1 Environment should exist.
  2. Endpoint security should be installed.
  3. Cases should be created with connectors.

Steps to Reproduce:

  1. Upgrade the build from 7.11.1 to 7.12.0
  2. Navigate to the cases tab
  3. Observe that no cases are displayed. Moreover, error is displayed: 'Error fetching data'

Impacted Test case:
N/A

Actual Result:
Error is displaying under cases tab after upgrade from 7.11.1 to 7.12.0 build

Expected Result:
Cases should be displayed under the cases tab after upgrade from 7.11.1 to 7.12.0 build

What's working:
N/A

What's not working:
N/A

Screenshot:
Cases_upgrade
Cases

@ghost ghost added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Feb 25, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@ghost
Copy link
Author

ghost commented Feb 25, 2021

@muskangulati-qasource Please review!!

@muskangulati-qasource muskangulati-qasource changed the title [Security Solution] Error is displaying under cases tab after upgrade 7.11.1 -> 7.12.0 BC2 [Security Solution] Error is displaying under cases tab after upgrade from 7.11.1 to 7.12.0 Feb 25, 2021
@muskangulati-qasource
Copy link

Reviewed and assigned to @MadameSheema

@muskangulati-qasource muskangulati-qasource added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Feb 25, 2021
@MadameSheema MadameSheema added the Team:Threat Hunting Security Solution Threat Hunting Team label Feb 25, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@MadameSheema
Copy link
Member

@deepikakeshav-qasource if you refresh the page you continue having that issue?

@XavierM please help to prioritise this, thanks

@MadameSheema
Copy link
Member

Found during BC2 regression elastic/security-team#843

@ghost
Copy link
Author

ghost commented Feb 25, 2021

@deepikakeshav-qasource if you refresh the page you continue having that issue?

Hi @MadameSheema

Thanks for looking into the Issue.

However, the issue was persisting after refresh also and even done the hard refresh fn+f5.

We tested it on the incognito tab also, it was occurring there too.

Please let us know if something else needs to be tried.

Thanks!

@jonathan-buttner
Copy link
Contributor

@deepikakeshav-qasource @MadameSheema can you describe the steps you used to reproduce this? I tried creating a few cases with user comments (no alerts though) on 7.11.1 and upgrading to 7.12.0 but didn't see any issues

image

Or if you could email me the creds and URL of the cloud instance that is failing that'd be helpful.

@jonathan-buttner
Copy link
Contributor

cc: @michaelolo24 ^^

@ghost
Copy link
Author

ghost commented Mar 1, 2021

Hi @jonathan-buttner

Thank you for looking into it.

Steps to reproduce:

  1. Deployed the cloud production build of 7.11.1.
  2. Navigate to the cases tab.
  3. Click on "Edit External Connection".
  4. Add the connectors [JIRA, IBM, Service Now]
  5. Click on back to the cases.
  6. Create the cases for [JIRA, IBM, Service Now]
  7. Now upgrade the build from 7.11.1 to 7.12.0.
  8. After up-gradation has done navigate to the Cases tab and observe that an error message is displayed.

Observation: If we add only JIRA connector in 7.11.1 build and create the case then issue is not occurring after upgrade from 7.11.1 to 7.12.0.

Screenshot:
Added all 3 connectors [JIRA, IBM, Service Now]
Cases_error

Moreover, We have shared the credentials over email.

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

Thanks!!

@MadameSheema MadameSheema added v7.12.0 impact:critical This issue should be addressed immediately due to a critical level of impact on the product. and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Mar 1, 2021
@MadameSheema
Copy link
Member

@deepikakeshav-qasource can you please validate the fix of this on BC3? Thanks :)

@ghost
Copy link
Author

ghost commented Mar 4, 2021

Hi @MadameSheema

We have validated this ticket on 7.12.0 BC3 and observe that issue is fixed.

  • Old Cases are displayed under the cases tab after upgrade from 7.11.1 to 7.12.0 build, also able to create the new cases.

Screenshots:
7.11.1 Build
cases_7 11 1

After upgrade to 7.12.0
Cases_list_7 12 0

Hence, We are closing this Ticket.

Thanks!!

@ghost ghost closed this as completed Mar 4, 2021
@ghost ghost added the QA:Validated Issue has been validated by QA label Mar 4, 2021
@ghost
Copy link

ghost commented Mar 30, 2021

Bug Conversion:

Created 01 Test Case for ticket:
https://elastic.testrail.io/index.php?/cases/view/76938

Thanks!!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:critical This issue should be addressed immediately due to a critical level of impact on the product. QA:Validated Issue has been validated by QA Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting Security Solution Threat Hunting Team v7.12.0
Projects
None yet
5 participants