Closed obnoxxx closed 2 months ago
@obnoxxx
The behavior of not allowing the operator to run (on production) if the namespace env var is not defined is by design.
Locally, when I run tests for this operator I use the command: OPERATOR_NAMESPACE="...." make test
After talking with @Madhu-1, we agreed that we want to preserve the production behavior while making the test usage simpler. For that, I am proposing the following fix: A change to the make test
target to set a default value for the OPERATOR_NAMESPACE
, only if it is not defined. I would further suggest using the same default namespace we use for the make build-installer
and make deploy
commands as the default value.
This change should be local to the test target and should not have any side effects on other make targets.
+1
JFYI:- even after the change, the test won't run it fails in the next steps.
@Madhu-1 wrote:
JFYI:- even after the change, the test won't run it fails in the next steps.
I can confirm this:
Running OPERATOR_NAMESPACE=foo make test
fails, but differently, without the panic.
@Madhu-1 tells me, however, that there is no point in fixing the test currently, as there are plans to remove/replace the whole test code.
Is there an issue to track that?
@nb-ohad is working on the test suite for it, AFAIK we don't have an issue tracker for it.
@obnoxxx The fix for the make test to introduce a default namespace is necessary even with my changes to how we implement tests.
The second issue, you might want to skip that one
@nb-ohad wrote:
@obnoxxx The fix for the make test to introduce a default namespace is necessary even with my changes to how we implement tests.
The second issue, you might want to skip that one
Are you suggesting, in order to address this issue, to fix the missing namespace setting and ignore the other test failure?
@nb-ohad wrote:
@obnoxxx The fix for the make test to introduce a default namespace is necessary even with my changes to how we implement tests. The second issue, you might want to skip that one
Are you suggesting, in order to address this issue, to fix the missing namespace setting and ignore the other test failure?
Yes that's correct
Describe the bug
On my Fedora 40 system,
make test
fails with a panic on a freshmain
clone:Environment details
main
branchSteps to reproduce
Steps to reproduce the behavior:
Here is what I did:
make
(--> succeeds)make test
Actual results
Describe what happened
make test
fails with the panic pasted aboveExpected behavior
make test
should pass.Logs
N/A (see paste above)
Additional context