Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EMIS Starburst image has updated to 391-e #856

Open
StevenMaude opened this issue Aug 16, 2022 · 1 comment
Open

EMIS Starburst image has updated to 391-e #856

StevenMaude opened this issue Aug 16, 2022 · 1 comment

Comments

@StevenMaude
Copy link
Contributor

Automated check failure:

A screenshot showing a test failure in GitHub Actions, with a different version of the Starburst image run by EMIS to that in this repository.

I tried updating, but there are other test failures with errors like:

PrestoExternalError(type=EXTERNAL, name=JDBC_ERROR, message="The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target". ClientConnectionId:1272c9a2-baae-4bd0-858f-5aca27eecbd1", query_id=20220816_082956_00059_5zqk3)

These apparently are due to the database not being connectable, so it might be:

  • the client needs updating, and/or
  • there's some other configuration change that's needed
@StevenMaude StevenMaude moved this to Next in Data Team Aug 16, 2022
@StevenMaude StevenMaude removed the status in Data Team Aug 16, 2022
StevenMaude added a commit that referenced this issue Jan 4, 2023
#856 has been open for a few months and it has not been resolved.

In the meantime, this check only serves to spam my GitHub notifications
every single weekday, to inform of the same problem.

This change should be reverted when #856 is fixed.
StevenMaude added a commit that referenced this issue Jan 4, 2023
#856 has been open for a few months and it has not been resolved.

In the meantime, this check only serves to spam my GitHub notifications
every single weekday, to inform of the same problem.

This change should be reverted when #856 is fixed.
@StevenMaude
Copy link
Contributor Author

We should then re-enable the scheduled check disabled in #905, perhaps with lower frequency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant