Bug 810558

Summary:	content and deployments are persistent state, not cacheable data
Product:	[Fedora] Fedora	Reporter:	Carlo de Wolf <cdewolf>
Component:	jboss-as	Assignee:	Marek Goldmann <mgoldman>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17	CC:	mgoldman, smarlow
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	jboss-as-7.1.0-3.fc17	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-22 04:16:48 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 Carlo de Wolf 2012-04-06 17:18:09 UTC

Description of problem:

The directories content and deployments with /var/cache/jboss-as/domain and /var/cache/jboss-as/standalone must appear in /var/lib/jboss-as/domain or /var/lib/jboss-as/standalone respectively.

/var/cache is reserved for reproducible data.

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

jboss-as-7.1.0-1.fc17.noarch

Comment 1 Fedora Update System 2012-04-16 19:54:36 UTC

jboss-as-7.1.0-3.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/jboss-as-7.1.0-3.fc17

Comment 2 Fedora Update System 2012-04-16 21:55:19 UTC

Package jboss-as-7.1.0-3.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing jboss-as-7.1.0-3.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-5974/jboss-as-7.1.0-3.fc17
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2012-04-22 04:16:48 UTC

jboss-as-7.1.0-3.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.