Created attachment 1633811 [details] lynx14 logs Description of problem: [4.4.0-4] failed to deploy HE over NFS on RHEL-8.1 with volume size error. Version-Release number of selected component (if applicable): ovirt-ansible-hosted-engine-setup-1.0.30-1.el8ev.noarch ovirt-ansible-engine-setup-1.1.9-1.el8ev.noarch python3-ovirt-setup-lib-1.3.0-0.0.master.20190419120545.gitfbe1cbd.el8ev.noarch ovirt-hosted-engine-setup-2.4.0-0.1.master.20191104160243.git0c51343.el8ev.noarch How reproducible: 100% Steps to Reproduce: 1. deploy the HE over NFS Actual results: it failed to deploy in: 13:38:02 TASK [ovirt.hosted_engine_setup : Add HE disks] ******************************** 13:38:21 changed: [lynx14.lab.eng.tlv2.redhat.com] => (item={u'content': u'hosted_engine', u'description': u'Hosted-Engine disk', u'sparse': True, u'format': u'raw', u'size': u'61GiB', u'name': u'he_virtio_disk'}) 13:38:49 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: 'NoneType' object has no attribute 'status' 13:38:49 failed: [lynx14.lab.eng.tlv2.redhat.com] (item={u'content': u'hosted_engine_sanlock', u'description': u'Hosted-Engine sanlock disk', u'sparse': False, u'format': u'raw', u'size': u'1GiB', u'name': u'he_sanlock'}) => {"ansible_loop_var": "item", "changed": false, "item": {"content": "hosted_engine_sanlock", "description": "Hosted-Engine sanlock disk", "format": "raw", "name": "he_sanlock", "size": "1GiB", "sparse": false}, "msg": "'NoneType' object has no attribute 'status'"} 13:39:18 changed: [lynx14.lab.eng.tlv2.redhat.com] => (item={u'content': u'hosted_engine_configuration', u'description': u'Hosted-Engine configuration disk', u'sparse': False, u'format': u'raw', u'size': u'1GiB', u'name': u'HostedEngineConfigurationImage'}) 13:39:37 changed: [lynx14.lab.eng.tlv2.redhat.com] => (item={u'content': u'hosted_engine_metadata', u'description': u'Hosted-Engine metadata disk', u'sparse': False, u'format': u'raw', u'size': u'1GiB', u'name': u'he_metadata'}) in the vdsm.log got the following error: 2019-11-07 06:38:29,665-0500 ERROR (tasks/7) [storage.Volume] The volume ce793779-292f-4983-ab9b-983f4ceb90bf apparent size 1027448832 is smaller than the requested capacity 1073741824 (volume:1179) 2019-11-07 06:38:29,665-0500 ERROR (tasks/7) [storage.Volume] Unexpected error (volume:1202) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 1180, in create raise se.VolumeCreationError() vdsm.storage.exception.VolumeCreationError: Error creating a new volume: () 2019-11-07 06:38:29,665-0500 ERROR (tasks/7) [storage.TaskManager.Task] (Task='eec0ec74-d8ec-4acc-9f41-adc84e0401df') Unexpected error (task:889) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 896, in _run return fn(*args, **kargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 344, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python3.6/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 1913, in createVolume initial_size=initialSize) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 938, in createVolume initial_size=initial_size) File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 1180, in create raise se.VolumeCreationError() vdsm.storage.exception.VolumeCreationError: Error creating a new volume: () It looks like the defined size 1GB(1024*1024*1024=1073741824) didn't define as expected for some reason. and we got the error "apparent size 1027448832 is smaller than the requested capacity"the question is why we got apparent size 1027448832 Expected results: Deploy completed successfully Additional info: checked 2-3 times on 2 different environments
one time it failed in the ansible deploy with the following error: 19:00:10 TASK [ovirt.hosted_engine_setup : Add HE disks] ******************************** 19:00:21 changed: [lynx01.lab.eng.tlv2.redhat.com] => (item={u'content': u'hosted_engine', u'description': u'Hosted-Engine disk', u'sparse': True, u'format': u'raw', u'size': u'61GiB', u'name': u'he_virtio_disk'}) 19:00:50 changed: [lynx01.lab.eng.tlv2.redhat.com] => (item={u'content': u'hosted_engine_sanlock', u'description': u'Hosted-Engine sanlock disk', u'sparse': False, u'format': u'raw', u'size': u'1GiB', u'name': u'he_sanlock'}) 19:10:53 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: Exception: Timeout exceed while waiting on result state of the entity. 19:10:53 failed: [lynx01.lab.eng.tlv2.redhat.com] (item={u'content': u'hosted_engine_configuration', u'description': u'Hosted-Engine configuration disk', u'sparse': False, u'format': u'raw', u'size': u'1GiB', u'name': u'HostedEngineConfigurationImage'}) => {"ansible_loop_var": "item", "changed": false, "item": {"content": "hosted_engine_configuration", "description": "Hosted-Engine configuration disk", "format": "raw", "name": "HostedEngineConfigurationImage", "size": "1GiB", "sparse": false}, "msg": "Timeout exceed while waiting on result state of the entity."} 19:11:13 changed: [lynx01.lab.eng.tlv2.redhat.com] => (item={u'content': u'hosted_engine_metadata', u'description': u'Hosted-Engine metadata disk', u'sparse': False, u'format': u'raw', u'size': u'1GiB', u'name': u'he_metadata'})
Is this reproducible with current builds? For the record, I now succeeded to deploy hosted-engine on nfs and a centos8 host, from current nightly master snapshot and ovirt-engine-appliance-4.4-20191221175026.1.el8.x86_64.
AFAICS in the latest build(4.4.0-13), we succeeded to deploy HE over NFS. so from my side, you can close this bug. Thanks!!