Bug 813147
| Summary: | Header message needs to be fixed while uploading an invalid xml in application blueprint | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Shveta <ssachdev> | ||||||||
| Component: | aeolus-conductor | Assignee: | Jan Provaznik <jprovazn> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | wes hayutin <whayutin> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 1.0.0 | CC: | akarol, asettle, cpelland, dajohnso, deltacloud-maint, dmacpher, rlandy, slinaber, ssachdev | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: |
The validation message for invalid XML displayed 'Application Blueprint XML' twice in the header. This fix revises the warning message code. The term 'Application Blueprint XML' no longer repeats.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-12-04 15:03:53 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: | |||||||||||
| Attachments: |
|
||||||||||
a patch is waiting for a review: https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-August/012353.html pushed, commit in master: 73db059e1a210e6e7b93ba7c612a0a864d0626ee in build aeolus-conductor-0.13.3-1.el6cf Tested rpms:
>> rpm -qa |grep aeolus
aeolus-configure-2.8.6-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.7.1-1.el6cf.noarch
aeolus-conductor-0.13.8-1.el6cf.noarch
aeolus-conductor-daemons-0.13.8-1.el6cf.noarch
aeolus-conductor-doc-0.13.8-1.el6cf.noarch
aeolus-all-0.13.8-1.el6cf.noarch
See two attached screenshots ... the first when the XML field is empty, and the second when an invalid file is entered.
Marking this BZ as 'verified' an neither message (shown in the screenshots) repeats 'Application Blueprint'.
Created attachment 615129 [details]
blank XML field
Created attachment 615130 [details]
not Valid XML uploaded
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-1516.html |
Created attachment 577877 [details] header_message Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. As shown in the screenshot , header message says : "Application Blueprint XML Application Blueprint XML file doesn't resolve valid XML file " 2. Application Blueprint XML is repeated .. 3. Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-doc-0.8.7-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configure-2.5.2-1.el6.noarch aeolus-conductor-0.8.7-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-all-0.8.7-1.el6.noarch aeolus-conductor-daemons-0.8.7-1.el6.noarch