Hi Paul,
please select oVirt / ovirt-engine [1] when creating the new bug and then select the Backend core component and the SLA team.
[1] https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
Regards
-- Martin Sivák SLA / oVirt
On Thu, Sep 15, 2016 at 4:11 PM, Paul Dyer pmdyermms@gmail.com wrote:
hi Roy,
we don't have VMs on that cluster any more. They were moved to a new cluster, from amd to intel architecture.
What is the SLA team? Is there a bugzilla that relates to SLA?
Thank you, Paul
On Thu, Sep 15, 2016 at 1:25 AM, Roy Golan rgolan@redhat.com wrote:
Hi Paul please open a bug on SLA team and put the steps to reproduce there with the logs. BTW I think you got VMs on that cluster, so remove them or move them to another cluster before removing the cluster
On 14 September 2016 at 20:40, Oved Ourfali oourfali@redhat.com wrote:
As far as I know cpu profiles are SLA related. CC-ing Roy and Martin as they might be able to help.
It sounds familiar to me, so perhaps will be fixed in 4.0.4.
Thanks, Oved
On Sep 14, 2016 20:36, "Paul Dyer" pmdyermms@gmail.com wrote:
I am using ovirt 4.0.3, and have a cluster that no longer has any hosts attached. On remove, the operation fails. The engine log shows this error.
ERROR: new row for relation "vm_static" violates check constraint "vm_static_cpu_profile_not_null"
I tried to remove the CPU profile from the cluster, but receive this warning:
2016-09-14 12:34:29,540 WARN [org.ovirt.engine.core.bll.profiles.RemoveCpuProfileCommand] (default task-47) [] Validation of action 'RemoveCpuProfile' failed for user admin@internal. Reasons: VAR__ACTION__REMOVE,VAR__TYPE__CPU_PROFILE,ACTION_TYPE_CANNOT_REMOVE_LAST_CPU_PROFILE_IN_CLUSTER
It seems I have some constraint loop.
Thanks, Paul
-- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750
vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/vdsm-devel@lists.fedorahosted.org
-- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750