use_blockstorage_volume option causes error 'There is no such action: os-set_image_metadata","code":400'

_This issue was originally opened by @vertrost as hashicorp/packer#8429. It was migrated here as a result of the [Packer plugin split](https://github.com/hashicorp/packer/issues/8610#issuecomment-770034737). The original body of the issue is below._

### Overview of the Issue

I am building suse15 image with packer and ansible scripts, however when I am adding parameter "use_blockstorage_volume": "true" - image building fails with error:

```
Build 'openstack' errored: Error setting image metadata: Bad request with: [POST https:///v3/0c2ea4d147794927b81dd1a3807788de/volumes/b8057af7-e582-4f38-993c-20085e958d22/action], error message: {"badRequest":{"message":"There is no such action: os-set_image_metadata","code":400}}
```

### Reproduction Steps

Build image with provided json.

### Packer version

1.4.5

### Simplified Packer Buildfile

```
{
"provisioners": [{
"type": "shell-local",
"inline": ["echo 'rubber ducky'> ducky.txt"]
}],
"builders": [{
"type": "openstack",
"identity_endpoint": "...",
"tenant_name": "{{user `dev_tenant_name`}}",
"domain_name": "{{user `dev_domain_name`}}",
"username": "{{user `dev_username`}}",
"password": "{{user `dev_password`}}",
"ssh_username": "linux",
"region": "...",
"image_name": "suse15",
"instance_name": "suse15-packer",
"source_image_name": "Beta_SLES15_SP0_latest",
"availability_zone": "...",
"flavor": "s2.medium.1",
"networks": ["..."],
"security_groups" : ["sg-packer"],
"use_blockstorage_volume": "true"
}],
"post-processors": [{
"strip_path": true,
"output": "packer-template-centos-updating-result.log",
"type": "manifest"
}]
}
```

### Log Fragments and crash.log files

[packer-log.txt](https://github.com/hashicorp/packer/files/3904753/packer-log.txt)

Inizia dal percorso del builder OpenStack che gestisce use_blockstorage_volume e imposta i metadati dell’immagine sul volume. Riproduci il problema con il buildfile Packer semplificato e confronta il risultato con packer-log.txt. Il lavoro è completato quando la build non fallisce più a causa dell’azione non supportata os-set_image_metadata.

Scritto dal modello di indicizzazione a partire dal testo della issue.