Bug 1651840
Summary: | Power up of HostedEngine environment does not connect Host to all storage domains | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Germano Veit Michel <gveitmic> |
Component: | BLL.Storage | Assignee: | Benny Zlotnik <bzlotnik> |
Status: | CLOSED DUPLICATE | QA Contact: | Avihai <aefrat> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.2.7 | CC: | bugs, bzlotnik, gscott, gveitmic, mkalinin, mperina, tnisan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-05-24 19:46:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1772688 |
Description
Germano Veit Michel
2018-11-21 02:17:51 UTC
(In reply to Germano Veit Michel from comment #0) > It happens on this situation: > 1. Enable global maintenance > 2. Migrate Hosted-Engine to Host X > 3. Shutdown the Hosted-Engine > 4. Power cycle the host > 5. Start Hosted-Engine on Host X Here the engine is also going to start on the engine. AFAIK after engine start there is a kind of grace period where the engine should try to reconcile hosts status before taking any further action. We should investigate why this wasn't enough in the reported case. > 6. HostedEngine goes up on Host X > - Host X is still in Up state in the DB since step 2 > 7. Host X is in Up state, but engine did not send connectStorageServer > commands to connect to all other SDs, it is only connected to hosted_storage > (master). (In reply to Germano Veit Michel from comment #0) Please use : Host A = initial Hosted-Engine Host Host X = New Hosted-Engine Host > > It happens on this situation: > 1. Enable global maintenance > 2. Migrate Hosted-Engine to Host X > 3. Shutdown the Hosted-Engine which one ? A or X ??? > 4. Power cycle the host which one ? A or X ??? > 5. Start Hosted-Engine on Host X > 6. HostedEngine goes up on Host X > - Host X is still in Up state in the DB since step 2 > 7. Host X is in Up state, but engine did not send connectStorageServer > commands to connect to all other SDs, it is only connected to hosted_storage > (master). (In reply to Eli Mesika from comment #2) > (In reply to Germano Veit Michel from comment #0) > > Please use : > > Host A = initial Hosted-Engine Host > Host X = New Hosted-Engine Host > > > > > It happens on this situation: > > 1. Enable global maintenance > > 2. Migrate Hosted-Engine to Host X > > 3. Shutdown the Hosted-Engine > > which one ? A or X ??? X > > > 4. Power cycle the host > > which one ? A or X ??? X > > > > 5. Start Hosted-Engine on Host X > > 6. HostedEngine goes up on Host X > > - Host X is still in Up state in the DB since step 2 > > 7. Host X is in Up state, but engine did not send connectStorageServer > > commands to connect to all other SDs, it is only connected to hosted_storage > > (master). In fact, I think any order will reproduce this, I get this bug every single time I power up my test environment. This warning is related to storage Please look at IrsProxy::addDomainInProblemData Seems that in that case host must go to non-operational Tal, can you take a look and move to storage ? This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. Closing the upstram bug in favor of downstream, to concentrate efforts. *** This bug has been marked as a duplicate of bug 1772688 *** |