Bug 837052
Summary: | Misleading prompt MSG when agent version is HIGHER than server | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Zhengping Jin <zjin> |
Component: | Agent | Assignee: | RHQ Project Maintainer <rhq-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | JON 3.1.0 | CC: | mazz, myarboro |
Target Milestone: | --- | ||
Target Release: | JON 3.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-22 16:25:20 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
Zhengping Jin
2012-07-02 15:51:07 UTC
As per 8/20 triage 8/20 pushing to JON312 Is the problem with the use of the word "update"? An "agent update binary" is simply the name we give to the agent that is packaged inside the binary jar used to install the agent. I may seem to imply the agent will be moved to a higher version, but that isn't the case (note: the word used isn't "upgrade" - its "update"). It simply "updates" the current agent on the box so it is the compatible version for the server. IMO, this isn't a misleading message. An "agent update" must be applied - this is true. It needs to download the "agent update binary" (that's its name) and install it. It just so happens when it is installed, it downgrades (rather than upgrades) the version of the agent. But again, the name isn't an "agent upGRADE binary", its an "agent upDATE binary". Anyway, I would close this issue. It really is a minor thing and has to do with the name we give the downloaded file - which is mentioned all over the documentation. So changing it isn't trivial. |