Description of problem:
If a single embeddable cartridge provides multiple versions of the same software (e.g., postgresql-8.4 and postgresql-9.2) it is conceivable to add a second cartridge to the same application.
In the case of postgresql, the second one will fail, because the first one has already created a database with the name $OPENSHIFT_APP_NAME. However, not all cartridges may fail similarly, and could lead to unexpected results.
It was determined earlier that supporting two versions of any cartridge within one gear or application would not be supported.
This is not about supporting it. I agree that it is not a good idea.
Rather, we would want to detect that such a maneuver is attempted, and inform the user with a meaningful message, rather than rely on each cartridge to fail somehow.
This should be more gracefully disallowed. Currently it is possible to get around this loose restriction with CLI (see https://bugzilla.redhat.com/show_bug.cgi?id=980760 and https://bugzilla.redhat.com/show_bug.cgi?id=980739).
Reopening and sending this to the broker team for further consideration.
Since v2 cartridge dropped the version suffix fromt the directory name, multiple versions will install to the same directory, causing strange problems.
Closing this as duplicate.
*** This bug has been marked as a duplicate of bug 981528 ***
*** This bug has been marked as a duplicate of bug 980760 ***