Bug 749419
Summary: | Do not let a definition pinned to a template be re-pinned to a different snapshot | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | John Sanda <jsanda> |
Component: | drift | Assignee: | John Sanda <jsanda> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 4.1 | CC: | jsanda |
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-07 19:26:40 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: | 707225 |
Description
John Sanda
2011-10-27 00:56:34 UTC
I have made changes so that the "Pin to Definition" button is disabled in the snapshot view. The "Pin to Template" button however is not disabled. The reason for this is as follows. Pinning a snapshop to a template only effects the definition when the template is the one from which the definition was created. If you pin to a new template or some other existing template, the definition (to which the snapshot belongs) remains unmodified. We do want to allow "repinning" particularly to support planned changes. Suppose you have a pinned template and pinned definition for an EAP server. As part of a planned change, you deploy a new or updated application to the EAP server. Drift monitoring is set up for the EAP server. A new snapshot is generated after the application is deployed, and you will want to repin the template to that new snapshot. master commit hash: 8777734dc997d9c499479eaaee692d57e1e31766 release_jon3.x commit hash: ffe008e5e343d594de53bffde293119ecb1fb224 verification blocked ... https://bugzilla.redhat.com/show_bug.cgi?id=753827 You can still verify this bug. Just use unique names for the templates. changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE |