Bug 1799005
| Summary: | [RHEL 8] gdeploy-3.0.0-1.noarch conflicts with file from package vdo-6.2.1.134-11.el8.x86_64 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Kshithij Iyer <kiyer> |
| Component: | build | Assignee: | Prajith <pkesavap> |
| Status: | CLOSED ERRATA | QA Contact: | Vivek Das <vdas> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.5 | CC: | godas, pkesavap, pprakash, puebele, rhs-bugs, sabose, sasundar, sheggodu, storage-qa-internal, vdas |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.5.z Batch Update 2 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gdeploy-3.0.0-2 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-06-16 06:19:37 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: | |||
|
Description
Kshithij Iyer
2020-02-06 13:09:31 UTC
Prajith - we need to remove the vdo.service file packaged with gdeploy. Just ensure that we are not missing any functionality by doing this. (In reply to Sahina Bose from comment #1) > Prajith - we need to remove the vdo.service file packaged with gdeploy. Just > ensure that we are not missing any functionality by doing this. Sahina, Instead of removing the vdo.service file, we should try to narrow down the conflict between the custom-made vdo.service file and the one provided by vdo itself. Identifying that difference, would help to resolve the issue. The same solution also needs to ported to gluster-ansible, which also updates the custom vdo.service for RHHI-V use case. Also VDO support may again required for future versions of RHGS 3.5.z as this one - https://bugzilla.redhat.com/show_bug.cgi?id=1795169, which may require gdeploy to enable the same ( maybe ) For all these reason, can we identify the reason behind the conflict ? (In reply to SATHEESARAN from comment #2) > (In reply to Sahina Bose from comment #1) > > Prajith - we need to remove the vdo.service file packaged with gdeploy. Just > > ensure that we are not missing any functionality by doing this. > > Sahina, > > Instead of removing the vdo.service file, we should try to narrow down the > conflict > between the custom-made vdo.service file and the one provided by vdo itself. > > Identifying that difference, would help to resolve the issue. > The same solution also needs to ported to gluster-ansible, which also updates > the custom vdo.service for RHHI-V use case. > > Also VDO support may again required for future versions of RHGS 3.5.z > as this one - https://bugzilla.redhat.com/show_bug.cgi?id=1795169, which may > require gdeploy to enable the same ( maybe ) > > For all these reason, can we identify the reason behind the conflict ? The vdo.service file was added as a fix for bug 1548399 - I think this is the same as the one provided by vdo module? Prajith, can you check? (In reply to Sahina Bose from comment #3) > (In reply to SATHEESARAN from comment #2) > > (In reply to Sahina Bose from comment #1) > > > Prajith - we need to remove the vdo.service file packaged with gdeploy. Just > > > ensure that we are not missing any functionality by doing this. > > > > Sahina, > > > > Instead of removing the vdo.service file, we should try to narrow down the > > conflict > > between the custom-made vdo.service file and the one provided by vdo itself. > > > > Identifying that difference, would help to resolve the issue. > > The same solution also needs to ported to gluster-ansible, which also updates > > the custom vdo.service for RHHI-V use case. > > > > Also VDO support may again required for future versions of RHGS 3.5.z > > as this one - https://bugzilla.redhat.com/show_bug.cgi?id=1795169, which may > > require gdeploy to enable the same ( maybe ) > > > > For all these reason, can we identify the reason behind the conflict ? > > The vdo.service file was added as a fix for bug 1548399 - I think this is > the same as the one provided by vdo module? Prajith, can you check? As per the discussions , i have provided with a build of gdeploy that does not contain vdo in the spec file, which resolves this issue. rpm -qa | grep vdo vdo-6.2.2.117-13.el8.x86_64 # rpm -qa | grep gdeploy gdeploy-3.0.0-4.el8rhgs.noarch gdeploy is now successfully installed. The concerned issue is resolved. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2572 |