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 add new rules in existing nsxt_policy_lb_virtual_server resource #826

Closed
mpyrsch opened this issue Jan 13, 2023 · 0 comments · Fixed by #843
Closed

unable to add new rules in existing nsxt_policy_lb_virtual_server resource #826

mpyrsch opened this issue Jan 13, 2023 · 0 comments · Fixed by #843
Assignees
Labels
bug Bug

Comments

@mpyrsch
Copy link

mpyrsch commented Jan 13, 2023

Describe the bug

Bug only appears in Version 3.2.9 (3.2.8 works fine)

If we create a new nsxt_policy_lb_virtual_server resource including http forwarding rule(s), the initial deployment works fine.
If we try to add new rule(s) to the existing virtual server, terraform plan & apply is successfull but the rule(s) are not applied in nsx-t. If we rerun terraform plan terraform also states that the new rules are not applied yet.

Reproduction steps

  1. existing resource "nsxt_policy_lb_virtual_server" including http forwarding rule(s)
  2. add new http forwarding rule(s) to existing resource with terraform vmware/nsxt version 3.2.9
  3. check in nsx-t manager gui or edgenode cli if new rule is added

Expected behavior

You should be able to add rules to an existing virtual server anytime

Additional context

No response

@mpyrsch mpyrsch added the bug Bug label Jan 13, 2023
@annakhm annakhm self-assigned this Feb 27, 2023
@annakhm annakhm linked a pull request Feb 28, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants