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

The trashbin button to delete a risk on a specific asset does not work #520

Closed
acherifi opened this issue Nov 30, 2023 · 11 comments
Closed

Comments

@acherifi
Copy link

Describe the bug
When a Information Risk is removed from the knowledge base, informations risk on the affected assets appear in blue with a trash bin icon to remove the risk.
This button does not work. No error appear when clicking the trashbin but the risk is still present.

To Reproduce
Steps to reproduce the behavior:

  1. Add an asset to an asset type
  2. Evaluate the risk for this asset
  3. Remove the information risk linked to the asset type
  4. Try to remove the risk on the asset

Expected behavior
The risk should be deleted

Screenshots
Before clicking the icon
image

After clicking
image

Desktop (please complete the following information):

Questions Answers
Type of issue Bug
OS version (server) Ubuntu
OS version (client) Ubuntu
PHP version The embedded in the Monarc VM
MONARC version / git hash Latest production
Browser Chrome
@ruslanbaidan
Copy link
Contributor

ruslanbaidan commented Nov 30, 2023

I can confirm the issue.
It is related to the global secondary assets' link and removal of other risks.
We are going to provide a fix for that soon, but it would be necessary to migrate to a new VM.
Could you tell if the Monarc cloud service solution works for you ?
So we can create an instance for your organisation and the updates will be done automatically without needs to migrate.

@acherifi
Copy link
Author

If the cloud solution provides the same feature set we would be glad to have an instance.

@ruslanbaidan
Copy link
Contributor

If the cloud solution provides the same feature set we would be glad to have an instance.

It's the same tool. The instances are deployed per organisation https://www.monarc.lu/service/
Could you request the access by contacting us on the email instance-monarc@nc3.lu with your organisation name and primary user first, last names and email address.

@acherifi
Copy link
Author

Thank you very much. The email has been sent.

@acherifi
Copy link
Author

acherifi commented Nov 30, 2023

Another question: I am trying to import a JSON risk assessment file. If the import takes longer than the session timeout, is the import fully done or does the session timeout interrupt the import ?

@ruslanbaidan
Copy link
Contributor

ruslanbaidan commented Nov 30, 2023

Another question: I am trying to import a JSON risk assessment file. If the import takes longer than the session timeout, is the import fully done or does the session timeout interrupt the import ?

Import process will be continued after the session timeout reached until it's done or failed.

@ruslanbaidan
Copy link
Contributor

@acherifi
Copy link
Author

acherifi commented Dec 1, 2023

Thank you very much for the fix. I solved my issue with a quickfix by removing in the DB, the instances_risks with an amv_id at null

DELETE FROM monarc_cli.instances_risks
WHERE amv_id is NULL;

@ruslanbaidan
Copy link
Contributor

Thank you for the information.
It could be that the missing amvs appeared when there was an issue with removal.
It would be good to try reproducing this issue on the latest code base (with applied code fix). New VM is also available.
And if those records appear by the other reasons, we have to look for an another issue.

@acherifi
Copy link
Author

acherifi commented Dec 4, 2023

I can confirm that it works perfectly on the latest code base with the fix.
Thank you for the reactivity

@ruslanbaidan
Copy link
Contributor

You are welcome.
Thanks for the confirmation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants