opennebula_template and opennebula_image datasources not working anymore after upgrade provider ppgrade

[ps-beilers]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v1.3.4
+ provider registry.terraform.io/opennebula/opennebula v1.0.1

Affected Resource(s)

• opennebula_template
• opennebula_image

Terraform Configuration Files

data "opennebula_template" "generic_ubuntu_terraform" {
  name = "Generic Ubuntu Terraform"
}
data "opennebula_image" "bionic" {
  name = "bionic_2022-11"
}

Debug Output

(https://gist.github.com/ps-beilers/a7cda9f3af56351acb4446b8334c5867)

Panic Output

Expected Behavior

The datasources should have returned the template and image objects.

Actual Behavior

No objects were found. The plan or apply commands fail with Error: (images|templates) filtering failed

Steps to Reproduce

We upgraded our community OpenNebula installation from 5.6 to 6.2. Afterwards we upgraded the terraform provider from 0.4.0 to 1.0.1. We also tried with 0.5.2 which showed the same issues as 1.0.1.

1. terraform apply

Important Factoids

References

• 0000

[treywelsh]

I reproduced the problem for the template datasource, we already discussed around this problem (in #349 around hasXXX flags handling).

However for the image datasource I didn't reproduced, is it related to #331 (could you check @ps-beilers ) ? If yes, we're waiting for a PR to update the goca dependency which fix some default behavior. If not, I'll need to test in depth.

[ps-beilers]

I reproduced the problem for the template datasource, we already discussed around this problem (in #349 around hasXXX flags handling).

However for the image datasource I didn't reproduced, is it related to #331 (could you check @ps-beilers ) ? If yes, we're waiting for a PR to update the goca dependency which fix some default behavior. If not, I'll need to test in depth.

Hi @treywelsh

Most likely it is related to #331, yes. Looking forward to the fix from #371 making it into the next tag.

Regards, Bernd