Bug 820520
Summary: | RFE: Setup Command should skip default server when only one exists | ||
---|---|---|---|
Product: | [Community] PressGang CCMS | Reporter: | Joshua Wulf <jwulf> |
Component: | CSProcessor | Assignee: | Lee Newson <lnewson> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.x | CC: | jwulf, lcarlon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 0.24.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-07 01:30:07 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
Joshua Wulf
2012-05-10 09:41:32 UTC
Not a bug. This is intended as it list all the possible server setups. You then have to select one of those. As such I'm turning this into an RFE so that when only one exists it will skip that question entirely. Fixed in 0.24.0 You can now use the -H option and just specify the csprocessor server name rather then the full path. Oops that comment was meant for a different bug. Anyways it's still added in 0.24.0. Now if there is only one server it will skip that question in the setup. Have to doublecheck, but when I did the EC2 machine to test the RHEL6 xml mangling issue, I'm pretty sure 0.25 still: * Prompted for a default during setup when only one server was being setup; * Refused to take it's own selection when I pressed enter, and made me laboriously type it out in front of it, humiliating me (just went through customs ;-) As stated it's updated in 0.24.0, which hasn't been released yet so of course it won't work on 0.23.5. Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it. |