Bug 708328

Summary:	as7: Implement re-deployment of content
Product:	[Other] RHQ Project	Reporter:	Heiko W. Rupp <hrupp>
Component:	Plugins	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	4.2	CC:	hrupp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-13 14:26:30 UTC	Type:	---
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:	707223

Description Heiko W. Rupp 2011-05-27 10:08:00 UTC

It must be possible to re-deploy a newer version of content.

This may include using a deployment plan, that explains if all servers of a server group should be updated at once or step-by-step and what policy should occur on failure.

Comment 1 Heiko W. Rupp 2011-08-16 20:17:33 UTC

Pushed to 4.2 as not implemented yet and the used can delete the deployment and deploy the new version as workaround

Comment 2 Charles Crouch 2011-10-04 18:07:10 UTC

Setting priority on enhancements to as7 plugin to high. They don't block the JON3 release, but will be needed for subsequent release

Comment 3 Heiko W. Rupp 2012-02-13 14:26:30 UTC


*** This bug has been marked as a duplicate of bug 767974 ***