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

Bug s3.path-style-access Error When Changing Integration from MiniO to Oracle OCI Object Storage #125

Open
agentelinux opened this issue Dec 18, 2024 · 1 comment

Comments

@agentelinux
Copy link

Hi Guys,

I am using the configuration with MiniO, and everything works fine. However, when I change the storage to Oracle OCI Object Storage, the integration returns an error.

Temporary Workaround (Unusual Solution):
I discovered a workaround that involves using a new image fixture:

https://hub.docker.com/r/apache/iceberg-rest-fixture
(not found git source)

Steps to Reproduce:

Configure the integration with MiniO.
Switch to Oracle OCI Object Storage.
Observe the error during the integration process.

Expected Behavior:
The integration should work seamlessly when switching to Oracle OCI Object Storage.

Actual Behavior:
An error occurs when attempting to use Oracle OCI Object Storage.

Environment Details:

Software Version: [Specify the version]
Storage Provider: MiniO / Oracle OCI Object Storage
Additional Configuration: required s3.path-style-access=true

Very thanks

Caused by: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <bucket-name.my-namespace.compat.objectstorage.my-region.oraclecloud.com> doesn't match any of the subject alternative names: [swiftobjectstorage.my-region.oraclecloud.com]
        at org.apache.iceberg.aws.shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:507)
        at org.apache.iceberg.aws.shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:437)
@agentelinux
Copy link
Author

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

No branches or pull requests

1 participant