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

The graph node for azurerm_backup_protected_vm has no │ configuration attached to it. This suggests a bug in Terraform's apply │ graph builder; please report it! #31915

Closed
petercharleston opened this issue Sep 30, 2022 · 8 comments
Labels
bug duplicate issue closed because another issue already tracks this problem

Comments

@petercharleston
Copy link

Terraform Version

Running latest version from Azure DevOps agent which i think is : terraform_1.3.0

│ Error: Resource node has no configuration attached
│ 
│ The graph node for azurerm_backup_protected_vm has no
│ configuration attached to it. This suggests a bug in Terraform's apply
│ graph builder; please report it!

Terraform Configuration Files

/*
resource "azurerm_recovery_services_vault" "RSV" {
name = local.RSVName
location = azurerm_resource_group.AzureResourceGroup.location
resource_group_name = azurerm_resource_group.AzureResourceGroup.name
sku = "Standard"
soft_delete_enabled = false
tags = {

CustomerName = var.CustomerName

}
}##Primary RSV

Debug Output

.

Expected Behavior

Commented out from .tf file as wanted to destroy the RSV in Azure
The resource did get destroyed but the Apply failed with mentioned Error

/*
resource "azurerm_recovery_services_vault" "RSV" {
name = local.RSVName
location = azurerm_resource_group.AzureResourceGroup.location
resource_group_name = azurerm_resource_group.AzureResourceGroup.name
sku = "Standard"
soft_delete_enabled = false
tags = {

CustomerName = var.CustomerName

}
}##Primary RSV

*/

Actual Behavior

Commented out from .tf file as wanted to destroy the RSV in Azure
The resource did get destroyed but the Apply failed with mentioned Error

Steps to Reproduce

.

Additional Context

.

References

.

@petercharleston petercharleston added bug new new issue not yet triaged labels Sep 30, 2022
@jbardin
Copy link
Member

jbardin commented Sep 30, 2022

Thanks @petercharleston, combining with #31850
Duplicate of #31850

@jbardin jbardin closed this as completed Sep 30, 2022
@petercharleston
Copy link
Author

petercharleston commented Sep 30, 2022 via email

@crw crw added duplicate issue closed because another issue already tracks this problem and removed new new issue not yet triaged labels Oct 3, 2022
@petercharleston
Copy link
Author

petercharleston commented Oct 4, 2022 via email

@jbardin
Copy link
Member

jbardin commented Oct 4, 2022

@petercharleston,

#31850 is an open issue, it has not yet been solved.
You can watch or contribute to that issue as we investigate.

@petercharleston
Copy link
Author

petercharleston commented Oct 4, 2022 via email

@crw
Copy link
Collaborator

crw commented Oct 4, 2022

Hi @petercharleston, please post further comments on #31850. Perhaps it will be determined that these are two separate issues, but that determination is unlikely to happen on this thread.

I would also suggest using the community forum where there are more people ready to help. The GitHub issues here are monitored only by a few core maintainers.

Thanks!

@petercharleston
Copy link
Author

petercharleston commented Oct 5, 2022 via email

@github-actions
Copy link

github-actions bot commented Nov 5, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate issue closed because another issue already tracks this problem
Projects
None yet
Development

No branches or pull requests

3 participants