Created attachment 576967 [details] ss1 Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.login to conductor 2.Go to "clouds" --> new image --> from URL 3.Issue the URL with a semicolon instead of colon ex:http;//hp-z600-01.rhts.eng.bos.redhat.com/rhel62vmtools Actual results: got an error on conductor:"undefined method `request_uri' for #<URI::Generic:0x7fb611605c60>" (PFA: rails.log, ss1.png) Expected results: should show appropriate error message Additional info: rpm -qa| grep aeolus aeolus-conductor-0.8.7-1.el6.noarch aeolus-configure-2.5.2-1.el6.noarch aeolus-conductor-daemons-0.8.7-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-all-0.8.7-1.el6.noarch aeolus-conductor-doc-0.8.7-1.el6.noarch
Created attachment 576969 [details] Rails log
This is also occurring when tried to create application blueprint with same url http;//hostname/filename
Bugfix has been sent to the aeolus-devel mailing list: https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-August/012285.html
Bugfix pushed in master with commit #90d951e4ae2a3eff3e8d5768b5927ef027a4b805 and to 1.1 branch with commit # ce955791f387d7f90f662448a152d6895ff9c4c1
in build aeolus-conductor-0.13.3-1.el6cf
"Provided URL is not valid http;//hp-z600-01.rhts.eng.bos.redhat.com/rhel62vmtools" is displayed if an image is created with an invalid url. see attached screenshot. verified: rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch aeolus-all-0.13.8-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch
Created attachment 614875 [details] validation
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