bwsw / cloudstack-ui

Modern UI for Apache Cloudstack User Self Service Portal
https://bitworks.software/
Apache License 2.0
164 stars 63 forks source link

Error and wrong notification in pending operation appear when try to detach ISO from VM #1581

Closed evgeniiamokhova closed 5 years ago

evgeniiamokhova commented 5 years ago

Description

Error "failed to detach" and the notification "NOTIFICATIONS.VM.DETACHMENT_FAILED" in the pending operations appear when try to detach ISO from VM. At the next attempt to detach ISO the detachment occurs without error.

Steps to reproduce

1) Login by user 2) Go to tab Storage in the sidebar of VM 3) Click Attach ISO 4) Choose any ISO 5) Click Attach 6) Click Detach 7) Click in dialog Yes 8) Click in modal Ok 9) Click Pending operation

Actual result

Error "failed to detach" and the notification "NOTIFICATIONS.VM.DETACHMENT_FAILED" in the pending operations appear

Expected result

Error isn't translated to Russian " Не удалось открепить ISO" and notification about error should be "Failed to detach ISO"/ "Не удалось открепить ISO"

Environment


Browser:
- [ x ] Chrome version XX
- [ x ] Firefox version XX
- [ x ] Safari version XX
- [ x ] Opera version XX
- [ x ] IE version XX
- [ x ] Edge version 

Connected requirement IDs

REQ_VM_DTLS_024

Screenshots

2019-02-13 16-17-26 2019-02-13 16-22-11

dron8552 commented 5 years ago

TO TEST: REQ_VM_DTLS_024

nikonov1996 commented 5 years ago

@dron8552 1) Error text not translated. Steps to reproduce:

  1. Login by user
  2. Go to tab Storage in the sidebar of VM
  3. Click Attach ISO
  4. Choose any ISO
  5. Click Attach
  6. Click Detach
  7. Click in dialog Yes
  8. Click in modal Ok
  9. Click Pending operation image

2) ISO not detached from first time. Steps to reproduce:

  1. Login by user
  2. Go to tab Storage in the sidebar of VM
  3. Click Attach ISO
  4. Choose any ISO
  5. Click Attach
  6. Click Detach
  7. Click in dialog Yes
  8. Click in modal Ok
  9. Click Detach
  10. Click in dialog Yes image
dron8552 commented 5 years ago

1 - was fixed. 2 - @ershovaelena this error reproduces in the original interface, it seems to be the CS bug.