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.

Sign up for GitHub

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

Jump to bottom

Errors on initialize step with latest module version (2.0.1) #757

Closed
gregslack78 opened this issue Feb 21, 2023 · 6 comments · Fixed by #761
Closed

Errors on initialize step with latest module version (2.0.1) #757

gregslack78 opened this issue Feb 21, 2023 · 6 comments · Fixed by #761
Assignees
@daltondhcp
Labels
triage

Comments

@gregslack78
Copy link

Since the latest module was installed I am seeing a number of errors in the pull initialize step immediately after "Processing Management Group [Tenant Root Group]"

Where-Object: The term 'Where-Object' is not recognized as a name of a cmdlet, function,
script file, or executable program. Check the spelling of the name, or if a
path was included, verify that the path is correct and try again.
##[error]PowerShell exited with code '1'.

SetValueInvocationException: Exception setting "type": "The property 'type' cannot be found on this object.
Verify that the property exists and can be set."
##[error]PowerShell exited with code '1'.

Write-PSFMessage: The term 'Write-PSFMessage' is not recognized as a name of a cmdlet, function,
script file, or executable program. Check the spelling of the name, or if a
path was included, verify that the path is correct and try again.
##[error]PowerShell exited with code '1'.

Steps to reproduce

  1. Run a pull pipeline ensuring you are on the latest module version (2.0.1)

Screenshots
image
@daltondhcp
Copy link
Contributor

daltondhcp commented Feb 21, 2023 •
edited
Loading

Thank you for reporting. We have seen this issue intermittently even prior to 2.0.0. Can you confirm if it worked on second attempt or if it breaks on every run? As an additional data point, can you please share your settings.json config?

@gregslack78
Copy link
Author

gregslack78 commented Feb 21, 2023 via email

@daltondhcp
Copy link
Contributor

daltondhcp commented Feb 21, 2023 •
edited
Loading

Thanks. Can you change "Message.Info.Maximum" to 9 (debug) and re-run to hopefully get additional insights what it is failing on. As an additional data point, can you please share your settings.json config?

@daltondhcp daltondhcp self-assigned this Feb 21, 2023
@jsandquist
Copy link
Contributor

@gregslack78 FYI - some references to previous findings: #656 and #699.

@daltondhcp
Copy link
Contributor

Thanks for the input, @jsandquist. I've had some side conversations with Greg and it indeed seems to be related to the increased parallelization in 2.0.

While we are nailing down the exact pattern and how to sustainably mitigate this from a more holistic point of view, I have advised to lower the "Core.ThrottleLimit" from default 10 to 5 or lower, which seems to have mitigated the issue during our attempts to reproduce the problem.

@gregslack78
Copy link
Author

gregslack78 commented Feb 23, 2023 via email •
edited by daltondhcp
Loading

@daltondhcp daltondhcp mentioned this issue Feb 24, 2023
Merged
5 tasks
@daltondhcp daltondhcp linked a pull request Feb 24, 2023 that will close this issue
Reliability improvements #761
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daltondhcp daltondhcp

Labels
triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reliability improvements daltondhcp/AzOps
3 participants
@jsandquist @daltondhcp @gregslack78