Created attachment 571331 [details] unreachable_host Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Application Blueprint -- From URL 2. Gave an unreachable url . 3. Actual results: Expected results: Additional info: This is a regression https://bugzilla.redhat.com/show_bug.cgi?id=784186 rpm -qa|grep aeolus aeolus-all-0.8.0-43.el6.noarch aeolus-conductor-doc-0.8.0-43.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-configure-2.5.0-18.el6.noarch aeolus-conductor-0.8.0-43.el6.noarch rubygem-aeolus-cli-0.3.0-14.el6.noarch aeolus-conductor-daemons-0.8.0-43.el6.noarch
May already be fixed upstream.
This is indeed fixed upstream. Attempting to add a new deployable from an unreachable URL gives me "Deployable XML file is either invalid or no longer reachable at http://1.1.1.1" now.
To keep everything connected, this is referenced in upstream Redmine here: https://www.aeolusproject.org/redmine/issues/3645
1. Application Blueprint -- From URL 2. Gave an unreachable url . Verified on :- [root@dhcp201-113 ~]# rpm -qa|grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.13.8-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch
Created attachment 615342 [details] unreachable url