Bug 1355778 - Applying the CP before/after upgrade of JON server produces different results
Summary: Applying the CP before/after upgrade of JON server produces different results
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Productization, Upgrade
Version: JON 3.3.6
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: CR01
: JON 3.3.6
Assignee: Simeon Pinder
QA Contact: Filip Brychta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-12 14:07 UTC by Filip Brychta
Modified: 2016-09-01 08:58 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-01 08:58:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1350180 0 medium CLOSED Applying the CP before/after installation of JON server produces different results 2021-02-22 00:41:40 UTC

Internal Links: 1350180

Description Filip Brychta 2016-07-12 14:07:41 UTC 
Description of problem:
Following differences are visible when applying the patch before/after upgrade from 3.2.3 to 3.3.6:
- diff in rhq-server.properties:
  - rhq.server.tomcat.security.secure-socket-protocol=TLS vs. rhq.server.tomcat.security.secure-socket-protocol=TLSv1,TLSv1.1,TLSv1.2

Version-Release number of selected component (if applicable):
JON3.3.6.ER01

How reproducible:
Always

Steps to Reproduce:
First server:
1. install JON 3.2.3
2. unzip JON3.3.0.GA
3. apply the CP6
4. upgrade

Second server:
1. install JON 3.2.3
2. unzip JON3.3.0.GA
3. upgrade
4. apply the CP6


Actual results:
Differences described above
Comment 2 Simeon Pinder 2016-07-21 06:34:38 UTC 
Moving to ON_QA as available to test with the following build:

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=504646

* Note  jon-server-patch-3.3.0.GA.zip maps to jon-server-3.3.0.GA-update-06 and is CR01 build of JON 3.3.6.
Note You need to log in before you can comment on or make changes to this bug.