-
Notifications
You must be signed in to change notification settings - Fork 56
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
URI::InvalidURIError: the scheme http does not accept registry part: fe80::c9bb:d19a:ed30:2443:5985 (or bad hostname?) #67
Comments
looks like it is trying to connect to the windows node using an IPv6 ip that it can't reach. This can happen for a number of reasons. Often because of misconfigured network settings. Start by checking to see if the provisioned node has a valid and reachable IP address. |
Hi mwrock, I manage to disable the ipv6 through Windows registry and convert into a VM template. This works. However, I met with another problem. here is the error message from
Here is my default.rb used to provision the VM.
I realize that the IPv4 has not been configured but the DNS IP has been configured. How do I resolve this? |
Hi mwrock, Just to note that the IP address is private. |
The machine from where you are running the provisioning must be able to reach the provisioned node in order to bootstrap it with the chef client. |
Hi mwrock, Thanks for the quick reply. Just want to ask you, do I need to set any IP address on the VM template before bootstrapping? This is one thing that I dont understand. Because I have specified the IP to be set on the new VM created from the VM templare and I thought chef-provisioner will do that. |
shouldn't have to set an ip in the template. That would defeat the purpose of the template :). VMWare should set the ip appropriately based on the provisioning config. However sometimes that can break because:
I suggest cloning the VM directly from the vsphere client first, assigning all the settings you intend to set in the chef provisioner. Then see if the vm is assigned the ip you expect and you can reach that machine on that IP. If things don't work in the vsphere client, you want to troubleshoot outside of chef just to make it less confusing where things might be going wrong. |
Hi mwrock, Thanks for the quick reply! I managed to narrow down to the portion where I need a DHCP server to assign the IP address and it will work well. However, I have encountered another problem.
I saw on the console that it have this message.
In this case, I am setting up my own chef server and I want to ask if there is a way to bypass the certificate verify. Thanks. |
You can get around this error by specifying See the chef-provisioning readme for a list of convergence options. |
Hi mwrock, Thanks for the quick reply! I have tried what you have suggested but still I cant bypass the certificate error.
I do a manual check on the NEW_VM machine and saw that the chef was successfully installed.
I also did a check on the
After I do a manual set to
This is the output from chef-stacktrace.out
What do I miss over here? Thanks. :) |
Odd, that always worked for me when I used this driver. Regarding the recipe error, your node is missing the cher-provisioning gem. |
Hi mwrock, Thanks for your quick reply! I have installed the chef-provisioning in the node. I still can't solve the
This is chef-stacktrace.out from the workstation where I issue the command to provision the new VM.
Any ideas how to I proceed? Thanks. |
Hi mwrock, I would like to ask what version of chef-client did you use?
I saw on this link and I thought they are quite similar. The chef-client installed on the node contained a ruby version of 2.0.0. I would like to ask could it be the embedded ruby that causes this problem? Thanks. |
My apologies for the delay getting back to you. I don't think this has anything to do with chef or ruby version. I just got some vsphere infra access and ran through a recipe and realized I gave you misinformation. The
That should set the right indo in your client.rb file and cause your node to ignore ssl validation errors. |
Hi mwrock, Thanks for the quick reply! I have tried to place the
outside This is
this is the
How do I resolve this problem? Thanks. |
The failure on the workstation is just saying that the chef-client run failed on the node. The node failure looks like it is trying to converge a machine resource. Are you running a machine resource on the node to provision another machine? |
Hi mwrock, I am running on a physical workstation (Windows 10) that is running on ChefDK to provision a node located in the vCenter. |
What run list are you setting on the provisioned node? Does it include your machine recipe and is that intentional? |
Hi mwrock, Thanks for your prompt reply! The command I have issued to perform provisioning on my workstation is I have been trying to follow what is written on here since I am provisioning Windows 2012R2 and how I perform sysprep on the Windows node is followed this example before I turned it into a VM template. Let me know if I miss out anything. :) |
So I think the issue here is that you are using the same recipe to bootstrap the node that you are to provision it. Since your recipie has:
Your worrkstation runs it to provision server09 and then once provisioned, server09 will converge with that recipie. So it really does not do provisioning only but rather provisions and then converges. The |
Hi mwrock, i have made changes to what you have told me and it works! Thanks you so much! |
You can send questions to the chef-dev list at https://discourse.chef.io/ |
Hi,
I have encountered an error while provisioning a new Windows VM.
The error from the chef-stacktrace.out is shown below.
any idea what the error means?
Thanks.
The text was updated successfully, but these errors were encountered: