[TencentCloud] source_image_name failed to retrieve source image by name

[jianzhiteh]

Overview of the Issue

We try to query source_image_name by passing in the custom image name we want to create our new image from, but the build seems failed with error below:

Reference - Feature Request: #9548

❯ packer build tencentcloud-cfs.json
tencentcloud-cvm: output will be in this color.

==> tencentcloud-cvm: Trying to check image name: our-image-name...
    tencentcloud-cvm: Image name: useable
==> tencentcloud-cvm: Trying to check source image: ...
==> tencentcloud-cvm: No image found under current instance_type(S2.MEDIUM4) restriction
Build 'tencentcloud-cvm' errored after 2 seconds 239 milliseconds: No image found under current instance_type(S2.MEDIUM4) restriction

Reproduction Steps

Steps to reproduce this issue

packer build

Packer version

1.7.0

Simplified Packer Buildfile

"source_image_name": "our-source-image-name",

Log Fragments and crash.log files

tencentcloud-cvm: output will be in this color.
2021/02/23 15:51:26 Force build: false

2021/02/23 15:51:26 On error: 
2021/02/23 15:51:26 Waiting on builds to complete...
2021/02/23 15:51:26 Starting build run: tencentcloud-cvm
2021/02/23 15:51:26 Running builder: tencentcloud-cvm
2021/02/23 15:51:26 [INFO] (telemetry) Starting builder tencentcloud-cvm
==> tencentcloud-cvm: Trying to check image name: our-image-name...
    tencentcloud-cvm: Image name: useable
==> tencentcloud-cvm: Trying to check source image: ...
2021/02/23 15:51:28 [INFO] (telemetry) ending tencentcloud-cvm
==> tencentcloud-cvm: No image found under current instance_type(S2.MEDIUM4) restriction
==> Wait completed after 1 second 730 milliseconds
2021/02/23 15:51:28 machine readable: error-count []string{"1"}
==> Some builds didn't complete successfully and had errors:
2021/02/23 15:51:28 machine readable: tencentcloud-cvm,error []string{"No image found under current instance_type(S2.MEDIUM4) restriction"}
==> Builds finished but no artifacts were created.
2021/02/23 15:51:28 [INFO] (telemetry) Finalizing.
Build 'tencentcloud-cvm' errored after 1 second 730 milliseconds: No image found under current instance_type(S2.MEDIUM4) restriction

==> Wait completed after 1 second 730 milliseconds

==> Some builds didn't complete successfully and had errors:
--> tencentcloud-cvm: No image found under current instance_type(S2.MEDIUM4) restriction

[SwampDragons]

In AWS, sometimes filters can fail if you're building in the wrong region -- could that be the issue here?

[jianzhiteh]

Hi @SwampDragons thanks for the reply. But I don't think it's the case here, as I could run packer to build the image successfully if I pass in the source_image_id instead.

[ghost]

This issue has been automatically migrated to hashicorp/packer-plugin-tencentcloud#5 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-tencentcloud#5.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.