Question

I'm trying to add S3 bucket(S3 compatible) in profile. I'm receiving error

  • 6 November 2023
  • 5 comments
  • 101 views

Userlevel 2

failed to get bucket testpoc: GetBucketLocation: RequestError: send request failed caused by: Get "https://vm1.test1.com:9000/testpoc?location=": dial tcp: lookup vm1.test1.com on 10.96.0.10:53: server misbehaving.RequestError: send request failed caused by: Get "https://vm1.test1.com:9000/testpoc?location=": dial tcp: lookup vm1.test1.com on 10.96.0.10:53: server misbehaving.

 

Inside the Pod curl to s3 bucket endpoint link is not resolving. cat /etc/resolv.conf has this entry 10.96.0.10.

Could someone help?

 

 


5 comments

Userlevel 7
Badge +6

Hello @Madhuri 

Check the ports requirements:

Ports - User Guide for VMware vSphere (veeam.com)

Userlevel 7
Badge +20

Hi, is 10.96.0.10 your DNS or your bucket? I can see you’re talking to it on port 53 but I’m wondering what your bucket IP should resolve to. Can another endpoint resolve vm1.test1.com against this dns server?

Userlevel 3
Badge +1

@Madhuri 

based on the error message , vm1.test1.com is not resolving or either rejecting the traffic. 

Can you try to create location profile with an IP Address of vm1.test1.com ? and see the result ?

10.96.0.10 possibly would be your service address of your dns pod, so all pods will contain that address as name server in resolve.conf. 

 

Regards
Satish

Userlevel 2

@Satish I did give a try with IP address of the bucket. Error is different now.

There was a problem validating the profile
failed to get bucket testpoc: GetBucketLocation: RequestError: send request failed caused by: Get "https://10.202.x.x:9000/testpoc?location=": tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, not 10.202.x.x
Could you suggest here?

 
Userlevel 3
Badge +1

@Madhuri since you are using IP, you might need to “Skip certificate chain and hostname verification” when creating the profile. 

Comment