Arm deployment for Azure Data Factory failed without error message about arm-deploy HOT 38 CLOSED

Hi all,
we have identified the root cause of this issue, will inform once we have an update regarding the fix checkin and rollout.

from arm-deploy.

Would be great if you could rollout the bugfix until tomorrow afternoon CET, since we are relying on this Action for our deployments.

from arm-deploy.

Hi @marvinbuss , we are still figuring out the fix, i will update once it is ready.

from arm-deploy.

Hi all,
the fix has been deployed. Let us know if you are still facing the issue

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

@andiasmara
Can you try running the action in debug mode to get more helpful logs?
You can refer https://docs.github.com/en/free-pro-team@latest/actions/managing-workflow-runs/enabling-debug-logging#enabling-runner-diagnostic-logging to enable the debug mode.
It will be great if you can share the failed run.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

@kanika1894
Should I enable "runner diagnostic logging" only or "step debug logging" as well?
and how can I share the log with you? there are some quite sensitive data in the log.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is stale because it has been open for 7 days with no activity.

from arm-deploy.

To enable step debug logging, you must set the following secret in the repository that contains the workflow: ACTIONS_STEP_DEBUG to true.
After setting the secret, more debug events are shown in the step logs. That can help you identify the issue.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

@andiasmara Can you please provide logs as mentioned by @kanika1894 ?
Since you mentioned it contains sensitive data, can you send it to

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

@andiasmara Any update?

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

@andiasmara waiting for your inputs.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is stale because it has been open for 7 days with no activity.

from arm-deploy.

@vineetmimrot and @kanika1894. Have you received the log files?

from arm-deploy.

@andiasmara Yes we have received the logs and @tejasd1990 is working on this issue.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

We are running into the same issue with another ARM template. We tried to deploy Private DNS Zones and came across the same issue. Do you have enough logs or do you need more data @tejasd1990 & @vineetmimrot ?
Any idea when this will be fixed?

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

@tejasd1990 Can we expect a fix later today?
Thanks for your help!

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is stale because it has been open for 7 days with no activity.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is stale because it has been open for 7 days with no activity.

from arm-deploy.

Possibly this will show more info
#40

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is stale because it has been open for 7 days with no activity.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

This issue is marked default for generating issues report.

from arm-deploy.

Closing this issue due to inactivity. Please reopen if you are still facing the same issue. @andiasmara

from arm-deploy.