-
Notifications
You must be signed in to change notification settings - Fork 567
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
HCI Box Logon Script Failing when windowsAdminPassword parameter contains a $ character #2440
Comments
Did your HCIBoxConfig.psd1 get corrupted somehow? I havent seen that before. Can you share the HCIBoxConfig.psd1 file contents? I've done multiple deploys off main since then and haven't encountered this so I am suspecting its a one-off. |
It doesn't seem to be corrupted. Here are the contents of the config psd1 file:
} |
I did find a link to this issue just now which indicates it could be a problem with the password I was using - it did in fact have a '$' in it which may be causing the powershell files to misread the env variables |
The dollar sign in the password was in fact the issue, the script is executing now just fine. |
ah ha, interesting find. I will look for a way to mitigate or at least warn users. |
nb |
This issue has been closed, added a note in docs for this edgecase: |
Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?
https://github.com/Azure/arc_jumpstart_docs/tree/main/docs/azure_jumpstart_hcibox
Describe the issue or the bug
Upon entering the VM produced a setup script should be run - but fails on the first step of importing the powershell data file.
To Reproduce
Expected behavior
For the script to succeed and deploy remaining resources.
Environment summary
azure-cli : 2.56.0
bastion: 0.3.0
azd: 1.6.1
Have you looked at the Troubleshooting and Logs section?
Yes
Screenshots
Additional context
Powershell data file cannot be read in, seems to be invalid chars
The text was updated successfully, but these errors were encountered: