Bug 1080422
| Summary: | JON 3.2 Update 01 can be applied to jon 3.1.0 agent | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Armine Hovsepyan <ahovsepy> | ||||||
| Component: | Agent, Upgrade | Assignee: | Simeon Pinder <spinder> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | JON 3.2.1 | CC: | loleary, mfoley, spinder | ||||||
| Target Milestone: | DR03 | ||||||||
| Target Release: | JON 3.2.1 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-05-08 17:44:02 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: | 1048595 | ||||||||
| Attachments: |
|
||||||||
This is fixed with commit: 2031642e614ed9 to jon.git. Apply updates should only work on 3.2.0.GA and greater agents. Moving this to MODIFIED. Moving to ON_QA as available for test in newest cumulative patch build from here: http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.1.GA/4-01-2014/ I moved the earlier build to 3-18-2014. Created attachment 881706 [details]
cp_3.1.0_agent
verified To be clear, this BZ: i)applies to customers using apply-updates.* tooling to update Agents where agent-auto-update has been disabled. ii)Is not applicable for agents installed via rpm. JON 3.2.1 released week of 5/5/2014 |
Created attachment 878424 [details] patch_apply_3.1.0_agent.log Description of problem: JON 3.2. CP1 can be applied to jon 3.1.0 agent Version-Release number of selected component (if applicable): jon 3.2. CR1 on jon 3.1.0 How reproducible: always Steps to Reproduce: 1. install jon 3.1.0 with agent 2. apply 3.2 CP1 on agent 3. Actual results: patch is applied Expected results: meaningful message should be shown to user telling patch cannot be applied to old version Additional info: log attached marking bug as urgent, cause server cannot be updated and agent can be updated, which may lead to unknown state