OCPBUGS-115550: use different INSTALL_INVOKER for unconfigured ignition - #10848
OCPBUGS-115550: use different INSTALL_INVOKER for unconfigured ignition#10848zaneb wants to merge 1 commit into
Conversation
The INSTALL_INVOKER environment variable in assisted-service is now set to agent-installer-postconfig when the agent unconfigured-ignition workflow is used, distinguishing it from the regular agent-installer workflow. This will show up in installations using the appliance or the OVE installer. Assisted-by: Claude Code
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@zaneb: This pull request references Jira Issue OCPBUGS-115550, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe agent template data now includes an install-invoker suffix. Unconfigured ignition sets the suffix to ChangesInstall invoker suffix templating
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to This localized change distinguishes the installer invocation for unconfigured ignition workflows; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. (1 skipped: 1 unsupported.) Full details: Stable And Deterministic Test NamesExplanation PASS: The pull request changes only a template value and Go template data plumbing. The commit adds no test files and no Full details: Test Structure And QualityExplanation PASS: The pull request changes only an environment template and two implementation files. It does not add or modify any Ginkgo test code, assertions, waits, setup, or cleanup. Therefore, the stated Ginkgo test-quality requirements are not applicable. Full details: Microshift Test CompatibilityExplanation PASS: The pull request changes only one environment template and two production Go files. The commit adds no Full details: Single Node Openshift (Sno) Test CompatibilityExplanation PASS: The pull request changes only an environment template and two Go implementation files. The diff adds no Ginkgo e2e tests or other new tests, so the SNO multi-node compatibility check is not applicable. Full details: Topology-Aware Scheduling CompatibilityExplanation PASS: The commit changes only an assisted-service environment template and template-data generation. It adds Full details: Ote Binary Stdout ContractExplanation PASS: The pull request changes only a template value, a template-data field, and the Full details: Ipv6 And Disconnected Network Test CompatibilityExplanation PASS — The pull request adds no Ginkgo e2e tests. The diff changes one environment template and two production Go files to set Full details: No-Weak-CryptoExplanation PASS: The pull request changes only a template variable, a template-data field, and the literal suffix "-postconfig". The diff introduces no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom cryptography, or secret comparison logic. The crypto API searches in the changed Go files also found no matches. Full details: Container-PrivilegesExplanation PASS: The pull request changes only an assisted-service environment template and Go template data. The diff adds Full details: No-Sensitive-Data-In-LogsExplanation No sensitive-data logging was introduced. The diff only adds ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Some tools did not complete. Review the errors below. 🔧 golangci-lint (2.13.2)Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions Comment |
|
@zaneb: This pull request references Jira Issue OCPBUGS-115550, which is valid. 3 validation(s) were run on this bug
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/retest-required |
|
/pipeline required |
|
Scheduling tests matching the |
|
@zaneb: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/retest-required |
|
/cc @andfasano |
| EPHEMERAL_INSTALLER_CLUSTER_TLS_CERTS_OVERRIDE_DIR=/opt/agent/tls | ||
| HW_VALIDATOR_REQUIREMENTS=TO_BE_REPLACED_BY_SYSTEMD | ||
| INSTALL_INVOKER=agent-installer | ||
| INSTALL_INVOKER=agent-installer{{.InstallInvokerSuffix}} |
There was a problem hiding this comment.
Currently in Assisted Service there's an exact string match for the specific ABI branches (see repo:openshift/assisted-service "agent-installer"), and also in Assisted Installer (see https://github.com/openshift/assisted-installer/blob/d4580efc20c260403b055a58368b1c12642dd80e/src/common/common.go#L40).
If we want to distinguish the different workflows then I think we'll need to have a less strict check in those repos first (ie, checking the invoker string begins with "agent-installer" should be good enough to cover all the cases)
There was a problem hiding this comment.
ugh, good point I completely forgot about those :(
|
/hold |
The INSTALL_INVOKER environment variable in assisted-service is now set to agent-installer-postconfig when the agent unconfigured-ignition workflow is used, distinguishing it from the regular agent-installer workflow.
This will show up in installations using the appliance or the OVE installer.
Summary by CodeRabbit
-postconfigsuffix automatically.