Bug 1529490

Summary: hosted-engine failed to deploy because of permission error for the cloud-init iso file
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Ido Rosenzwig <irosenzw>
Component: GeneralAssignee: Ido Rosenzwig <irosenzw>
Status: CLOSED CURRENTRELEASE QA Contact: Nikolai Sednev <nsednev>
Severity: high Docs Contact:
Priority: high    
Version: 2.2.0CC: bugs, irosenzw, lveyde, tnisan
Target Milestone: ovirt-4.2.1Keywords: Triaged
Target Release: 2.2.5Flags: rule-engine: ovirt-4.2+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-hosted-engine-setup-2.2.5 Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:58:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1458709    
Attachments:
Description Flags
vdsm.log none

Description Ido Rosenzwig 2017-12-28 11:12:49 UTC 
Created attachment 1373162 [details]
vdsm.log

Description of problem:
hosted-engine --deploy failed.
the reason for this failure revealed on this patch:
https://gerrit.ovirt.org/#/c/85018/

in the patch, vdsm user checks the file descriptor of seed.iso which doesn't have permission for the folder containing seed.iso

Need to add permission for this directory


How reproducible:
100%

Steps to Reproduce:
1. hosted-engine --deploy


Actual results:
failed to deploy

Expected results:
deployment finish successfuly

Additional info:
Logs attached.
Comment 1 Nikolai Sednev 2018-02-08 16:21:10 UTC 
Please provide more detailed reproduction steps.
Comment 2 Ido Rosenzwig 2018-02-11 07:21:30 UTC 
Nikolai, 
This was reproducible easily before merging the patch by doing hosted-engine --deploy --noansible

If you want to reproduce the bug again and see the error, simply revert my patch locally and run 'hosted-engine --deploy --noansible'. 
IMO, it's unnecessary, just do a deployment to see everything is working fine.
Comment 3 Nikolai Sednev 2018-02-11 07:58:30 UTC 
(In reply to Ido Rosenzwig from comment #2)
> Nikolai, 
> This was reproducible easily before merging the patch by doing hosted-engine
> --deploy --noansible
> 
> If you want to reproduce the bug again and see the error, simply revert my
> patch locally and run 'hosted-engine --deploy --noansible'. 
> IMO, it's unnecessary, just do a deployment to see everything is working
> fine.

Yes, but what ere the reproduction exact steps?
Deployment of SHE done on host without any ISO, then deployment itself is downloading rpm with the appliance, then what?
Comment 4 Ido Rosenzwig 2018-02-11 09:07:26 UTC 
There are no special exact steps for the reproduction of the bug other then deploying hosted-engine by doing 'hosted-engine --deploy --noansible' with default answers, specially generated cloud-init file.
Comment 5 Nikolai Sednev 2018-02-11 09:36:11 UTC 
Successfully deployed using default answers including cloud-init generation, deployed over Gluster storage domain. Works for me on these components:
ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.9-1.el7ev.noarch
rhvm-appliance-4.2-20180202.0.el7.noarch
Linux 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Moving to verified.
Comment 6 Sandro Bonazzola 2018-02-12 11:58:46 UTC 
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.