| Summary: | [engine-backend] NPE during ChangeVDSCluster | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Elad <ebenahar> | ||||
| Component: | BLL.Infra | Assignee: | Yevgeny Zaspitsky <yzaspits> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Pavel Stehlik <pstehlik> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.6.3.2 | CC: | bugs, danken, ebenahar, masayag | ||||
| Target Milestone: | ovirt-3.6.5 | Keywords: | Regression | ||||
| Target Release: | --- | Flags: | danken:
ovirt-3.6.z?
rule-engine: blocker? ebenahar: planning_ack? masayag: devel_ack+ ebenahar: testing_ack? |
||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-02-25 12:36:00 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Happens also from Hosts tab -> edit host. Cannot change host cluster at all (from Webadmin). Therefore, changing severity to urgent. Please share ALL logs from the logs directory in the engine. All /var/log/ content from engine: http://file.tlv.redhat.com/ebenahar/bug2.tar.gz This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. Elad, Please explain the scenario: 1. How the environment was created? Was that a fresh install or an upgrade? 2. What cluster the host belongs prior moving it to the new one? Is this a valid cluster (belongs to a DC)? Is cluster management network defined properly? (In reply to Yevgeny Zaspitsky from comment #5) > Elad, > > Please explain the scenario: > 1. How the environment was created? Was that a fresh install or an upgrade? Upgrade > 2. What cluster the host belongs prior moving it to the new one? Is this a > valid cluster (belongs to a DC)? Is cluster management network defined > properly? The host was part of a valid cluster belongs to a DC. no special network configured in these clusters, only the management network. The host was Up in the first cluster The problem isn't reproducible. |
Created attachment 1129250 [details] engine and server logs Description of problem: Changed one of the host's clusters from cluster creation wizard in Webadmin and got a general command failure in UI accompanied by a NullPointerException. The Host cluster remains the old one, the operation failed. Version-Release number of selected component (if applicable): rhevm-3.6.3.2-0.1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Have a host in maintenance 2. Create a new DC and cluster from the DC and cluster creation wizard 3. Pick 'Select host' with the host in maintenance Actual results: Getting a 'general command failure' in UI with a NullPointerException in engine.log: 2016-02-22 11:36:13,421 INFO [org.ovirt.engine.core.bll.ChangeVDSClusterCommand] (ajp-/127.0.0.1:8702-3) [2fcf61e1] Lock Acquired to object 'EngineLock:{exclusiveLocks='[58ff7df3-4e94-4a81-b3ef-4bd18ae42a0d=<VDS, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}' 2016-02-22 11:36:13,426 ERROR [org.ovirt.engine.core.bll.ChangeVDSClusterCommand] (ajp-/127.0.0.1:8702-3) [2fcf61e1] Error during CanDoActionFailure.: java.lang.NullPointerException at org.ovirt.engine.core.bll.ChangeVDSClusterCommand.isSameManagementNetwork(ChangeVDSClusterCommand.java:225) [bll.jar:] at org.ovirt.engine.core.bll.ChangeVDSClusterCommand.canDoAction(ChangeVDSClusterCommand.java:160) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.internalCanDoAction(CommandBase.java:791) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.canDoActionOnly(CommandBase.java:352) [bll.jar:] at org.ovirt.engine.core.bll.MultipleActionsRunner.canRunActions(MultipleActionsRunner.java:103) [bll.jar:] at org.ovirt.engine.core.bll.MultipleActionsRunner.invokeCommands(MultipleActionsRunner.java:91) [bll.jar:] at org.ovirt.engine.core.bll.MultipleActionsRunner.execute(MultipleActionsRunner.java:63) [bll.jar:] The Host cluster remains the old one, the operation failed. Expected results: Host cluster should change successfully. Additional info: engine and server logs