yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

Honestly, I don't know what to say from a Nova side if cloud-init isn't
correctly running on the guest.

The only interaction that would impact Nova would be the metadata
service, which could be unavailable, or, or... but if the guest just
doesn't run cloud-init and with other official images it does work
properly, then I don't think this is a Nova problem.

Moving the bug to Opinion for the Nova project, but please change the
status back to New once you find evidence that Nova is messing up with
metadata or whatever else but not the guest image.

** Changed in: nova
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1859525

Title:
  Setting release file causes cloud-init failure to launch

Status in kolla-ansible:
  Incomplete
Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Kolla-Ansible 8.0.1 Stein installation on CentOS

  We ran into an issue where Ubuntu images would not launch Cloud-Init
  when deployed.  This started after we added the file:

  /etc/nova/release

  with the contents:

  [Nova]
  vendor = Company
  product = Company Cloud
  package = ""

  This was specified in the Kolla configuration file in
  /etc/kolla/config/release, which is copied to /etc/nova/release on all
  compute nodes.

  All images deployed fine previously, which have the appropriate
  os_distro and os_type to "ubuntu" and "linux", respectively.

  Deployment testing is pretty simple, such as:

  openstack server create --image 72270019-df0d-4d7e-a90c-dbc1d64b98db
  --network TestNetwork001 --flavor t5sd.4xlarge --key-name testkey
  --security-group AllowSSHInbound TestUbuntuServer001

  After adding a floating IP, we tested connecting via SSH.  The
  connection failed.

  After removing all items from the "release" file above, so only the
  stanza [Nova] existed, and re-deploying Kolla-Ansible, verifying that
  the empty release file was installed on all compute nodes, and finally
  restarting all Nova containers, the problem goes away.

  Eric

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla-ansible/+bug/1859525/+subscriptions