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

Unable to connect to v center via self signed ssl certifcate (allow_unverified_ssl == false is failing) #1994

Closed
1 of 4 tasks
pradeep-git23 opened this issue Aug 17, 2023 · 6 comments
Labels
bug Type: Bug

Comments

@pradeep-git23
Copy link

Community Guidelines

  • I have read and agree to the HashiCorp Community Guidelines .
  • Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
  • Do not leave "+1" or other comments that do not add relevant information or questions.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Terraform

1.4

Terraform Provider

v2.4.1

VMware vSphere

7.0.3

Description

When allow_unverified_ssl == false , Automation is failing

Affected Resources or Data Sources

provider "vsphere" {
user = "{{vmware_user}}"
password = "{{vmware_pass}}"
vsphere_server = "{{vcenter}}"
allow_unverified_ssl = false
}

Terraform Configuration

automation is failing while allow_unverified_ssl = false

Debug Output

�[31m│�[0m �[0m�[1m�[31mError: �[0m�[0m�[1merror setting up new vSphere SOAP client: Post "https://ip.of.vcenter/sdk": x509: certificate signed by unknown authority�[0m

Panic Output

No response

Expected Behavior

It should execute terraform plan and apply
.

Actual Behavior

Failing with the error at terraform Plan. �[31m│�[0m �[0m�[1m�[31mError: �[0m�[0m�[1merror setting up new vSphere SOAP client: Post "https://ip/sdk": x509: certificate signed by unknown authority�[0m

Steps to Reproduce

allow_unverified_ssl = false
while executing automation from awx to vcenter

Environment Details

No response

Screenshots

error from awx

References

No response

@pradeep-git23 pradeep-git23 added bug Type: Bug needs-triage Status: Issue Needs Triage labels Aug 17, 2023
@github-actions
Copy link

Hello, pradeep-git23! 🖐

Thank you for submitting an issue for this provider. The issue will now enter into the issue lifecycle.

If you want to contribute to this project, please review the contributing guidelines and information on submitting pull requests.

@tenthirtyam
Copy link
Collaborator

Set it to true for self-signed or add the vCenter Server and VMCA certificates to your trust store if using false.

@tenthirtyam tenthirtyam removed the needs-triage Status: Issue Needs Triage label Aug 17, 2023
@pradeep-git23
Copy link
Author

Hi @tenthirtyam thank you for your input i am using K8 cluster for running awx.

@tenthirtyam tenthirtyam added vsphere/v8 vSphere 8.0 and removed vsphere/v8 vSphere 8.0 labels Sep 5, 2023
@tenthirtyam
Copy link
Collaborator

Are you still having an issue?

@tenthirtyam
Copy link
Collaborator

No reply from OP.

@tenthirtyam tenthirtyam closed this as not planned Won't fix, can't repro, duplicate, stale Nov 13, 2023
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Type: Bug
Projects
None yet
Development

No branches or pull requests

2 participants