Bug 802698
| Summary: | max-qmf-table-sort doesn't work as expected | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Stanislav Graf <sgraf> |
| Component: | cumin | Assignee: | Chad Roberts <croberts> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Stanislav Graf <sgraf> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | Development | CC: | esammons, iboverma, matt, mkudlej, tmckay |
| Target Milestone: | 3.2 | Keywords: | Regression, Reopened, TestCaseProvided |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cumin-0.1.5357-1 | Doc Type: | Bug Fix |
| Doc Text: |
Consequence: Tables with a large number of rows (greater than max-qmf-table-sort) would not be sortable, but would still show the "sort ascending/descending" link, which when clicked would not actually do any sorting and could be confusing to the user.
Cause: max-qmf-table-sort was not being respected when the decision was made to make the table column header static or live.
Fix: We are now checking the count of the rows in the table against max-qmf-table-sort before choosing the type of column header.
Result: The table headers for tables with > max-qmf-table-sort rows will no longer be clickable links.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-05-06 13:52:16 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: | |||
|
Description
Stanislav Graf
2012-03-13 10:06:29 UTC
Fixed in revision 5347. For tables with > max-qmf-table-sort rows, the column headers will be static.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Consequence: Tables with a large number of rows (greater than max-qmf-table-sort) would not be sortable, but would still show the "sort ascending/descending" link, which when clicked would not actually do any sorting and could be confusing to the user.
Cause: max-qmf-table-sort was not being respected when the decision was made to make the table column header static or live.
Fix: We are now checking the count of the rows in the table against max-qmf-table-sort before choosing the type of column header.
Result: The table headers for tables with > max-qmf-table-sort rows will no longer be clickable links.
Test Case: Prepare environment: # echo 'TEST1_LIMIT = 1' > /etc/condor/config.d/99cumin.config # echo 'TEST2_LIMIT = 1' > /etc/condor/config.d/99cumin.config # service condor restart # getent passwd test || adduser test # echo -e "executable=/bin/sleep\narguments=10\niwd=/tmp\nconcurrency_limits=TEST1\nqueue" | runuser -s /bin/bash -c "condor_submit " test # echo -e "executable=/bin/sleep\narguments=10\niwd=/tmp\nconcurrency_limits=TEST2\nqueue" | runuser -s /bin/bash -c "condor_submit " test Test: # grep max-qmf-table-sort /etc/cumin/cumin.conf # max-qmf-table-sort: 1000 Cumin -> Grid -> Limits -> sortable # sed -i 's,^# max-qmf-table-sort:.*,max-qmf-table-sort: 1,' /etc/cumin/cumin.conf # grep max-qmf-table-sort /etc/cumin/cumin.conf max-qmf-table-sort: 1 # service cumin restart Cumin -> Grid -> Limits -> The table headers for tables with > max-qmf-table-sort rows are no longer clickable links Reproduced RHEL 6 x86_64 cumin-0.1.5444-3 Verified RHEL 5/6 i386/x86_64 cumin-0.1.5675-1 --> VERIFIED |