-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
RHODS_1.20.0_GA, RHODS_1.21.0_GA, RHODS_1.31.0_GA
Description of problem:
Anaconda cannot be enabled because the validator job doesn't get created.
Could be related to https://issues.redhat.com/browse/RHODS-5945
Prerequisites (if any, like setup, operators/versions):
Install RHODS Self-managed or Cloud Service
Steps to Reproduce
- Go to RHODS Dashboard > Explore
- click on Anaconda tile
- click on Enable button
- insert any key (even an invalid one is ok)
- click on Connect button
Actual results:
validation fails because the validator job is missing
Expected results:
validation fails or pass depending on the license key
Reproducibility (Always/Intermittent/Only Once):
Always on OpenShift > 4.11. From our automated runs on 4.10 it seems working fine
Build Details:
RHODS v1.21.0-21
Workaround:
Additional info:
- cron job "anaconda-ce-periodic-validator" exists, while the Job doesn't
- the issue is present in 1.20 too, but Anaconda couldn't be enabled because of another bug https://issues.redhat.com/browse/RHODS-5945 so this issue was not captured earlier
- is related to
-
RHODS-5945 InvalidImageName error while enabling Anaconda
- Closed