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.

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

[QE] integration: Setting env var on windows fail #4618

Open
albfan opened this issue Feb 13, 2025 · 1 comment · May be fixed by #4624
Open

[QE] integration: Setting env var on windows fail #4618

albfan opened this issue Feb 13, 2025 · 1 comment · May be fixed by #4624
Assignees
Labels
kind/bug Something isn't working

Comments

@albfan
Copy link
Contributor

albfan commented Feb 13, 2025

General information

crc might be setting boolean parameters incorrectly

Operating System

Windows

Hypervisor

Hyper-V

Did you run crc setup before crc start?

yes

Running on

Laptop

Steps to reproduce

test disable update check

CRC version

CRC status

CRC config

Host Operating System

windows 10

Expected behavior

env var set is readed correctly

Actual behavior

error parsing the command line created

CRC Logs

Step starting CRC with default bundle succeeds: command '$env:CRC_DISABLE_UPDATE_CHECK=true; crc start -p 'C:\Users\rhqp\crc-e2e\pull-secret' ', expected to succeed, exited with exit code: 1
Command stdout: 
Command stderr: true : The term 'true' is not recognized as the name of a cmdlet, function, script file, or operable program. Check 
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:31
+ $env:CRC_DISABLE_UPDATE_CHECK=true; crc start -p 'C:\Users\rhqp\crc-e ...
+                               ~~~~
    + CategoryInfo          : ObjectNotFound: (true:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
 
level=debug msg="CRC version: 2.47.0+457b65\n"
level=debug msg="OpenShift version: 4.17.14\n"

Additional context

From a quick test:

PS C:\Users\crcqe> $env:CRC_DISABLE_UPDATE_CHECK="true"
PS C:\Users\crcqe> echo $env:CRC_DISABLE_UPDATE_CHECK  
true
PS C:\Users\crcqe> $env:CRC_DISABLE_UPDATE_CHECK='true'
PS C:\Users\crcqe> echo $env:CRC_DISABLE_UPDATE_CHECK  
true
PS C:\Users\crcqe> $env:CRC_DISABLE_UPDATE_CHECK=$true 
PS C:\Users\crcqe> echo $env:CRC_DISABLE_UPDATE_CHECK 
True
PS C:\Users\crcqe> $env:CRC_DISABLE_UPDATE_CHECK=true 
true: The term 'true' 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.
@albfan albfan added the kind/bug Something isn't working label Feb 13, 2025
@albfan albfan self-assigned this Feb 14, 2025
@praveenkumar
Copy link
Member

Is this bug around e2e? may be when create an issue put [e2e] or [integration] as part of title so that it is easy to figure out where this issue.

@albfan albfan changed the title Setting env var on windows fail [QE] integration: Setting env var on windows fail Feb 17, 2025
@albfan albfan linked a pull request Feb 17, 2025 that will close this issue
@albfan albfan moved this to Work In Progress in Project planning: crc Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
Status: Work In Progress
Development

Successfully merging a pull request may close this issue.

2 participants