Bug 848671
Summary: | Prevent duplication of priority group name and score | ||
---|---|---|---|
Product: | [Retired] CloudForms Cloud Engine | Reporter: | Rehana <redakkan> |
Component: | aeolus-conductor | Assignee: | Imre Farkas <ifarkas> |
Status: | CLOSED DEFERRED | QA Contact: | Giulio Fidente <gfidente> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.1.0 | CC: | athomas, cpelland, dajohnso, dmacpher, gfidente, ifarkas, jzigmund, morazi, slinaber |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-10-02 14:32:11 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
Rehana
2012-08-16 07:48:20 UTC
I'd like to prefer constraining only the names of groups, not the score. I can imagine the use cases when users want to have the same score. Also score is not the only one attribute that saying what provider/provider account will be choosen for deploying. Thus I don't see any reason to ban the same score for priority groups. If you have some other points that I missed, please feel free to write them up here. I discussed this with Angus and agreed on that it makes more sense to apply the unique constraints on both fields. So the posted patch solves the issue: https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-August/012169.html in 1.1 branch: commit 846fbb1ce0ec922288696ef66799e584a36acf47 Author: Imre Farkas <ifarkas> Date: Fri Aug 17 16:17:07 2012 +0200 BZ848671: Add unique constraints to ProviderPriorityGroup https://bugzilla.redhat.com/show_bug.cgi?id=848671 (cherry picked from commit 38176e283cf4c51170e68f4fd39779875d2eef9b) in build aeolus-conductor-0.13.3-1.el6cf Currently only "Penalty for failure strategy" is displayed (testing down stream aeolus1.1 repo repo:http://download.lab.bos.redhat.com/rel-eng/CloudForms/1.1/latest/el6-ce/x86_64/os/ ) Will retest it once "strict order" strategy becomes available for testing on rpm -qa | grep aeolus aeolus-conductor-doc-0.13.14-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.13.14-1.el6cf.noarch aeolus-conductor-0.13.14-1.el6cf.noarch rubygem-aeolus-cli-0.7.2-1.el6cf.noarch aeolus-configure-2.8.7-1.el6cf.noarch aeolus-conductor-daemons-0.13.14-1.el6cf.noarch The strict order will never be available in 1.1, you can only find it in upstream for now. I think this[1] has removed completely the new/edit actions bound to priority groups, so I'm closing this bug as DEFERRED [1] commit 4bc6d5630a29f51f0bb0ed2d5fdabb042142523a on 1.1 |