Bug 1389455
| Summary: | Trying to use extended LUN size results in REFRESH_LUN_ERROR | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Barak Korren <bkorren> | ||||
| Component: | BLL.Storage | Assignee: | Fred Rolland <frolland> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Kevin Alon Goldblatt <kgoldbla> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.0.4.4 | CC: | amureini, bugs, frolland, tnisan | ||||
| Target Milestone: | ovirt-4.0.5 | Keywords: | Regression, Reopened | ||||
| Target Release: | 4.0.5.5 | Flags: | amureini:
ovirt-4.0.z?
amureini: blocker? rule-engine: planning_ack? amureini: devel_ack+ rule-engine: testing_ack+ |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1397950 (view as bug list) | Environment: | |||||
| Last Closed: | 2016-11-24 09:40:34 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: | 1397950 | ||||||
| Attachments: |
|
||||||
Tested with the following code: ---------------------------------------- rhevm-4.0.5.5-0.1.el7ev.noarch vdsm-4.18.15.2-1.el7ev.x86_64 Tested with the following scenario: Steps to Reproduce: Steps to Reproduce: 1. setup a system with iSCSI storage and multiple hosts 2. extend an iSCSI lun in the storage 3. Go into "Manage Domain" for the domain containing the LUN, the added capacity should show up in the "Additional Size" column. 4. Click on the button showing the additional size and click ok Actual results: The storage domain should NOW HAS the new capacity. grep -o "deviceSize='[^']*'" engine.log reports the correct old and new LUN sizes Expected results: Moving to VERIFIED! 4.0.5 has been released, closing. |
Created attachment 1214657 [details] engine.log of the failed command Description of problem: When trying to have engine make use of some extra space added to a pre-existing iSCSI LUN, the adding of space fails with REFRESH_LUN_ERROR. Looking at engine.log the following error shows up: Failed to refresh LUNs. Not all VDS are seeing the same size Comparing device sizes that show up on the engine.log (as output of the "GetDeviceListVDSCommand"), all sizes look the same on all hosts. Version-Release number of selected component (if applicable): 4.0.4.4-0.1 How reproducible: seems easily Steps to Reproduce: 1. setup a system with iSCSI storage and multiple hosts 2. extend an iSCSI lun in the storage 3. Go into "Manage Domain" for the domain containing the LUN, the added capacity should show up in the "Additional Size" column. 4. Click on the button showing the additional size and click ok Actual results: After a few minutes and error message will pop up Expected results: The storage domain should have the new capacity. Additional info: relevant engine.log section will be attached. The following command could be used to compare device sized as reported in the log: grep -o "deviceSize='[^']*'" engine.log-74331481