[ 
https://issues.apache.org/jira/browse/AMBARI-11367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561604#comment-14561604
 ] 

Hudson commented on AMBARI-11367:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #2727 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/2727/])
AMBARI-11367. RU - Knox upgrade fails because topologies folder is not created, 
and admin.xml not copied (alejandro) (afernandez: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=766b934c086024a65e53b5441f561828e388578c)
* 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/upgrade.py
* ambari-server/src/test/python/stacks/2.2/KNOX/test_knox_gateway.py
* ambari-server/src/test/python/stacks/2.2/configs/knox_upgrade.json
* 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/knox.py
* 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
* 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/knox_gateway.py
* ambari-agent/src/main/python/ambari_agent/Controller.py


> RU - Knox upgrade fails because topologies folder is not created, and 
> admin.xml not copied
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11367
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11367
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11367.patch
>
>
> Knox Upgrade failed because the /usr/hdp/current/knox-server/conf/topologies 
> directory doesn't exist and needs to be created.
> Further, the admin.xml file exposes the Knox API, and the file needs to be 
> copied from the older config folder to the new one after calling conf-select.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to