The privs regression tests expect that authorization should be enabled plus all
the required users registered.
When privs1 or privs2 is run, the runregr_privs1.ksh and runregr_privs2.ksh
scripts check to see if authorization is enabled.
If not, it initializes authorization and registers the required SQL users.
It looks like the installation process is now enabling authorization by
default. If this is true, then regressions that require non DB__ROOT users
need to make sure users are registered.
During install, is authorization enabled by default now?
Roberta
-----Original Message-----
From: Steve Varnau [mailto:[email protected]]
Sent: Sunday, March 5, 2017 12:27 PM
To: [email protected]
Subject: RE: Trafodion release2.1 rh6 Daily Test Result - 6 - Still Failing
Looks like the full nightly test runs with python-installer worked pretty well,
except the priv tests.
The config of ldap should be same as it was with the bash installer, so I'm not
sure of the issue. Maybe folks who know more about that area and pyinstaller
can chime in.
--Steve
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Sunday, March 5, 2017 1:38 AM
> To: [email protected]
> Subject: Trafodion release2.1 rh6 Daily Test Result - 6 - Still Failing
>
> Daily Automated Testing release2.1 rh6
>
> Jenkins Job: https://jenkins.esgyn.com/job/Check-Daily-release2.1-rh6/6/
> Archived Logs: http://traf-testlogs.esgyn.com/Daily-release2.1/6
> Bld Downloads: http://traf-builds.esgyn.com
>
> Changes since previous daily build:
> No changes
>
>
> Test Job Results:
>
> FAILURE core-regress-privs1-cdh (38 min)
> FAILURE core-regress-privs1-hdp (1 hr 2 min)
> FAILURE core-regress-privs2-cdh (43 min)
> FAILURE core-regress-privs2-hdp (53 min)
> SUCCESS build-rh6-release2.1-debug (32 min)
> SUCCESS build-rh6-release2.1-release (38 min)
> SUCCESS core-regress-charsets-cdh (43 min)
> SUCCESS core-regress-charsets-hdp (50 min)
> SUCCESS core-regress-compGeneral-cdh (53 min)
> SUCCESS core-regress-compGeneral-hdp (1 hr 14 min)
> SUCCESS core-regress-core-cdh (58 min)
> SUCCESS core-regress-core-hdp (1 hr 11 min)
> SUCCESS core-regress-executor-cdh (1 hr 37 min)
> SUCCESS core-regress-executor-hdp (1 hr 56 min)
> SUCCESS core-regress-fullstack2-cdh (14 min)
> SUCCESS core-regress-fullstack2-hdp (13 min)
> SUCCESS core-regress-hive-cdh (56 min)
> SUCCESS core-regress-hive-hdp (1 hr 8 min)
> SUCCESS core-regress-qat-cdh (28 min)
> SUCCESS core-regress-qat-hdp (22 min)
> SUCCESS core-regress-seabase-cdh (1 hr 37 min)
> SUCCESS core-regress-seabase-hdp (1 hr 57 min)
> SUCCESS core-regress-udr-cdh (27 min)
> SUCCESS core-regress-udr-hdp (35 min)
> SUCCESS jdbc_test-cdh (32 min)
> SUCCESS jdbc_test-hdp (40 min)
> SUCCESS phoenix_part1_T2-cdh (59 min)
> SUCCESS phoenix_part1_T2-hdp (1 hr 22 min)
> SUCCESS phoenix_part1_T4-cdh (1 hr 3 min)
> SUCCESS phoenix_part1_T4-hdp (1 hr 24 min)
> SUCCESS phoenix_part2_T2-cdh (1 hr 7 min)
> SUCCESS phoenix_part2_T2-hdp (1 hr 19 min)
> SUCCESS phoenix_part2_T4-cdh (1 hr 10 min)
> SUCCESS phoenix_part2_T4-hdp (1 hr 26 min)
> SUCCESS pyodbc_test-cdh (17 min)
> SUCCESS pyodbc_test-hdp (14 min)
