Bug 1142098
| Summary: | hosted engine setup doesn't detect volume creation failures | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Sandro Bonazzola <sbonazzo> | ||||
| Component: | ovirt-hosted-engine-setup | Assignee: | Sandro Bonazzola <sbonazzo> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Elad <ebenahar> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.5 | CC: | acanan, amureini, bugs, danken, dfediuck, didi, ecohen, gklein, istein, lsurette, lveyde, msivak, rbalakri, sbonazzo, stirabos, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.6.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | integration | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Thanks to the migration from vdsClient to vdscli API it is now possible to detect volume creation failures properly.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-11-04 13:55:28 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1234915 | ||||||
| Attachments: |
|
||||||
Created attachment 937885 [details]
logs
Looks like it was a bad vdsm error handling by setup. It failed to create a volume with size of 25GB in a iscsi lun of 26GB due to insufficient space but the error has not been detected by the setup. Reducing severity and priority and drop blocking. Just a note for remembering what need to be changed:
status, message = serv.createVolume([
sdUUID,
spUUID,
imgUUID,
self.environment[ohostedcons.StorageEnv.IMAGE_SIZE_GB],
volFormat,
preallocate,
diskType,
volUUID,
self.environment[ohostedcons.StorageEnv.IMAGE_DESC],
])
it returns status = 0 also if it failed creating the volume.
Need to change this code for using API instead of vdsClient.
Moving to 3.6 since the solution uses refactored code for using API instead of CLI Automated message: can you please update doctext or set it as not required? Hi Sandro, Please provide exact reproduction steps. (In reply to Nikolai Sednev from comment #6) > Hi Sandro, > Please provide exact reproduction steps. See comment #2. try to create a volume with size of 25GB in a iscsi lun of 26GB: it should detect insufficient space and properly handle it. An attempt to deploy the hosted-engine image on a LUN that doesn't have enough capacity (tried on a 26G LUN) is detected and handled well:
[WARNING] Not enough free space, about 21 GiB are available
Please specify the disk size of the VM in GB [Defaults to minimum requirement: 25]:
Verified using:
ovirt-hosted-engine-setup-1.3.0-0.0.master.20150518075146.gitdd9741f.el7.noarch
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one. |
Not sure about what changed in HA or VDSM but now when I try to deploy hosted engine on iSCSI I have: {'status': {'message': "Logical volume does not exist: ('59fbe5c7-3f29-4149-8595-fa6fb60b2965/688bc33b-5da4-4072-bd74-0dee60f1c940',)", 'code': 610}} Since the setup part has not been changed, opening this bug down in the chain.