Bug 749415
Summary: | Fields need to be read only in drift definition editor | ||
---|---|---|---|
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: | medium | ||
Version: | 4.1 | 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-07 19:26:33 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, 734807, 745494 |
Description
John Sanda
2011-10-27 00:43:54 UTC
For scenarios two and four the pinned field should be rendered and read-only. In scenario two it should be set to false and in scenario four it should be set to true. I have committed changes that I think cover all of the above scenarios; however, before this bug is verified, It may be good for QE, Jay, and myself to go over them to make sure that the scenarios I listed are correct. commit hash: 3af3311a04c8959b65660abf2bd6e26cf39991c1 #1 is verified. 1. Create a drift definition from an unpinned template Here the editor is being used to create a new drift definition. All fields should be rendered and editable. #2 is verified. 2. Edit a definition that is created from an unpinned template All fields should be rendered. The following fields should be read-only - name, base directory, includes, and excludes. ah ... on step #2 ... i now notice that "pinned" is also read-only. that is unexpected. fail to verify/agree with expectations. jsanda, can you clarify if this is expected or a bug? That is definitely a bug. With the pinned field being set to read-only there is no way to unpin the definition. And we do intend to support resource-level unpinning. That is, if you pin a definition to a snapshot, you should be able to unpin the definition. Now if a definition is pinned to a template, we do not want to allow for the definition to be unpinned. Added fix so that the pinned field is editable for scenario 2. commit hash: d230e442f126d6d09d2b05188a4624310dcf990d verified "pinned" is now editable. step #3 is verified. i worked thru this with jsanda. you start with a snapshot ... and create a new drift template. i verified the drift template is created. on the template ... the includes, excludes, and base directory are read-only. the pinned field is on the list view ... but not on the detail view. on the drift configuration, the configuration remains un-pinned....which is confusing ... but correct. discussed with jsanda step #4 is verified. step #5 is verified step #6 is verified step #7 and #8 are verified Reopening so we make sure we don't miss this in the cut over to the jon3x release branch. This fix is in master, but not in the release branch currently The commits for this bug are in the release_jon3.x branch. Here are the commit hashes, 3af3311a04c8959b65660abf2bd6e26cf39991c1 670c2a76b570312eedc71e6d1bffaaadae39e2d1 Moving back to ON_QA. So this is in rhq 4.2 and jon 3 ? verified jon3 branch changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE |