[chef] Re: Re: Re: Re: Re: Re: Chef cookbooks converges to 0 resources


Chronological Thread 
  • From: Vijaya Bhaskar < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Chef cookbooks converges to 0 resources
  • Date: Fri, 23 Jan 2015 10:10:21 +0530

I have found the issue. The confidugration: default['openstack']['compute']['network']['service_type'] is set in a cookbook named openstack-common. When I set the option correctly , deployment went fine. The openstack cookbooks, I have used so far, keystone, glance are working fine. I have not tested the neutron/nova deployment with chef. After the testing, I will update the status, so that it will be a useful feedback to you, I think.


On Thu, Jan 22, 2015 at 10:58 PM, JJ Asghar < " target="_blank"> > wrote:
Hi Vijaya,

Nice to see people are leveraging Chef and Openstack. As you
undoubtedly know Openstack in extremely interdependent on the
different projects and setting up just one thing usually is a
challenge.

That being said, we are in the process of deprecating the chef-repo
(https://github.com/stackforge/openstack-chef-repo) in favor for the
testing-stack (https://github.com/jjasghar/chef-openstack-testing-stack)
with chef provisioning.

We have some neutron builds in there:
https://github.com/jjasghar/chef-openstack-testing-stack/blob/master/aio-neutron.rb
and as you can see it heavily relies on the roles that we define.

If you have an specific questions or would like to bounce some ideas
don't hesitate to ping me directly "> , or drop by our IRC
channel on freenode #openstack-chef.
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2


On Thu, Jan 22, 2015 at 5:11 AM, Vijaya Bhaskar
< "> > wrote:
> Thank you, I think that must be the case. I'll take on from here. I have
> found a workaround by adding the compute cookbook as the dependency for this
> cookbook.  The service_type is set as 'network'
>
> On Thu, Jan 22, 2015 at 4:20 PM, Tensibai < "> > wrote:
>>
>> I did not go really far in the analysis of your problem but most of the
>> recipes in openstack-network start with:
>>
>> ['quantum',
>> 'neutron'].include?(node['openstack']['compute']['network']['service_type'])
>> || return
>>
>> which ends up the recipe compilation if the attribute
>> node['openstack']['compute']['network']['service_type'] is not 'quantum' or
>> 'neutron' (this attribute is not set by default in this cookbook)
>>
>> I suspect you're missing some attributes for this runlist and all the
>> recipes returns before defining any resource to be converged, that's why it
>> ends up with 0 resources.
>>
>>
>>
>> I can't help more on the subject, hope someone more used to this can give
>> you a better hint/guide lines
>>
>>
>>
>> Le 2015-01-22 11:17, Vijaya Bhaskar a écrit :
>>
>> Hi ,
>>
>> Thank you for the response:
>>
>> Here is the link to the debug log:
>> https://gist.github.com/anonymous/b5ab6a435f6c06b8187a
>>
>>
>> On Thu, Jan 22, 2015 at 3:35 PM, AJ Christensen
>> < > wrote:
>>>
>>> Run with debug logging turned on via -l debug and post that to a
>>> gist/pastebin service.
>>>
>>> cheers,
>>>
>>> --aj
>>>
>>> On Thu, Jan 22, 2015 at 11:03 PM, Vijaya Bhaskar
>>> < "> > wrote:
>>> > Hello All,
>>> >
>>> > I am trying to deploy openstack network with chef. When I run the
>>> > chef-client , it simply finishes with 0 resources:
>>> >
>>> > :~# chef-client
>>> >
>>> > [2015-01-22T15:21:04+05:30] WARN:
>>> > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>> > * *
>>> > * *
>>> > SSL validation of HTTPS requests is disabled. HTTPS connections are
>>> > still
>>> > encrypted, but chef is not able to detect forged replies or man in the
>>> > middle
>>> > attacks.
>>> >
>>> > To fix this issue add an entry like this to your configuration file:
>>> >
>>> > ```
>>> >   # Verify all HTTPS connections (recommended)
>>> >   ssl_verify_mode :verify_peer
>>> >
>>> >   # OR, Verify only connections to chef-server
>>> >   verify_api_cert true
>>> > ```
>>> >
>>> > To check your SSL configuration, or troubleshoot errors, you can use
>>> > the
>>> > `knife ssl check` command like so:
>>> >
>>> > ```
>>> >   knife ssl check -c /etc/chef/client.rb
>>> > ```
>>> >
>>> > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>> > * *
>>> > * *
>>> >
>>> > Starting Chef Client, version 11.16.4
>>> > resolving cookbooks for run list:
>>> > ["openstack-network::identity_registration",
>>> > "openstack-network::linuxbridge", "openstack-network::l3_agent",
>>> > "openstack-network::dhcp_agent", "openstack-network::metadata_agent",
>>> > "openstack-network::server"]
>>> > Synchronizing Cookbooks:
>>> >   - openstack-identity
>>> >   - openstack-network
>>> >   - openstack-common
>>> >   - smf
>>> >   - apt
>>> >   - database
>>> >   - yum-mysql-community
>>> >   - yum
>>> >   - mysql
>>> >   - postgresql
>>> >   - rbac
>>> >   - openssl
>>> >   - aws
>>> >   - xfs
>>> >   - mysql_chef_gem
>>> >   - build-essential
>>> >   - chef-sugar
>>> >   - yum-epel
>>> >   - mariadb
>>> > Compiling Cookbooks...
>>> > Converging 0 resources
>>> >
>>> > Running handlers:
>>> > Running handlers complete
>>> > Chef Client finished, 0/0 resources updated in 6.136653261 seconds
>>> >
>>> > No other cookbooks have this issue and the node has a role assigned to
>>> > it.
>>> >
>>> > Please update about the possible reasons of failure.
>>
>>
>>
>>
>
>




Archive powered by MHonArc 2.6.16.

§