Description

If using provided configuration in the pillar.example file, the zoomdata-screenshot-service is not able to create any screenshots for Zoomdata visualizations, dashboards and bookmarks.
The Pillar should contain the following:

zoomdata:
  post_install:
    zoomdata-screenshot-service:
      - /opt/zoomdata/docs/screenshot-service/install-dependencies.sh

Symptoms

The service log file at /opt/zoomdata/logs/screenshot-service.log contains the exception like this:

2019-01-08 12:56:58,013 INFO  [c.z.s.c.ScreenshotController] [334c9d3f0b654168, 09fd1740ae63edfc, true] Received screenshot request for: http://localhost:8080/zoomdata/visualization/5c349e195c30a43e92334125?__target=widget&screenshot_capture=true&hidecontrol=timetable,vistitle&key=10t6N47ijX 
2019-01-08 12:56:58,124 ERROR [o.s.c.s.i.w.ExceptionLoggingFilter] [334c9d3f0b654168, 09fd1740ae63edfc, true] Uncaught exception thrown 
org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.util.concurrent.ExecutionException: java.lang.IllegalStateException: The path to the driver executable must be set by the webdriver.chrome.driver system property; for more information, see https://github.com/SeleniumHQ/selenium/wiki/ChromeDriver. The latest version can be downloaded from http://chromedriver.storage.googleapis.com/index.html

The affected zoomdata-screenshot-service package version is 3.7.3-4.

Reason

This is not an issue with the formula, but the packaged post-installation script!

The install-dependencies.sh script contains a shameful bug causing chromedriver binary would not be unpacked from downloaded archive.

Workaround

Run the following commands on the machine where Zoomdata has been installed:

CHROMEDRIVER_LATEST_VERSION=$(curl -s https://chromedriver.storage.googleapis.com/LATEST_RELEASE)
curl -s -o /tmp/chromedriver.zip "https://chromedriver.storage.googleapis.com/${CHROMEDRIVER_LATEST_VERSION}/chromedriver_linux64.zip"
sudo unzip /tmp/chromedriver.zip -d /usr/bin/ && rm -f /tmp/chromedriver.zip

On Ubuntu GNU/Linux operating systems you may need to additionally install curl in advance.

sudo apt-get install curl

Resolution

The issue with the packaged script is expected to be fixed in Zoomdata LTS patch release 3.7.4 and upcoming 4.0.0 cutting-edge release.

Got this error during state.apply with latest stable Salt 2019.2.1:

Data failed to compile:
----------
    Rendering SLS 'base:zoomdata.backup.metadata' failed:
    Jinja variable 'dict object' has no attribute 'zoomdata_properties'

The states in tls.sls file are not being used and tested for a while.
The production Zoomdata setup requires external load-balancer or proxy to efficiently offload TLS, such as AWS ELB, Nginx or HAproxy.
Also, we do not ship keytool with bundled JVM anymore.

The function zoomdata.list_repos, when called with compact=True argument, returns wrong results if configured Zoomdata release is not latest.
For example:

  base_url: https://repo.zoomdata.com
  components:
  - stable
  gpgkey: https://repo.zoomdata.com/ZOOMDATA-GPG-KEY.pub
  release: tools
  repositories:
  - '3.7'

Expected result is:

...
  release: '3.7'
  repositories:
  - tools

Other side effect reveals when legacy repositories are present in the system:

  base_url: http://repo.zoomdata.com
  components:
  - stable
  - unstable
  gpgkey: https://repo.zoomdata.com/ZOOMDATA-GPG-KEY.pub
  release: latest
  repositories:
  - tools
  - tools
  - '3.1'

Heaving this in pillar:

spring.datasource.password:
    zQkHK3rHD22z%]Q:

note colon at the end of password!
zoomdata.backup state rendering fails with this:

Data failed to compile:
----------
    Rendering SLS 'base:zoomdata.backup' failed: mapping values are not allowed here; line 99

---
[...]
        gzip
        --stdout  >
        /opt/zoomdata/data/backups/18-04-23_14:45:29/zoomdata-scheduler_postgre.sql.gz
    - env:
      - PGUSER: zoomdata
      - PGPASSWORD: zQkHK3rHD22z%]Q:    <======================
    - onchanges:
      - file: zoomdata_backup_dir
    - onchanges_in:
      - file: zoomdata_backup_retension
    - require:
[...]

@vutny FYI