sous-chefs/etcd

7.0.0+ No longer works

Closed this issue ยท 0 comments

๐Ÿ—ฃ๏ธ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

๐Ÿ‘ป Brief Description

When using etcd cookbook 7.0.0 or 7.0.1, the start service is not working properly.

etcd_service node['hostname'] do
  advertise_client_urls "http://#{node['ipaddress']}:2379"
  listen_client_urls "http://#{node['ipaddress']}:2379,http://127.0.0.1:2379"
  initial_advertise_peer_urls "http://#{node['ipaddress']}:2380"
  listen_peer_urls "http://#{node['ipaddress']}:2380"
  initial_cluster_token 'etcd-cluster-1'
  initial_cluster cluster_members.join(',')
  initial_cluster_state 'existing'
  default_service_name true
  data_dir '/var/lib/etcd'
  enable_v2 true
  action :start
end

After adding additional logging, the resource is not picking up any of those resource attributes. I have narrowed down the issue to the unified_mode true line in etcd_service.rb resource. When I set that to be false, everything works fine. Alternatively, if I use etcd_service_manager_systemd resource directly it also works fine.

๐Ÿฅž Cookbook version

7.0.0/7.0.1

๐Ÿ‘ฉโ€๐Ÿณ Chef-Infra Version

Tested on both 15.17.4 & 17.2.29

๐ŸŽฉ Platform details

RHEL

Steps To Reproduce

Steps to reproduce the behavior:

  1. Use resource above
  2. Run chef-client
  3. Note that the etcd service file created is not using the default name and has none of the attributes passed in

๐Ÿš“ Expected behavior

Resource attributes should properly pass to the systemd resource

โž• Additional context

Add any other context about the problem here. e.g. related issues or existing pull requests.