Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1087622

Summary: patch cannot be applied to 3.2.0 if rhqctl start was not executed beforehand
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: Installer, UpgradeAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2.1CC: ahovsepy, mfoley, myarboro, spinder
Target Milestone: DR03Keywords: Triaged
Target Release: JON 3.2.2   
Hardware: x86_64   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-29 00:17:16 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:
Attachments:
Description Flags
upgrade-without-rhqctl-start
none
apply_patch_to_not_started_jon none

Description Armine Hovsepyan 2014-04-14 20:41:54 UTC
Created attachment 886264 [details]
upgrade-without-rhqctl-start

Description of problem:
patch cannot be applied to 3.2.0 if rhqctl start was not executed beforehand

Version-Release number of selected component (if applicable):
jon 3.2.0 CP1

How reproducible:


Steps to Reproduce:
1. unzip jon 3.2.0
2. run rhqctl install (windows)
3. run  jon-server-3.2.0.GA-update-01\apply-updates.bat jon-server-3.2.0.GA
4. run rhqctl start

Actual results:
patch is applied - server is not installed

Expected results:
patch is applied and server, storage and agent started without exceptions

Additional info:
screen-shot attached

This only happens if 3.2.0 installed (service) but not configured by running rhqctl start

Comment 3 Simeon Pinder 2014-06-20 23:44:33 UTC
I'm not able to reproduce this with 3.2.2(DR02) build. I retested on linux and windows and in both cases installing, applying the patch and then starting the server worked as expected to launch a fully patched server on startup.

Additionally if you look at the install log, you'll see that the installation process starts up the JON server anyway, but leaves everything in a shutdown state when not passing in --start at install time.

Moving this to ON_QA to have QE retest this. Also putting a needinfo on Armine so that she can retest this on DR02 earlier in case the reproduce steps were insufficient.

Comment 4 Armine Hovsepyan 2014-06-30 12:30:43 UTC
Created attachment 913395 [details]
apply_patch_to_not_started_jon

Comment 5 Armine Hovsepyan 2014-06-30 12:31:19 UTC
verified

Comment 6 Larry O'Leary 2014-07-29 00:17:16 UTC
This has been verified and released in Red Hat JBoss Operations Network 3.2 Update 02 (3.2.2) available from the Red Hat Customer Portal[1].



[1]: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=31783