BUGFIX: MSF-25904 Error no suitable driver found when testing LCM Bri…

…cks with environment C9S
gooddata · Nov 8, 2023 · 9677e29 · 9677e29
1 parent 2931de7
commit 9677e29
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 0 deletions.
diff --git a/Dockerfile b/Dockerfile
@@ -13,6 +13,9 @@ RUN yum install -y which patch make git maven procps \
     && yum clean all \
     && rm -rf /var/cache/yum
 
+RUN update-alternatives --set java /usr/lib/jvm/jre-11/bin/java
+RUN export JAVA_HOME=/usr/lib/jvm/jre-11
+
 # Install + verify RVM with gpg (https://rvm.io/rvm/security)
 RUN curl -sSL https://rvm.io/mpapis.asc | gpg --import - \
     && curl -sSL https://rvm.io/pkuczynski.asc | gpg2 --import - \

diff --git a/bin/run_brick.rb b/bin/run_brick.rb
@@ -62,6 +62,12 @@ def handle_error(params, log, brick_type, error, error_message)
   params['GDC_EXECUTION_RESULT_LOG_PATH'] = execution_result_log_path
 
   log.info "action=#{brick_type}_execution status=start commit_hash=#{commit_hash} execution_id=#{execution_id}"
+
+  # Start sleep to investigate issue no suitable driver found
+  log.info "action=#{brick_type}_execution status=start commit_hash=#{commit_hash} execution_id=#{execution_id} sleep=start"
+  sleep(60)
+  log.info "action=#{brick_type}_execution status=start commit_hash=#{commit_hash} execution_id=#{execution_id} sleep=end"
+
   brick_pipeline.call(params)
 rescue GoodData::LcmExecutionError => lcm_error
   handle_error(execution_result_log_params, log, brick_type, lcm_error, lcm_error.summary_error)

diff --git a/gooddata.gemspec b/gooddata.gemspec
@@ -74,6 +74,7 @@ if RUBY_VERSION >= '2.5'
   s.add_dependency 'parseconfig', '~> 1.0'
   s.add_dependency 'pmap', '~> 1.1'
   s.add_dependency 'sequel', '< 5.72.0'
+  s.add_dependency 'gooddata-dss-jdbc', '< 0.2.9'
   s.add_dependency 'remote_syslog_logger', '~> 1.0.3'
   s.add_dependency 'restforce', '>= 2.4'
   s.add_dependency 'rest-client', '~> 2.0'