Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Create a pool family with name called "family-aziza". 2.create a pool called "default" in the above family. pool with name "default" gets created in family "family-aziza".although pool with name Default already exists in Default family. see attached screenshot. i see that if the first letter of the pool name is either capital or small ,pool with same name gets created across families. Expected results: validation required. Additional info: [root@dell-pe2950-1 ~]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch [root@dell-pe2950-1 ~]#
Created attachment 549777 [details] pool names
adding to ce-sprint-next
adding to ce-sprint
removing ce-sprint-next tracker
I'm not seeing the case for taking the ability to create identical or near-identical names for pools across pool families away from Administrators. Unless the actual problem can be articulated more precisely, this should be closed.
Well.. the only case I can make.. is that from the monitor page.. it would look pretty stupid to have three pools listed w/ the same name.. Perhaps you want to have some kind of indication of the pool family from the monitor page.. even if its just a hover over txt or something moving back to Angus
Ken, Can you propose a means to address this, without too much disruption to the current page? Angus
This isn't an issue with the layout/design -- it's more of an issue with user-generated taxonomy rules. Do we wish to ensure that pool names are unique even across environments, or should a user be allowed to create two "default" pools in separate environments?
We don't care about making pool names unique, no -- we just want the user to be able to tell them apart. Wes' suggestion of a rollover hint seems fine to me.
So, the problem with a rollover hint on the monitor page is that it would interfere with the click area, and potentially be misleading to the user. For example, when you hover over the "default" pool and see the environment name, some users' expectations might be that a click action would take you to an environment page. My recommendation would be to place each block of pools under a header which shows the environment. Is that okay with everyone? It won't be perfect, but it'll work.
Talked to a few of the guys -- turns out, looking at the models, that we were supposed to be validating that duplicate pool names could not be created; however, Rails changed some syntax in validates_uniqueness_of such that :case_sensitive must now be manually set to => true. Submitting a patch for both product and upstream.
Okay, after much further deliberation between matty_dubs, sseago, and myself we've decided that this should be closed as notabug. I put it up for comment on the list, and received no feedback -- so here we go: This is not a bug because the user should be required to have an understanding and mental model of the names of their pools, and any "fix" (read: handholding) that we wished to apply for this would have a much larger impact across the application, rather than just two or three areas.