Description

babyhuey

opened on Jan 16, 2024

Issue body actions

Looks like ssl cert got updated yesterday, and it's set for *.netlify.app and causing issues in logs:

WARNING   2024-01-16 16:46:30,278 urllib3.connection.connection:547 | Certificate did not match expected hostname: usage.feast.dev. Certificate: {'subject': ((('countryName', 'US'),), (('stateOrProvinceName', 'California'),), (('localityName', 'San Francisco'),), (('organizationName', 'Netlify, Inc'),), (('commonName', '*.netlify.app'),)), 'issuer': ((('countryName', 'US'),), (('organizationName', 'DigiCert Inc'),), (('commonName', 'DigiCert Global G2 TLS RSA SHA256 2020 CA1'),)), 'version': 3, 'serialNumber': '03ED167A2659DA278E7B21CDBEB33E32', 'notBefore': 'Jan 15 00:00:00 2024 GMT', 'notAfter': 'Feb 14 23:59:59 2025 GMT', 'subjectAltName': (('DNS', '*.netlify.app'), ('DNS', 'netlify.app')), 'OCSP': ('http://ocsp.digicert.com/',), 'caIssuers': ('http://cacerts.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crt',), 'crlDistributionPoints': ('http://crl3.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl', 'http://crl4.digicert.com/DigiCertGlobalG2TLSRSASHA2562020CA1-1.crl')}

Reacted by Matt Armand and SeanWidesense

Activity

1. babyhuey

   added

   kind/bug

   priority/p2

   on Jan 16, 2024
2. robhowley commented on Jan 17, 2024

   

   robhowley

   on Jan 17, 2024

   Contributor

   More actions

   ran into the same issue. as a stopgap, i set FEAST_USAGE to false and it went away. I know I shouldn't really be advocating for people to work around feast telemetry, but it should keep things quiet until a real fix goes in.

   Reacted by Hannah Lyons, Matt Armand, Harry and Breno Costa
3. tokoko commented on Feb 8, 2024

   

   tokoko

   on Feb 8, 2024

   Collaborator

   More actions

   This has already been fixed, right?

   Reacted by SeanWidesense
4. redhatHameed commented on Feb 19, 2024

   

   redhatHameed

   on Feb 19, 2024

   Contributor

   More actions

   found similar warnings when using Feast in OpenShift/Kubernetes but setting environments FEAST_USAGE=False and it get disappeared.
5. SeanWidesense commented on Feb 27, 2024

   

   SeanWidesense

   on Feb 27, 2024

   More actions

   When running "feast serve" the certificate warning still appears as of a pip download on Feb 25, 2024.
6. shuchu commented on Apr 10, 2024

   

   shuchu

   on Apr 10, 2024

   Collaborator

   More actions

   let's disable the feature of "usage.feast.dev". It will be more useful for the users who use Feast at Enterprise level.
7. shuchu

   self-assigned this

   on Apr 10, 2024
8. haoxu0

   closed this as completedin #4090on Apr 15, 2024

Issue actions