Comment 7 for bug 1995609

EC2 instances are started w/ Ansible which injects the following `cloud-init.j2`:

»»»»»»»»»»»»»»»» start cloud-init.j2
#cloud-config
# vim: syntax=yaml
repo_update: true
repo_upgrade: all

groups:
  - {{ devops_group }}

users:
{% for i in company_devops %}
  - name: {{ i }}
    gecos: {{ company_employees[i].name }}
    primary_group: {{ devops_group }}
    groups: wheel
    no_user_group: True
    ssh_authorized_keys:
{% for key in company_employees[i].pub_keys %}
      - {{ key }}
{% endfor %}
{% endfor %}

runcmd:
  - echo 'JXdoZWVsCUFMTD0oQUxMKQlOT1BBU1NXRDogQUxMCg==' | base64 -d > /etc/sudoers.d/wheel
  - chage -E -1 -d 01/01/2017 -M 99999 root
  - rm -f /root/anaconda-ks.cfg /root/original-ks.cfg
  - /usr/bin/hostnamectl set-hostname {{ inventory_hostname }}
  - echo yes > {{ machine_is_ansible_ready_file }}

»»»»»»»»»»»»»»»» end cloud-init.j2

The initial machine is started w/ this.
From that machine a snapshot is created.
Another machine is started from the snapshot and this latter machine has this issue.