[
https://issues.apache.org/jira/browse/AMBARI-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328701#comment-15328701
]
Hudson commented on AMBARI-17176:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5070 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5070/])
AMBARI-17176 VDF: include default version definition in list, even if (zhewang:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8fbfdc218c6c7459174957123aa5f537bae4eb11])
* ambari-web/app/templates/wizard/step1.hbs
* ambari-web/app/controllers/wizard/step1_controller.js
*
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js
> VDF: include default version definition in list, even if Internet Access is
> available
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-17176
> URL: https://issues.apache.org/jira/browse/AMBARI-17176
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin, ambari-web
> Affects Versions: 2.4.0
> Reporter: Zhe (Joe) Wang
> Assignee: Zhe (Joe) Wang
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17176.v0.patch
>
>
> We need to include the Default Version Definition in the list of dropdown
> Versions along with the discovered versions.
> Current experience: we only include Default if we believe we do not have
> internet access
> New experience: include Default in the list regardless of internet or not.
> This is for backwards compatibility, and in the case where the user "just
> does not know" their version (and therefore, needs Ambari to just figure it
> out best it can).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
