problem
When viewing a resource, for example an instance, that is currently in a project that differs from the currently selected or global project scope, it will attempt to fetch volumes yet none will return as it is only filtering on the ones that are owned by this user (not the project user).
versions
The only relevant version is the UI and management server; replicated on 4.23.0.0. Also replicated this issue to the current HEAD of main.
The steps to reproduce the bug
- Create a project "test".
- Create (for example) and instance under that project "instance-01".
- (Optionally) add another volume to this instance.
- Make sure you have no project enabled at the top of the page ("Default view").
- Go to instances, turn on the project slider and select "instance-01" in the list.
- Browse to the Volumes tab and notice that this list is empty.
What to do about it?
Add the {projectid: "-1"} parameter to this API call. Unsure whether this happens to other resources (like NICs), I have not tested this.
diff --git a/ui/src/components/view/VolumesTab.vue b/ui/src/components/view/VolumesTab.vue
index b65933a643..e4679c02dc 100644
--- a/ui/src/components/view/VolumesTab.vue
+++ b/ui/src/components/view/VolumesTab.vue
@@ -141,7 +141,7 @@ export default {
}
},
getVolumes () {
- getAPI('listVolumes', { listall: true, listsystemvms: true, virtualmachineid: this.vm.id }).then(json => {
+ getAPI('listVolumes', { listall: true, listsystemvms: true, projectid: "-1", virtualmachineid: this.vm.id }).then(json => {
this.volumes = json.listvolumesresponse.volume
if (this.volumes) {
this.volumes.sort((a, b) => { return a.deviceid - b.deviceid })
problem
When viewing a resource, for example an instance, that is currently in a project that differs from the currently selected or global project scope, it will attempt to fetch volumes yet none will return as it is only filtering on the ones that are owned by this user (not the project user).
versions
The only relevant version is the UI and management server; replicated on 4.23.0.0. Also replicated this issue to the current HEAD of
main.The steps to reproduce the bug
What to do about it?
Add the
{projectid: "-1"}parameter to this API call. Unsure whether this happens to other resources (like NICs), I have not tested this.