-
Notifications
You must be signed in to change notification settings - Fork 455
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
Sync Trigger fails when AzureWebJobsStorage is not set and functions host is running in Managed Environment (ACA) #10686
Labels
Comments
the requirement is that the sync trigger should be called without failures. A PR to support this along with the sync trigger optimization below |
ishank12
added a commit
to ishank12/azure-functions-host
that referenced
this issue
Jan 24, 2025
… ManagedAppEnvironment for Hybrid Logic Apps Issue : Azure#10686
9 tasks
ishank12
added a commit
to ishank12/azure-functions-host
that referenced
this issue
Feb 27, 2025
… ManagedAppEnvironment for Hybrid Logic Apps Issue : Azure#10686 (cherry picked from commit cd15f8f)
siddharth-ms
pushed a commit
that referenced
this issue
Feb 27, 2025
…Environment (#10894) * Fix sync trigger error when AzureWebjobsStorage is not set in case of ManagedAppEnvironment for Hybrid Logic Apps Issue : #10686 (cherry picked from commit cd15f8f) * Add test (cherry picked from commit 9f30d19) * Resolved comments (cherry picked from commit 33ef8a1) * Fixed comment (cherry picked from commit be030c5) * fix comment - skip hash check when client is not set (cherry picked from commit bb83e10) * update test for managedenv (cherry picked from commit 95d4409) * add test for kubernetes managed env (cherry picked from commit 88801b0) * resolve comments - to use cache disabled in test (cherry picked from commit 4b24959) --------- Co-authored-by: Ishank Gupta <[email protected]>
siddharth-ms
pushed a commit
that referenced
this issue
Feb 28, 2025
…Environment (#10894) * Fix sync trigger error when AzureWebjobsStorage is not set in case of ManagedAppEnvironment for Hybrid Logic Apps Issue : #10686 (cherry picked from commit cd15f8f) * Add test (cherry picked from commit 9f30d19) * Resolved comments (cherry picked from commit 33ef8a1) * Fixed comment (cherry picked from commit be030c5) * fix comment - skip hash check when client is not set (cherry picked from commit bb83e10) * update test for managedenv (cherry picked from commit 95d4409) * add test for kubernetes managed env (cherry picked from commit 88801b0) * resolve comments - to use cache disabled in test (cherry picked from commit 4b24959) --------- Co-authored-by: Ishank Gupta <[email protected]>
siddharth-ms
pushed a commit
that referenced
this issue
Mar 4, 2025
…App Environment (#10767) * Fix sync trigger error when AzureWebjobsStorage is not set in case of ManagedAppEnvironment for Hybrid Logic Apps Issue : #10686 * Add test * Update release notes * Update release_notes.md * Resolved comments * Fixed comment * fix comment - skip hash check when client is not set * update test for managedenv * add test for kubernetes managed env * resolve comments - to use cache disabled in test --------- Co-authored-by: Ishank Gupta <[email protected]>
@ishank12 I see that the PR for resolving this has been merged. Are you keeping this open to track its official release? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Logic Apps Hybrid runs on ACA on the customers Kubernetes server cluster and does not have any runtime dependency on Azure Storage.
So there is no AzureWebJobsStorage setting in Hybrid Logic Apps.
in that case the SyncTrigger always fails trying to connect to blob.
the code where issue exist is below
azure-functions-host/src/WebJobs.Script.WebHost/Management/FunctionsSyncManager.cs
Lines 138 to 142 in ba3e9ef
Check for a solution in the Azure portal
For issues in production, please check for a solution to common issues in the Azure portal before opening a bug. In the Azure portal, navigate to your function app, select
Diagnose and solve problems
from the left, and view relevant dashboards before opening your issue.Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
Provide a description of the expected behavior.
Actual behavior
Provide a description of the actual behavior observed.
Known workarounds
Provide a description of any known workarounds.
Related information
Provide any related information
The text was updated successfully, but these errors were encountered: