Bug 989221
Summary: | vms_sp.sql argument error in InsertVm function | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Shahar Havivi <shavivi> |
Component: | ovirt-engine-core | Assignee: | Shahar Havivi <shavivi> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | acathrow, iheim, juan.hernandez, michal.skrivanek, ofrenkel, shavivi, yeylon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | virt | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-23 07:28:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Shahar Havivi
2013-07-28 13:39:08 UTC
Shahar, how did you detect this? Was it doing a code inspection or did you detect it as a real problem? I ask because as far as I can tell this stored procedure is only called from the VmDAO.save() method, and that method isn't currently (in the current master) called by anyone. This is important to determine, as if it is actually causing a problem then we need to backport it to 3.2.z. (In reply to Juan Hernández from comment #1) I did not encounter any problem, I notice the bug by examining the function. We may have a hidden bug, if not we centrally have a potential one. I checked this in the downstream 3.2.z branch and, like in the upstream master, the VmDAO.save() method isn't called at all, so this change doesn't need to be backported. I would also suggest to remove the VmDAO.save() method and the stored procedure. (In reply to Juan Hernández from comment #3) > I would also suggest to remove the VmDAO.save() method and the stored > procedure. Omer note that two... Michal, what do you think? I'm fine with cleanup, as soon as Omer confirms it's not needed and there are no plans to use it since currently no one uses it, i prefer to remove it, no point for unused code. as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this) closing as this should be in 3.3 (doing so in bulk, so may be incorrect) |