Source image not found when searching by image name

Abierto
#14 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
go
Área
cloud

Línea de trabajo

Comienza con la ruta del builder de OpenStack que gestiona source_image, usando la configuración build.json proporcionada y comparando ejecuciones con y sin las opciones de blockstorage. Reproduce el fallo con el nombre de la imagen y la ejecución correcta con el ID de la imagen; se considera terminado cuando la imagen de origen indicada se inicia correctamente sin esas opciones.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

builder/openstack community-supported plugin question

This issue was originally opened by @v0lumehi as hashicorp/packer#8630. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.


Hello guys,

I think I discovered a bug in the openstack builder.
I have following packer version:

$ packer --version
1.5.1

This is my packer config and it is working fine:

{
  "variables": {
    "git_username": "",
    "git_password": ""
  },
  "builders": [{
    "type": "openstack",
    "flavor": "m.large",
    "image_name": "jenkins-chef-slave-nightly",
    "source_image": "ubuntu-18.04-x86_64-latest",
    "ssh_username": "ubuntu",
    "identity_endpoint": "https://my.great.cloud:5000/v3",
    "networks": ["6e80f6c6-3a24-44be-b15c-54b1f9d86c6e"],
    "floating_ip_network": "6541b7d0-db72-4a17-9d7e-de5d5b894ead",
    "security_groups": ["97e99840-e6f0-4fff-8f67-2afd3b8a3c43"],
    "use_blockstorage_volume": true,
    "volume_size": 10,
    "volume_name": "jenkins-chef-slave-nightly-volume",
    "image_disk_format": "qcow2",
    "metadata": {
      "image_name": "jenkins-chef-slave-nightly"
    }
  }],
  "provisioners": [{
      "type": "shell",
      "environment_vars": [
        "GIT_USERNAME={{user `git_username`}}",
        "GIT_PASSWORD={{user `git_password`}}"
      ],
      "scripts": [
        "./common/scripts/ubuntu/base.sh",
        "./common/scripts/ubuntu/docker.sh",
        "./common/scripts/ubuntu/chefdk.sh",
        "./common/scripts/ubuntu/users.sh",
        "./common/scripts/ubuntu/cleanup.sh"
      ]
    }
  ]
}

Now if I remove this block:

"use_blockstorage_volume": true,
"volume_size": 10,
"volume_name": "jenkins-chef-slave-nightly-volume",
"image_disk_format": "qcow2",

and run packer, packer throws this error:

$ packer build build.json
openstack output will be in this color.

==> openstack: Loading flavor: m.large
    openstack: Verified flavor. ID: 92506745-0305-4997-a58a-0f1a6be40a08
==> openstack: Creating temporary keypair: packer_5e26cac3-61bd-d7be-f4b1-463cc436cbc4 ...
==> openstack: Created temporary keypair: packer_5e26cac3-61bd-d7be-f4b1-463cc436cbc4
==> openstack: Launching server...
==> openstack: Launching server...
==> openstack: Error launching source server: Bad request with: [POST https://my.great.cloud:8774/v2.1/2b1777b0d2ec4263a6f0a63a0f313670/servers], error message: {"badRequest": {"message": "Invalid input for field/attribute imageRef. Value: ubuntu-18.04-x86_64-latest. u'ubuntu-18.04-x86_64-latest' is not valid under any of the given schemas", "code": 400}}
==> openstack: Terminating the source server:  ...
==> openstack: Error terminating server, may still be around: Resource not found
==> openstack: Deleting temporary keypair: packer_5e26cac3-61bd-d7be-f4b1-463cc436cbc4 ...
Build 'openstack' errored: Error launching source server: Bad request with: [POST https://my.great.cloud:8774/v2.1/2b1777b0d2ec4263a6f0a63a0f313670/servers], error message: {"badRequest": {"message": "Invalid input for field/attribute imageRef. Value: ubuntu-18.04-x86_64-latest. u'ubuntu-18.04-x86_64-latest' is not valid under any of the given schemas", "code": 400}}

==> Some builds didn't complete successfully and had errors:
--> openstack: Error launching source server: Bad request with: [POST https://my.great.cloud:8774/v2.1/2b1777b0d2ec4263a6f0a63a0f313670/servers], error message: {"badRequest": {"message": "Invalid input for field/attribute imageRef. Value: ubuntu-18.04-x86_64-latest. u'ubuntu-18.04-x86_64-latest' is not valid under any of the given schemas", "code": 400}}

==> Builds finished but no artifacts were created.

If I replace the source_image name with its ID, it's working properly:

$ packer build build.json
openstack output will be in this color.

==> openstack: Loading flavor: m.large
    openstack: Verified flavor. ID: 92506745-0305-4997-a58a-0f1a6be40a08
==> openstack: Creating temporary keypair: packer_5e26cb83-cafb-8502-3cd6-727f291199f5 ...
==> openstack: Created temporary keypair: packer_5e26cb83-cafb-8502-3cd6-727f291199f5
==> openstack: Launching server...
==> openstack: Launching server...
    openstack: Server ID: 0c516d5d-d23e-4ee4-8355-b78d28bdc6b3
==> openstack: Waiting for server to become ready...
==> openstack: Creating floating IP using network 6541b7d0-db72-4a17-9d7e-de5d5b894ead ...
    openstack: Created floating IP: 'f58318df-3644-420a-af6b-fdfa3c803549' (10.0.30.38)
==> openstack: Associating floating IP 'f58318df-3644-420a-af6b-fdfa3c803549' (10.0.30.38) with instance port...
    openstack: Added floating IP 'f58318df-3644-420a-af6b-fdfa3c803549' (10.0.30.38) to instance!
==> openstack: Using ssh communicator to connect: 10.0.30.38
==> openstack: Waiting for SSH to become available...
==> openstack: Connected to SSH!
==> openstack: Provisioning with shell script: ./common/scripts/ubuntu/base.sh
...
==> openstack: Deleting temporary keypair: packer_5e26cb83-cafb-8502-3cd6-727f291199f5 ...
Build 'openstack' finished.

==> Builds finished. The artifacts of successful builds are:
--> openstack: An image was created: 0983f994-6de4-4894-8fd1-4f700c2dc644

Do you got any idea what causes this? Am I overseeing something?
Best Regards

Lenguaje dominante
Go
Estrellas
29
Forks
27
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de hashicorp/packer-plugin-openstack

Todos los issues de hashicorp/packer-plugin-openstack

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.