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

Bug 1181082

Summary:	Warn users about not issuing recordKnowGlobalKeyset op. in REST rolling upgrades
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Tomas Sykora <tsykora>
Component:	Documentation	Assignee:	Rakesh <rghatvis>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4.0	CC:	jdg-bugs, mhusnain, rghatvis, tsykora
Target Milestone:	GA
Target Release:	6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-27 23:43:47 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 Tomas Sykora 2015-01-12 11:00:17 UTC

Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1086180

Document that while issuing REST rolling upgrades, there MUST NOT be used operatio recordKnowGlobalKeyset.

Remove this step from respective parts and add a WARNING that explicitly forbid that usage. There is a migrator's intersection and pollution possible. 

Also, check with Misha/Gemma, whether we can change info in older documentation releases. 

Make async release for 6.2.1 6.3.0 6.3.1 and 6.3.2 ??

Comment 2 Tomas Sykora 2015-01-12 11:00:56 UTC

Hi Misha, needinfo, see my question in last comment please.

Comment 3 Tomas Sykora 2015-01-12 11:08:24 UTC

However, we need to make sure that our effort in including one waring message + deleting one step from REST roll ups process in just not too much for last 4 releases.

Comment 4 Misha H. Ali 2015-01-12 13:33:31 UTC

Hi Tomas. Sure, we can update the older docs as well. Since you have already take on this bug, just make the relevant changes and let me know what needs to be added and/or removed and in which versions and I'll make the changes and push them out.

Comment 10 Misha H. Ali 2015-01-14 00:45:10 UTC

Sounds like a good idea, Bobb. We can update the older docs after GA. As long as this is documented and reviewed for this release, we should be good for now.