You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Myroslav Papirkovskyy (JIRA)" <ji...@apache.org> on 2014/06/23 18:05:25 UTC
[jira] [Resolved] (AMBARI-6221) Ambari Server reset show wrong
commands for DB manipulation
[ https://issues.apache.org/jira/browse/AMBARI-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myroslav Papirkovskyy resolved AMBARI-6221.
-------------------------------------------
Resolution: Fixed
Pushed to trunk and branch-1.6.1
> Ambari Server reset show wrong commands for DB manipulation
> -----------------------------------------------------------
>
> Key: AMBARI-6221
> URL: https://issues.apache.org/jira/browse/AMBARI-6221
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.6.1
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Priority: Critical
> Fix For: 1.6.1
>
>
> When performing ambari-server reset with external DB, ambari-server does nothing but outputs commands for resetting it manually.
> But:
> 1. Commands are wrong, at least on Suse:
> {code}
> su -postgres --command=psql -f /var/lib/ambari-server/resources/Ambari-DDL-Postgres-DROP.sql -v username='"ambari"' -v password="'bigdata'"
> su: invalid option -- 'o'
> Try `su --help' for more information.
> {code}
> 2. This commands should take in account that external DB can be located on the another host.
> 3. Maybe the best option would be to give user ability to reset *automatically*, for example via command line switch like
> {code}
> ambari-server reset -a
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)