starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #1828] Ubuntu 18.04, Buster, and Leap 15 CI fail #939

New issue

Closed

opened 2026-03-04 01:50:04 +03:00 by kerem · 8 comments

kerem commented

2026-03-04 01:50:04 +03:00

Owner

Originally created by @gaul on GitHub (Jan 2, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1828

These fail with:

moved file content-type is not as expected expected:text/plain got:

Originally created by @gaul on GitHub (Jan 2, 2022). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1828 These fail with: ``` moved file content-type is not as expected expected:text/plain got: ```

kerem closed this issue

2026-03-04 01:50:04 +03:00

kerem commented

2026-03-04 01:50:05 +03:00

Author

Owner

@gaul commented on GitHub (Jan 3, 2022):

Buster mime-support should have /etc/mime.types:

https://packages.debian.org/buster/mime-support

But this is not installed by default and apt-get does not install it?!

@gaul commented on GitHub (Jan 3, 2022): Buster mime-support should have `/etc/mime.types`: https://packages.debian.org/buster/mime-support But this is not installed by default and `apt-get` does not install it?!

kerem commented

2026-03-04 01:50:05 +03:00

Author

Owner

@gaul commented on GitHub (Jan 3, 2022):

The MIME issue was a red herring; the real error is above:

SSL validation failed for https://127.0.0.1:8080/s3fs-integration-test/testrun-23332/test-s3fs-ALT.txt [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1056)
moved file content-type is not as expected expected:text/plain got:

I am not sure how this succeeded before but using HTTP resolve this.

@gaul commented on GitHub (Jan 3, 2022): The MIME issue was a red herring; the real error is above: ``` SSL validation failed for https://127.0.0.1:8080/s3fs-integration-test/testrun-23332/test-s3fs-ALT.txt [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1056) moved file content-type is not as expected expected:text/plain got: ``` I am not sure how this succeeded before but using HTTP resolve this.

kerem commented

2026-03-04 01:50:05 +03:00

Author

Owner

@petrus-v commented on GitHub (Jan 3, 2022):

I am not sure how this succeeded before but using HTTP resolve this.

Just an idea in reading this PR (I haven't tools to open the keystore.jks on my local machine) I'm wondering if the keystore.jks could contains self signed ssl certificat for localhost that could be used for testing secure things which coud expire at some point ?

@petrus-v commented on GitHub (Jan 3, 2022): > I am not sure how this succeeded before but using HTTP resolve this. Just an idea in reading this PR (I haven't tools to open the keystore.jks on my local machine) I'm wondering if the keystore.jks could contains self signed ssl certificat for localhost that could be used for testing secure things which coud expire at some point ?

kerem commented

2026-03-04 01:50:05 +03:00

Author

Owner

@gaul commented on GitHub (Jan 3, 2022):

The tests use a self-signed certificate which succeeds for newer distributions but fails for older ones. I suspect that the certificate that Java generates is somehow incompatible with the older Python implementation. There could be other solutions to this but using HTTP provides a slight performance advantage so maybe not worth investigating.

@gaul commented on GitHub (Jan 3, 2022): The tests use a self-signed certificate which succeeds for newer distributions but fails for older ones. I suspect that the certificate that Java generates is somehow incompatible with the older Python implementation. There could be other solutions to this but using HTTP provides a slight performance advantage so maybe not worth investigating.

kerem commented

2026-03-04 01:50:05 +03:00

Author

Owner

@petrus-v commented on GitHub (Jan 3, 2022):

ok thanks for reply !

@petrus-v commented on GitHub (Jan 3, 2022): ok thanks for reply !

kerem commented

2026-03-04 01:50:05 +03:00

Author

Owner

@gaul commented on GitHub (Jan 4, 2022):

Duplicate of #1812?

@gaul commented on GitHub (Jan 4, 2022): Duplicate of #1812?

kerem commented

2026-03-04 01:50:05 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 4, 2022):

@gaul
Yes, this issue is the same as #1812.
I've been investigating (and still investigating) a lot, but I still don't know the cause.

Could it be the cause of keystore.jks?
(I'm not very familiar with it)
I also tested renewal of CA certificate(package) and everything I can think, but the result was the same.

@ggtakec commented on GitHub (Jan 4, 2022): @gaul Yes, this issue is the same as #1812. I've been investigating (and still investigating) a lot, but I still don't know the cause. Could it be the cause of keystore.jks? (I'm not very familiar with it) I also tested renewal of CA certificate(package) and everything I can think, but the result was the same.

kerem commented

2026-03-04 01:50:05 +03:00

Author

Owner

@gaul commented on GitHub (Jan 8, 2022):

Duplicate of #1812.

@gaul commented on GitHub (Jan 8, 2022): Duplicate of #1812.

kerem referenced this issue

2026-03-04 02:01:48 +03:00

[PR #939] [MERGED] Prefer specific [io]stringstream where possible #1711