Hello,
I run into an issue, that the value of the CPU variable is not carried over from VM template to instance when using Sunstone interface. Value of variable CPU is filled with the value of variable VCPU from template instead.
Is it a bug or am I doing something wrong?
I am using OpenNebula 7.4.0 but I noticed the same behavior on OpenNebula 7.2.0.
Vojta
Hi, do you mean it’s not implemented on VM instantiation or not saved in the template after edit at all?
What about template modifications in the CLI?
It’s a weird case, I checked in the 7.4.1 and 7.2.1. CPU value is saved and propagated correctly, so it might be a browser glitch. First check whether template parameters are saved correctly after modification.
Edit: Checked also in 7.4.0 clean install and it works correctly. I set for example 2 CPUs/4 vCPUs and a VM has been spinned up exactly with those parameters so that’s certainly some deployment-specific issue. Have you tried to restart opennebula & opennebula-fireedge services? Maybe they spit some useful info in logs but I’d rather advise to deploy a new frontend and see yourself. I’m pretty sure on the new install it will work.
It is like a Sunstone bug rather than something in your template, especially since you can reproduce it on both 7.2 and 7.4. CPU and VCPU are separate VM attributes, so the CPU field shouldn’t automatically inherit the VCPU value. I’d compare the generated VM template/instance with the values shown in Sunstone. If the backend has the correct CPU value but Sunstone displays VCPU, that would pretty clearly point to a UI issue.