[chef] Re: Re: Facing 401 unauthorized errors intermittently on Windows


Chronological Thread 
  • From: Madhurranjan Mohaan < >
  • To:
  • Subject: [chef] Re: Re: Facing 401 unauthorized errors intermittently on Windows
  • Date: Fri, 30 Mar 2012 10:15:16 +0530

Yes they are all different. The Customization spec in Vmware doesn't even run if the name is present in the Domain Controller.  So we are sure the names are different.

On Fri, Mar 30, 2012 at 2:52 AM, Bryan McLellan < "> > wrote:
On Thu, Mar 29, 2012 at 10:46 AM, Madhurranjan Mohaan
< "> > wrote:
> I am trying to get the Windows VMs to run jobs similar to bootstrap. The
> knife vsphere plugin wasn't quite working. So I have a powershell script
> that spawns off a VM and uses Customization spec. As part of the
> customization spec, I run the following command :
> "C:\opscode\chef\bin\chef-client -j C:\etc\chef\first-boot.json" . As part
> of my template, I already have chef installed along with the c:\etc\chef
> containing "client.rb", " validation.pem" and "first-boot.json" .
>
> Problem is that this seems to be working alternatively. Every 2nd time it
> fails with the 401 Authorized error ( Searched for this error and I can
> safely say that the various files are right). I have opened the Vmware
> console a couple of times to see what happens and every time I do that I can
> see that the chef run succeeds  .  Any suggestions around what I can do to
> make this more stable?

Are you sure the node_name (based on the hostname) of the VMs are all
different? The new client could be trying to register with the same
name of an existing client.

Bryan




Archive powered by MHonArc 2.6.16.

§