-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57276/#review168237
-----------------------------------------------------------


Ship it!




Ship It!

- Velmurugan Periasamy


On March 7, 2017, 1:23 p.m., Pradeep Agrawal wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57276/
> -----------------------------------------------------------
> 
> (Updated March 7, 2017, 1:23 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Mehul Parikh, Ramesh Mani, Selvamohan Neethiraj, 
> Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1417
>     https://issues.apache.org/jira/browse/RANGER-1417
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> **Problem Statement:** Ranger Upgrade(0.6 to 0.7) is failing for Oracle DB 
> flavor as the java patches are not marked applied in x_db_version_h table by 
> db_setup.py script in 0.6 version.
> 
> **Proposed Solution :** db_setup.py can identify java patches that are marked 
> as 'N' but NOT installed by current version of Ranger Admin; and marked such 
> entries status to 'Y'.
> 
> 
> Diffs
> -----
> 
>   security-admin/scripts/db_setup.py 4112e05 
> 
> 
> Diff: https://reviews.apache.org/r/57276/diff/1/
> 
> 
> Testing
> -------
> 
> **Use Case: Ranger upgrade case(0.6 to 0.7)**
> Steps performed(with patch) :
> 1. Installed and started 0.6 version of Ranger admin for Oracle DB flavor.
> 2. From installation log messages it was observed that java patches have been 
> executed.
> 3. Logged into ranger Oracle DB and executed below command to check whether 
> executed java patches entries status has been marked 'Y' or not.
> SELECT * FROM X_DB_VERSION_H WHERE VERSION LIKE 'J%';
> From output of above sql statement it was observed that though patches have 
> been applied their active status is not set to ='Y'.
> 4. Stop Ranger admin.
> 5. Took Ranger latest code from master; applied patch and created build. 
> Unzipped the generated tar file and in install.properties provided Ranger db 
> configuration which were used in 0.6 version of Ranger installation.
> 6. Logged into ranger Oracle DB and executed below command to check whether 
> executed java patches entries status has been marked 'Y' or not.
> SELECT * FROM X_DB_VERSION_H WHERE VERSION LIKE 'J%';
> 
> **Expected Behaviour:**
> output of above sql statement should state that all java patches have been 
> applied, this can be determine by referring active column of output where 
> active column value must be 'Y'.
> 
> **Actual Behaviour:**
> From output of above sql statement it was observed that active column value 
> was set to 'Y' and additional java patches have also been applied 
> successfully.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Reply via email to