Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to destroy host #34

Open
syphernl opened this issue Mar 21, 2022 · 8 comments · May be fixed by #46
Open

Unable to destroy host #34

syphernl opened this issue Mar 21, 2022 · 8 comments · May be fixed by #46
Labels
waiting Waiting for answer

Comments

@syphernl
Copy link

When destroying using terraform plan -destroy -out destroy.plan we're getting an error:

│ Error: -32602 (Invalid params.): Invalid parameter "/1": a number is expected.

The only way to be able to fully destroy an infra-stack is by removing the Zabbix Host manually via the Zabbix Webinterface and from the state using:

terraform state rm zabbix_host.this
@pdecat
Copy link
Member

pdecat commented Jul 27, 2022

What version of terraform, the provider and Zabbix server are in use?

Does this error happen with just terraform destroy?

Does you have a minimum configuration sample to reproduce this issue?

@pdecat pdecat added the waiting Waiting for answer label Jul 27, 2022
@mahsoud
Copy link

mahsoud commented Sep 15, 2022

We are seeing this with latest version of provider and zabbix v6

@scytem
Copy link

scytem commented Sep 27, 2022

@pdecat please check the PR above. Seems like it's working after this fix.

@scytem
Copy link

scytem commented Sep 28, 2022

@pdecat do you plan to bump the provider version to implement this fix?

@scytem
Copy link

scytem commented Oct 17, 2022

@pdecat Hello! Seems like you improving tests. Is there any news related to this fix? I'm using my own downstream fork build, but probably I can help somehow.

@aloisiobilck
Copy link

Hi,
Any news?
I am using zabbix 6, terraform 1.3.x and the latest version 0.4.0

@rdavisunr
Copy link

Also looking for news on this one. When will the release be available?

@pdecat
Copy link
Member

pdecat commented Mar 23, 2023

@pdecat Hello! Seems like you improving tests. Is there any news related to this fix? I'm using my own downstream fork build, but probably I can help somehow.

Hi @scytem, sorry for the silence here.

When all the compatibility issues with newer Zabbix server versions started being reported, I indeed spent some time testing the provider across several versions of Zabbix server, only to discover maintaining compatibility with all those versions would mean a lot of work in both the API lib and the provider.

I'm starting to believe the best way forward would be have compatibility with a single Zabbix server major version in each provider version. A bit like Gitlab did recently.
Still a lot of work to follow server API changes across versions, though.

Anyway, I do not have the bandwidth to work on this right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting Waiting for answer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants