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

Start and stop button do not appear #170

Open
samu8991 opened this issue Nov 22, 2024 · 5 comments
Open

Start and stop button do not appear #170

samu8991 opened this issue Nov 22, 2024 · 5 comments

Comments

@samu8991
Copy link

Hello,
Setup:

  • k8s cluster
    • Client Version: v1.28.14
      Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
      Server Version: v1.28.15
  • kubevirt
    • targetKubeVirtVersion: v1.4.0
  • rancher v2.10
  • kubevirt dash board extension (1.1.0, 1.2.0)

Issue:
I can not see the start and stop buttons related to VMs
I do not see any relevant error, everything seems to work because it appears the kubevirt section on the left when I install the extension, the only problem is the buttons
I tried both kubevirt dashboard extension versions, same issue

Regards

@jtomasek
Copy link
Contributor

Can you please provide the VM resource manifest you're using? The ability to start/stop the VM depends on whether spec.running is defined vs spec.runStrategy is defined. See runStrategy for more details. There is also a Run Strategy column in the Virtual machines list.

@samu8991
Copy link
Author

samu8991 commented Nov 25, 2024

kind: VirtualMachine 
metadata:            
  name: vm1          
  namespace: default 
spec:                
  runStrategy: Always
  template:          

Thanks for the answer!
This is what it looked like when I opened the issue.
Now I tried with spec.running: true and it works, in the sense that I can see the buttons and they work. The problem is that I keep getting a warning related to the use of spec.running. Moreover, the documentation states that: runStrategy: Always: [...] This behavior is equal to spec.running: true but I am not experiencing that.
Regards

@jtomasek
Copy link
Contributor

Can you please elaborate on what exact warning you're getting related to the use of spec.running?

Note that as the documentation states, the use of spec.running and spec.runStrategy is mutually exclusive and the API server won't let you use both at once.

spec.runStrategy: Always is the same as spec.running: true in a sense that in both cases the system is tasked with keeping the VM in a running state - in case when the VM crashes or is manually shut down from within the quest, the VirtualMachineInstance will be immediately respawned to get the VM running again.

@samu8991
Copy link
Author

Screenshot from 2024-11-26 11-47-25
This is what I see but If I do what it says, i.e use spec.runStrategy: Always instead of spec.running true, I can not see the start and stop buttons

@jtomasek
Copy link
Contributor

jtomasek commented Nov 26, 2024

I see that the spec.running has been deprecated in KubeVirt v1.4. That's why you're seeiing the warning. The latest version of KubeVirt extension is targeted against the KubeVirt 1.3.1 (Chart available in this repository). We are going to rebase against newer version eventually which will require to adjust the extension to stop using spec.running to start/stop the VM.

When this is done, the actions on the VM will be available when the spec.runStrategy is set to 'Manual'.

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

No branches or pull requests

2 participants