Azure / Azure/azure-quickstart-templates
pfSense freebsd failing to deploy.
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
[pf-freebsd-setup]( https://github.com/Azure/azure-quickstart-templates/tree/master/pf-freebsd-setup )
### Issue Details
Template is failing to fully deploy. The last few steps (nat/configurepf.sh) are failing with the following error:
> OPERATION IDBB675008D8BDA65D
TRACKING ID1a9373c7-99ec-4884-9153-e1094f4db0d5
STATUSConflict
PROVISIONING STATEFailed
TIMESTAMP3/3/2017, 3:19:37 PM
DURATION4 minutes 30 seconds
TYPEMicrosoft.Compute/virtualMachines/extensions
RESOURCE ID/subscriptions/dd017dd5-2752-4b8a-b59c-9ca4fe900660/resourceGroups/hce/providers/Microsoft.Compute/virtualMachines/hceopn-nat/extensions/configurepf
STATUSMESSAGE
`{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'configurepf'. Error message: "Malformed status file (000003)Invalid status/status: failed."
}
]
}
}`
RESOURCEhceopn-nat/configurepf
I do not know if it's relate, but because of this we are also unable to access the web gui of pfSense to configure it ourselves.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the pf-freebsd-setup template and inspect the nat/configurepf.sh step and configurepf VM extension referenced in the deployment error. Reproduce the deployment failure and trace the malformed status file; done means the final deployment steps complete successfully and the pfSense web GUI is accessible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100