Add postgresql-18 tests into test suite#98
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
|
[test] |
|
[test] |
|
@pkhartsk Please rebase it against master. Thanks |
2c91b0f to
4800c23
Compare
📝 WalkthroughWalkthroughThis PR expands the Ansible OpenShift test playbook to verify newer RHEL 9 and 10 container image variants. The playbook's test loops are updated to reference new MariaDB, MySQL, PostgreSQL, Python, and Ruby container images, and eight new YAML variable files are added to configure deployment parameters and validation behavior for each container type. ChangesContainer Image Test Coverage Expansion
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@deploy-and-test.yml`:
- Around line 122-124: Two RHEL10 test loops ("full-run" and "s2i-only") are
missing the rhel10-s2i-ruby-40-container entry; add the
rhel10-s2i-ruby-40-container string to both lists so Ruby 4.0 on RHEL10 is
exercised (i.e., insert rhel10-s2i-ruby-40-container alongside
rhel10-s2i-ruby-33-container and the Python entries in the same YAML sequence
for each loop).
In `@vars/rhel10-mariadb-118-container.yml`:
- Line 4: The DATABASE_SERVICE_NAME environment variable is using an invalid
value with a dot ("mariadb-11.8") which mismatches pod_name (mariadb-118);
update the DATABASE_SERVICE_NAME assignment to "mariadb-118" so it matches
pod_name and avoids service-name validation/deployment failures (look for
DATABASE_SERVICE_NAME in the vars/rhel10-mariadb-118-container.yml and change
its value to mariadb-118).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 46da61ae-71cc-4741-8324-2bd75d40f49f
📒 Files selected for processing (9)
deploy-and-test.ymlvars/rhel10-mariadb-118-container.ymlvars/rhel10-postgresql-18-container.ymlvars/rhel10-s2i-python-314-minimal-container.ymlvars/rhel10-s2i-ruby-40-container.ymlvars/rhel9-mariadb-118-container.ymlvars/rhel9-postgresql-18-container.ymlvars/rhel9-s2i-python-314-container.ymlvars/rhel9-s2i-ruby-40-container.yml
| - rhel10-s2i-ruby-33-container | ||
| - rhel10-s2i-python-312-minimal-container | ||
| - rhel10-s2i-python-314-minimal-container |
There was a problem hiding this comment.
Add the RHEL10 Ruby 4.0 S2I case to both RHEL10 test loops.
rhel10-s2i-ruby-40-container is missing from the full-run and s2i-only loops, so Ruby 4.0 on RHEL10 is not exercised. This leaves a coverage hole relative to the PR objective. See Line 122 and Line 196 sections.
Suggested patch
@@
- rhel10-mysql-84-container
- rhel10-s2i-ruby-33-container
+ - rhel10-s2i-ruby-40-container
- rhel10-s2i-python-312-minimal-container
- rhel10-s2i-python-314-minimal-container
@@
- rhel10-nodejs-ex-24
- rhel10-nodejs-ex-24-minimal
- rhel10-s2i-ruby-33-container
+ - rhel10-s2i-ruby-40-container
- rhel10-s2i-python-312-minimal-container
- rhel10-s2i-python-314-minimal-containerAlso applies to: 196-199
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@deploy-and-test.yml` around lines 122 - 124, Two RHEL10 test loops
("full-run" and "s2i-only") are missing the rhel10-s2i-ruby-40-container entry;
add the rhel10-s2i-ruby-40-container string to both lists so Ruby 4.0 on RHEL10
is exercised (i.e., insert rhel10-s2i-ruby-40-container alongside
rhel10-s2i-ruby-33-container and the Python entries in the same YAML sequence
for each loop).
| registry_redhat_io: "rhel10/mariadb-118" | ||
| tag_name: "mariadb:11.8-el10" | ||
| deployment: "oc process -f https://raw.githubusercontent.com/sclorg/mariadb-container/master/examples/mariadb-persistent-template.json -p MARIADB_VERSION=11.8-el10 -p NAMESPACE={{ oc_project_rhscl }} \ | ||
| -p DATABASE_SERVICE_NAME=mariadb-11.8 \ |
There was a problem hiding this comment.
Fix invalid/inconsistent database service name.
At Line 4, DATABASE_SERVICE_NAME=mariadb-11.8 includes a dot and does not match the rest of this config (pod_name: mariadb-118). Use mariadb-118 to avoid service-name validation/deployment failures.
Suggested patch
- -p DATABASE_SERVICE_NAME=mariadb-11.8 \
+ -p DATABASE_SERVICE_NAME=mariadb-118 \📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| -p DATABASE_SERVICE_NAME=mariadb-11.8 \ | |
| -p DATABASE_SERVICE_NAME=mariadb-118 \ |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@vars/rhel10-mariadb-118-container.yml` at line 4, The DATABASE_SERVICE_NAME
environment variable is using an invalid value with a dot ("mariadb-11.8") which
mismatches pod_name (mariadb-118); update the DATABASE_SERVICE_NAME assignment
to "mariadb-118" so it matches pod_name and avoids service-name
validation/deployment failures (look for DATABASE_SERVICE_NAME in the
vars/rhel10-mariadb-118-container.yml and change its value to mariadb-118).
|
/retest |
Wait until GA before merging
Summary by CodeRabbit