Bug 1577811
| Summary: | NPE on various VM operations (update/power-off etc) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Dafna Ron <dron> | ||||
| Component: | Backend.Core | Assignee: | Eli Mesika <emesika> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Liran Rotenberg <lrotenbe> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.3.0 | CC: | ahadas, bugs, dron, emesika, lsvaty, mavital, mperina | ||||
| Target Milestone: | ovirt-4.3.0 | Flags: | rule-engine:
ovirt-4.3+
|
||||
| Target Release: | 4.3.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-4.3.0_alpha | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-02-13 07:48:04 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Dafna Ron
2018-05-14 07:58:42 UTC
Looks like a problem in JDBC.
With psql it seems fine:
engine=> select getNonCountableQutoaVmStatuses();
getnoncountablequtoavmstatuses
--------------------------------
0
13
14
15
(4 rows)
But calling that from Java raises an NPE.
Happen only on the master branch. (In reply to Arik from comment #2) > Happen only on the master branch. Ahh, only on Fedora 28 or also CentOS? (In reply to Martin Perina from comment #3) > (In reply to Arik from comment #2) > > Happen only on the master branch. > > Ahh, only on Fedora 28 or also CentOS? On my environment, it happened on Fedora 26. Dafna, can you please shed more light on the OST jobs that failed? Related to the upgrade to Spring 5 : In commit 608a0e46 (core: Bump Spring dependency), Spring dependency updated to 5.0.4. Spring JDBC 5 is slightly stricter than Spring JDBC 4, and no longer allows null MapSqlParameterSources. Apparently not all DAOs were changed Ala already have a patch on that after failing power-off a VM , I had tested that related patch solve the update VM issue as well What are the reproduction steps? (In reply to Israel Pinto from comment #6) > What are the reproduction steps? 1) Open a VM for editing and try to update and save its description 2) power-off a VM Verified on: ovirt-engine-4.3.0-0.0.master.20181008123033.gitf23e91f.el7.noarch Steps: 1. Edit a VM's description. 2. Start the VM. 3. Edit the VM's description again. 4. Power-off the VM. 5. Search for NPE in the engine log. Results: Actions passed without any error. This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |