Bug 1635756
| Summary: | YUM report a collectd failure during 4.0 to 4.2 upgrade. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Frank DeLorey <fdelorey> |
| Component: | ovirt-fast-forward-upgrade | Assignee: | Douglas Schilling Landgraf <dougsland> |
| Status: | CLOSED NOTABUG | QA Contact: | meital avital <mavital> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.6 | CC: | dougsland, fdelorey, michal.skrivanek, ratamir, rmcswain, sbonazzo |
| Target Milestone: | --- | Flags: | lsvaty:
testing_plan_complete-
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-04 07:39:35 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: | |||
Closing as not a bug due to EPEL repository being enabled. Removing EPEL solved. I guess our upgrade tools can't detect this and report a warning? (In reply to Frank DeLorey from comment #4) > I guess our upgrade tools can't detect this and report a warning? We can probably add a check on enabled repos not in the required list and issue a warning, but we already have the list of repositories in documentation. Douglas, can you consider adding such check in next release we'll have for 4.3? (In reply to Sandro Bonazzola from comment #5) > (In reply to Frank DeLorey from comment #4) > > I guess our upgrade tools can't detect this and report a warning? > > We can probably add a check on enabled repos not in the required list and > issue a warning, but we already have the list of repositories in > documentation. Douglas, can you consider adding such check in next release > we'll have for 4.3? Hi Sandro/Frank, Do you think worth check only for EPEL repos? Today when the tool starts and find a non standard repository like EPEL or internal repos we log and show a warning message like: "The following repositories are enabled and not the main repositories for RHV" Maybe we can add an input like: 'are you sure you want to continue? It might generate conflicts on rpm dep. [N/y]' That would be very helpful thanks!! Frank Douglas, I would also agree that this would be very helpful for customers. I've seen a number of cases where customers have additional non-required repos for RHV as well as EPEL that have caused big issues to the point that this is one of the earliest things I try to check when I see dependency issues. Having this built in would deflect a number of install issues. (In reply to Robert McSwain from comment #8) > Douglas, > > I would also agree that this would be very helpful for customers. I've seen > a number of cases where customers have additional non-required repos for RHV > as well as EPEL that have caused big issues to the point that this is one of > the earliest things I try to check when I see dependency issues. Having this > built in would deflect a number of install issues. Fell free to give a feedback guys: https://gerrit.ovirt.org/#/c/95001/ (In reply to Douglas Schilling Landgraf from comment #6) > (In reply to Sandro Bonazzola from comment #5) > "The following repositories are enabled and not the main repositories for > RHV" > > Maybe we can add an input like: > > 'are you sure you want to continue? It might generate conflicts on rpm dep. > [N/y]' looks ok to me |
Description of problem: Customer doing a fast forward upgrade is seeing the following failure during engine setup: # engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-wsp.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'] Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20181002133253-5yl2x5.log Version: otopi-1.6.3 (otopi-1.6.3-1.el7ev) [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Stage: Environment customization Welcome to the RHEV 4.1 setup/upgrade. Please read the RHEV 4.1 install guide https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/installation_guide/index.html Please refer to the RHEV Upgrade Helper application https://access.redhat.com/labs/rhevupgradehelper/ which will guide you in the upgrading process. Would you like to proceed? (Yes, No) [Yes]: --== PRODUCT OPTIONS ==-- --== PACKAGES ==-- [ INFO ] Checking for product updates... [ ERROR ] Yum [u'collectd-write_http-5.8.0-3.el7.x86_64 requires collectd(x86-64) = 5.8.0-3.el7', u'collectd-disk-5.8.0-3.el7.x86_64 requires collectd(x86-64) = 5.8.0-3.el7'] [ INFO ] Yum Performing yum transaction rollback [ ERROR ] Failed to execute stage 'Environment customization': [u'collectd-write_http-5.8.0-3.el7.x86_64 requires collectd(x86-64) = 5.8.0-3.el7', u'collectd-disk-5.8.0-3.el7.x86_64 requires collectd(x86-64) = 5.8.0-3.el7'] [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20181002133253-5yl2x5.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20181002133316-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed How reproducible: Every time. Steps to Reproduce: 1. Added the correct repositories 2. Ran fast upgrade from 4.0 to 4.1 Actual results: Fails complaining about collectd packages Expected results: Should upgrade as expected Additional info: This was reported previously here: https://access.redhat.com/discussions/3035971 For a workaround they removed all the collectd packages.