mattermost-plugin-jira
mattermost-plugin-jira copied to clipboard
mattermost
Isolated case where instance is in the "list" key but its correct key is not found in the KV store
I have one isolated case where and instance ID is wrong and the instance cannot be uninstalled.
As per Lev instance is in the "list" key, but its own key is not found in the KV store
I will attempt to find reproduction steps.
Observed Steps:
- Deployed latest Jira
- Run
/jira setup - Use Setup flow to install the intance
- Run
/jira list
Observed: KV store shows an error and instance ID is wrong.
@levb - could the growth spike -related changes introduce this? Dylan has the instance preserved if needed.
@catalintomai Yes, but it was likely the result of testing and failing. There are no specific steps to reproduce AFAIK.
@dipak-demansol I have added observed steps. Please follow to see if you encounter the issue.
@DHaussermann i did testing with latest master build and it worked, issue not generated but when i was doing some experiment then in the jira i was getting this error while Upload the Mattermost app to Jira
it can be a issue or we can ignore it?
More details to add for this:
- @dipak-demansol was having an installation issue above ☝️
- We did not yet investigate his setup issue
- I then saw the instance as
Setup in-progress - I went and setup the same Cloud MM test instance on separate serve
- Now @dipak-demansol servers shows the issue
A. Maybe the logs on https://dipak-ha-04.test.mattermost.cloud/ can shed some light on this? B. Is it conceivable that installing a different MM server on the the same instance while setup is in progress could affect this? I'm curious if actions on the Jira side could affect the results.
@DHaussermann @hanzei @mickmister I am not able to reproduce this error. From the screenshots, it is looking like a Jira cloud instance so I tried installing that both using /jira setup and /jira instance install cloud <url> and both worked fine for me. I also tried your reproduction steps which also worked fine for me. Please let me know whether I should try this for jira server/datacenter as well.
Just on a different note, this issue is looking similar to the issue https://github.com/mattermost/mattermost-plugin-jira/issues/902 for which I have created a PR https://github.com/mattermost/mattermost-plugin-jira/pull/914. Please see whether this PR solves this issue as well.
