Bug 813147 - Header message needs to be fixed while uploading an invalid xml in application blueprint
Summary: Header message needs to be fixed while uploading an invalid xml in applicatio...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
Assignee: Jan Provaznik
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-17 05:30 UTC by Shveta
Modified: 2012-12-04 15:03 UTC (History)
9 users (show)

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.
Clone Of:
Environment:
Last Closed: 2012-12-04 15:03:53 UTC
Embargoed:

Attachments (Terms of Use)
header_message (219.80 KB, image/png)
2012-04-17 05:30 UTC, Shveta 		no flags Details
blank XML field (82.29 KB, image/png)
2012-09-20 21:29 UTC, Ronelle Landy 		no flags Details
not Valid XML uploaded (86.07 KB, image/png)
2012-09-20 21:29 UTC, Ronelle Landy 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:1516 0 normal SHIPPED_LIVE CloudForms Cloud Engine 1.1 update 2012-12-04 19:51:45 UTC

Description Shveta 2012-04-17 05:30:39 UTC 
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
Comment 3 Jan Provaznik 2012-08-30 13:02:33 UTC 
a patch is waiting for a review: https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-August/012353.html
Comment 4 Jan Provaznik 2012-09-04 14:09:35 UTC 
pushed, commit in master: 73db059e1a210e6e7b93ba7c612a0a864d0626ee
Comment 5 Steve Linabery 2012-09-07 21:52:53 UTC 
in build aeolus-conductor-0.13.3-1.el6cf
Comment 7 Ronelle Landy 2012-09-20 21:28:12 UTC 
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'.
Comment 8 Ronelle Landy 2012-09-20 21:29:06 UTC 
Created attachment 615129 [details]
blank XML field
Comment 9 Ronelle Landy 2012-09-20 21:29:32 UTC 
Created attachment 615130 [details]
not Valid XML uploaded
Comment 11 errata-xmlrpc 2012-12-04 15:03:53 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.