Bug 1004005
Summary: | ISO Domain set-up during run of 'rhevm-setup' fails to attach to Data Center | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Rejy M Cyriac <rcyriac> | |
Component: | ovirt-engine-setup | Assignee: | Sandro Bonazzola <sbonazzo> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | sefi litmanovich <slitmano> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 3.3.0 | CC: | acathrow, alonbl, bazulay, ecohen, iheim, oschreib, Rhev-m-bugs, scohen, yeylon | |
Target Milestone: | --- | |||
Target Release: | 3.3.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | integration | |||
Fixed In Version: | is14 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1004395 (view as bug list) | Environment: | ||
Last Closed: | 2014-01-21 22:11:24 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: | 1004395, 1019461 |
Description
Rejy M Cyriac
2013-09-03 17:10:37 UTC
Alon, are you familiar with how the domain is created during rhevm-setup? Seems like something there isn't quite right. from the logs it seems there are 2 issues here: - wrong permission on created directory tree - wrong encoding of the uuid of the domain. A little history regarding the wrong ownerships at the root directory of the ISO Domain. During the run of 'rhevm-setup' in RHEVM3.3, if a non-existing directory path is given for the ISO Domain, the set-up does not create the directory for you, as it is in RHEVM3.2. The setup gives out an error, and waits again for the input of an existing directory path. So the directory for the ISO Domain was manually created, and provided to setup, which accepted it, but did not change the ownerships of the root directory of the ISO Domain to vdsm:kvm, as expected. I think that the earlier process was better in which the setup created the directory for you, and ensured right ownerships. Should I create a separate BZ for that ? (In reply to Rejy M Cyriac from comment #3) > A little history regarding the wrong ownerships at the root directory of the > ISO Domain. > > During the run of 'rhevm-setup' in RHEVM3.3, if a non-existing directory > path is given for the ISO Domain, the set-up does not create the directory > for you, as it is in RHEVM3.2. I meant... the set-up does not create the directory for you, unlike the case in RHEVM3.2. ... (In reply to Rejy M Cyriac from comment #3) > I think that the earlier process was better in which the setup created the > directory for you, and ensured right ownerships. Should I create a separate > BZ for that ? I think it can be addressed solving this bug. (In reply to Sandro Bonazzola from comment #5) > (In reply to Rejy M Cyriac from comment #3) > > I think that the earlier process was better in which the setup created the > > directory for you, and ensured right ownerships. Should I create a separate > > BZ for that ? > > I think it can be addressed solving this bug. looking at the code it seems that setup should already create that directory for you with the right permissions. It seems that the only thing missing is ensuring that the specified path, if exists, has the right ownership. So maybe it's better to open a new bug about the failure in creating the directory if you're able to reproduce it. In this case please also attach the setup logs to the new bug. (In reply to Sandro Bonazzola from comment #6) > So maybe it's better to open a new bug about the failure in creating the > directory if you're able to reproduce it. In this case please also attach > the setup logs to the new bug. I reproduced this issue: Configure an NFS share on this server to be used as an ISO Domain? (Yes, No) [Yes]: Local ISO domain path [/var/lib/exports/iso-20130905082803]: /ISOstore [ ERROR ] Cannot access mount point /ISOstore: Error: mount point /ISOstore is not writable Local ISO domain path [/var/lib/exports/iso-20130905082814]: /var/ISOstore Local ISO domain name [ISO_DOMAIN]: So it fails only specifying a non existent directory on / . (In reply to Sandro Bonazzola from comment #7) > I reproduced this issue: > Configure an NFS share on this server to be used as an ISO Domain? (Yes, > No) [Yes]: > Local ISO domain path [/var/lib/exports/iso-20130905082803]: /ISOstore > [ ERROR ] Cannot access mount point /ISOstore: Error: mount point /ISOstore > is not writable > Local ISO domain path [/var/lib/exports/iso-20130905082814]: /var/ISOstore > Local ISO domain name [ISO_DOMAIN]: > > So it fails only specifying a non existent directory on / . upstream patch 18899 should fix this specific issue. (In reply to Sandro Bonazzola from comment #2) > from the logs it seems there are 2 issues here: > - wrong permission on created directory tree upstream patch 18901 should fix this specific issue: previously if an existing directory was specified for using it as iso domain its ownership and access bits where untouched. Now ownership and access bits are enforced. > - wrong encoding of the uuid of the domain. I'm still trying to reproduce this. > - wrong encoding of the uuid of the domain.
upstream patch 18902 should fix this specific issue.
Moving the bug to post, patch under review on upstream master.
merged upstream master, pushed on upstream 3.3 branch. pushed also to upstream 3.3.0 branch All patches merged in master, 3.3 and 3.3.0 upstream branches. Verified- ran engine-setup on vm with RHEL6.4 after installing rhevm is14. 1.Local ISO domain path [/var/lib/exports/iso-20130905082803]: /ISOstore worked fine 2. created POSIX complaint FS Data Center of 3.2 compatibility version, and cluster accordingly. 3. added host, added storge: POSIX complaint FS. 4. after data center went up, attached the ISO_DOMAIN successfully Closing - RHEV 3.3 Released |