microsoft / microsoft/AzureTRE
TRE processor/UI does not seem to be picking up VM resource status changes/operations
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Describe the bug
We are encountering a situation where requesting VM changes (e.g. Stop/Start) seems to be working but the API never seems to pick up the resource status changing and the UI just spins on the "awaiting action" status. These workspaces/VMs were working normally earlier today and there has not been any code changes since.
Steps to reproduce
- Select a VM in the TRE UI with either the Stopped or Started state.
- Start (or Stop) the VM via the TRE UI
- The Operations page will show "Status: awaiting_action" indefinitely.
- Checking the VM's state via the Azure Portal shows it in the Running (or Stopped) state.
Azure TRE release version (e.g. v0.14.0 or main):
v0.21.0
Deployed Azure TRE components - click the (i) in the UI:
tre-service-guacamole (0.12.9)
tre-service-databricks (1.0.10)
tre-service-azureml (0.9.2)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.