Closed ramondg closed 4 years ago
this may be due to the permissions, we should use projects in that case
I did not see any 403 permission denied errors looking at the network stream. Also, I have loaded the admin credentials. Furthermore, I can create a VM through a yaml file and browse all the namespaces..
hmm, that is weird. Did the other fields get populated successfully ?
Yes they did, can you point out where in the code this data is being loaded?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@kubevirt-bot: Closing this issue.
Seems like namespaces in the Create VM from wizard window are not properly fetched. The list is empty. Deploying a VM from yaml works like a charm!