I was implemented, "install_chef_client" option for AmazonLinux.

[suzumura-ss]

Hi there

I was implemented install_chef_client option for AmazonLinux.

• Install the Chef-client when generating the EC2 instance.
• The solution is to comment out the setting of the Defaults requiretty of /etc/sudoers, the problem of sudo mkdir -p in AWS::Action::SyncFolders#call fails.
• user_data option will be overwritten for this option.
  If the user_data option and install_chef_client option is enabled at the same time, it will display a warning to the user.

[sevos]

Hey, thanks for the contribution! However I think that desired way to install chef-client is to use vagrant-omnibus plugin. What do you think?

[suzumura-ss]

Sorry, I did not know vagrant-omnibus plugin.
Therefore, I have tried the vagrant-omnibus plugin,
The AIM of default of AmazonLinux, I will get the error below.

    :
[default] Waiting for instance to become "ready"...
[default] Waiting for SSH to become available...
[default] Machine is booted and ready for use!
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.

An error occurred while executing the action on the 'default'
machine. Please handle this error then try again:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

echo $(chef-solo --v | awk "{print \$2}" || "")

Then, I will get the error below even if I do not use a vagrant-omnibus plugin (only vagrant-aws plugin), when I use the default AIM of AmazonLinux.

    :
[default] Rsyncing folder: /Users/suzumura/vagrant/ec2/vagrant-2/ => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'

So, I left only the part to be able to use the sudo command via ssh.