Bug 1007408
Summary: | [redhat-support-plugin-rhev] "Would you like transactions from the Red Hat Access Plugin sent from the RHEV Manager to be brokered through a proxy server" is asked again during upgrade | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> |
Component: | redhat-support-plugin-rhev | Assignee: | Sandro Bonazzola <sbonazzo> |
Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.3.0 | CC: | acathrow, alonbl, bsanford, cboyle, iheim, jbelka, oschreib, pstehlik, sbonazzo, srevivo, sshumake, yeylon |
Target Milestone: | --- | ||
Target Release: | 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | integration | ||
Fixed In Version: | redhat-support-plugin-rhev-3.3.0-10.el6ev.noarch.rpm | Doc Type: | Bug Fix |
Doc Text: |
A message "Would you like transactions from the Red Hat Access Plugin sent from the RHEV Manager to be brokered through a proxy server" was asked again during an upgrade even if the same question was answered during initial engine-setup. The old implementation always ran interactive proxy configuration. The new implementation tries to read the configuration file to check whether proxy was already defined.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-21 16:58:21 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: | 1013790 | ||
Bug Blocks: |
Description
Jiri Belka
2013-09-12 12:34:19 UTC
not nice, worth verifying It asks me still for the answer. Procedure: - rhevm build is16 - manual upgrade to redhat-support-plugin-rhev-3.3.0-8.el6ev.noarch (rpm --nodeps -Uhv ...) - engine-setup - change yum repo to rhevm is17 - yum update rhevm-setup - engine-setup The current implementation handles upgrades from 3.3. 1. Can you please verify it works as expected in 3.3 -> further? 2. I will need to check what can we do for 3.2 -> 3.3 upgrade. Sorry but this is 3.3 (latest two 3.3 builds). @Jiri To verify it works correctly in 3.3, you need to take *this* version, install it clean, and then run upgrade on it (or even run setup again on the same system). The code that handles the problem is only introduced with this release and doesn't exist on previous 3.3 builds. Please verify under these conditions. I have tested the *new* install of 3.3 (is19) and this has nothing to do with upgrading. The answer file does not contain the correct value to be passed to the plugin. The bug I filed is: https://bugzilla.redhat.com/show_bug.cgi?id=1013790 ok, is22. This bug is currently attached to errata RHBA-2013:15513. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. 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. http://rhn.redhat.com/errata/RHBA-2014-0082.html |