Skip to content
This repository was archived by the owner on Sep 9, 2026. It is now read-only.

MGMT-23507: Update submodules to latest main - #55

Merged
openshift-merge-bot[bot] merged 1 commit into
mainfrom
MGMT-23507/update-submodules-latest
Apr 13, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
mainfrom
MGMT-23507/update-submodules-latest

Conversation

@eranco74

@eranco74 eranco74 commented Apr 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Update fulfillment-service submodule from 5587c36 to 80e77b6 (23 new commits)
  • Update osac-operator submodule from f4f99a7 to f81b015 (29 new commits)
  • osac-aap already at latest main — no change needed

Notable changes included

  • SecurityGroup provisioning support (completing networking API coverage)
  • Subnet deletion state propagation (MGMT-23637)
  • Networking retry with exponential backoff (MGMT-23624)
  • Organizations API (MGMT-22987)
  • Host/HostPool removal from both services
  • Lease type in private API
  • Leader election, database metrics, and various fixes

Test plan

  • Deploy with updated submodules and verify all networking resources (VirtualNetwork, Subnet, SecurityGroup, NetworkClass) work end-to-end
  • Verify Host/HostPool removal doesn't break existing deployments

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated internal service components to their latest versions.

…o latest main

Updates submodule refs to include SecurityGroup provisioning,
subnet deletion state propagation, networking retry backoff,
organizations API, Host/HostPool removal, and other recent changes.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci-robot

openshift-ci-robot commented Apr 12, 2026

Copy link
Copy Markdown

@eranco74: This pull request references MGMT-23507 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

  • Update fulfillment-service submodule from 5587c36 to 80e77b6 (23 new commits)
  • Update osac-operator submodule from f4f99a7 to f81b015 (29 new commits)
  • osac-aap already at latest main — no change needed

Notable changes included

  • SecurityGroup provisioning support (completing networking API coverage)
  • Subnet deletion state propagation (MGMT-23637)
  • Networking retry with exponential backoff (MGMT-23624)
  • Organizations API (MGMT-22987)
  • Host/HostPool removal from both services
  • Lease type in private API
  • Leader election, database metrics, and various fixes

Test plan

  • Deploy with updated submodules and verify all networking resources (VirtualNetwork, Subnet, SecurityGroup, NetworkClass) work end-to-end
  • Verify Host/HostPool removal doesn't break existing deployments

🤖 Generated with Claude Code

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.

@openshift-ci
openshift-ci Bot requested review from danmanor and tzvatot April 12, 2026 12:34
@openshift-ci-robot

openshift-ci-robot commented Apr 12, 2026

Copy link
Copy Markdown

@eranco74: This pull request references MGMT-23507 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

  • Update fulfillment-service submodule from 5587c36 to 80e77b6 (23 new commits)
  • Update osac-operator submodule from f4f99a7 to f81b015 (29 new commits)
  • osac-aap already at latest main — no change needed

Notable changes included

  • SecurityGroup provisioning support (completing networking API coverage)
  • Subnet deletion state propagation (MGMT-23637)
  • Networking retry with exponential backoff (MGMT-23624)
  • Organizations API (MGMT-22987)
  • Host/HostPool removal from both services
  • Lease type in private API
  • Leader election, database metrics, and various fixes

Test plan

  • Deploy with updated submodules and verify all networking resources (VirtualNetwork, Subnet, SecurityGroup, NetworkClass) work end-to-end
  • Verify Host/HostPool removal doesn't break existing deployments

🤖 Generated with Claude Code

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.

@openshift-ci-robot

openshift-ci-robot commented Apr 12, 2026

Copy link
Copy Markdown

@eranco74: This pull request references MGMT-23507 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

  • Update fulfillment-service submodule from 5587c36 to 80e77b6 (23 new commits)
  • Update osac-operator submodule from f4f99a7 to f81b015 (29 new commits)
  • osac-aap already at latest main — no change needed

Notable changes included

  • SecurityGroup provisioning support (completing networking API coverage)
  • Subnet deletion state propagation (MGMT-23637)
  • Networking retry with exponential backoff (MGMT-23624)
  • Organizations API (MGMT-22987)
  • Host/HostPool removal from both services
  • Lease type in private API
  • Leader election, database metrics, and various fixes

Test plan

  • Deploy with updated submodules and verify all networking resources (VirtualNetwork, Subnet, SecurityGroup, NetworkClass) work end-to-end
  • Verify Host/HostPool removal doesn't break existing deployments

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
  • Updated internal service components to their latest versions.

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.

@coderabbitai

coderabbitai Bot commented Apr 12, 2026

Copy link
Copy Markdown

Walkthrough

This pull request updates two submodule references. The base/osac-fulfillment-service submodule commit was updated to 80e77b66817985e903e0c34a28ee3ae01d8f5e2c, and the base/osac-operator submodule commit was updated to f81b015385154c341d5c5af5734722b3935c1127. Both changes involve a single line modification each with no alterations to exported or public entity declarations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: updating submodules to their latest versions on the main branch.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch MGMT-23507/update-submodules-latest

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
base/osac-operator (1)

1-1: Ensure comprehensive testing coverage for 52 commits across two submodules.

This PR updates osac-operator (29 commits) and osac-fulfillment-service (23 commits), introducing multiple significant features and changes:

  • SecurityGroup provisioning support
  • Subnet deletion state propagation
  • Networking retry with exponential backoff
  • Organizations API
  • Host/HostPool removal
  • Lease type additions
  • Leader election and database metrics

Given the scope, verify that the test plan covers all major features and potential integration points between the updated submodules.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@base/osac-operator` at line 1, The PR touches many cross-cutting features and
needs comprehensive tests: add unit tests for SecurityGroup provisioning (e.g.,
SecurityGroupProvisioner) and subnet state propagation (e.g., SubnetService)
including success/failure and state transitions; add unit+integration tests for
networking retry/backoff logic (e.g., NetworkingClient.retryWithBackoff or
exponentialBackoff) that assert retries, delays and jitter behavior and that
transient errors are retried while fatal errors abort; add controller/service
tests for the Organizations API (e.g.,
OrganizationsController/OrganizationsService) covering CRUD, validation and auth
cases; add tests for Host and HostPool removal flows (e.g.,
HostService/HostPoolManager) ensuring related resources are cleaned and edge
cases handled; add tests for new Lease type handling (e.g., LeaseType enum
consumer code) including serialization/deserialization and business logic that
branches on lease type; add leader election tests (e.g., LeaderElector) to
simulate leadership changes and ensure only leader executes critical work; add
tests for DB metrics emission (e.g., DBMetricsCollector) validating metrics
values and tagging; and add cross-module integration/system tests that exercise
interactions between osac-operator and osac-fulfillment-service for
provisioning, deletion propagation and org workflows, using mocks for external
systems, deterministic time control for backoff tests, and CI flaky-test
mitigation (retries/timeouts). Ensure test suites cover both happy and failure
paths and add appropriate test files and CI job updates to run them for both
submodules.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@base/osac-operator`:
- Line 1: Update the JIRA issue MGMT-23507 to include the target version
"4.22.0" for the target branch: open the JIRA ticket MGMT-23507 and set its
Target Version (or Fix Version/s) field to "4.22.0", save the change, and ensure
any related metadata (components/labels) required by CI for release tracking are
present so the bot no longer flags the missing target version.

---

Nitpick comments:
In `@base/osac-operator`:
- Line 1: The PR touches many cross-cutting features and needs comprehensive
tests: add unit tests for SecurityGroup provisioning (e.g.,
SecurityGroupProvisioner) and subnet state propagation (e.g., SubnetService)
including success/failure and state transitions; add unit+integration tests for
networking retry/backoff logic (e.g., NetworkingClient.retryWithBackoff or
exponentialBackoff) that assert retries, delays and jitter behavior and that
transient errors are retried while fatal errors abort; add controller/service
tests for the Organizations API (e.g.,
OrganizationsController/OrganizationsService) covering CRUD, validation and auth
cases; add tests for Host and HostPool removal flows (e.g.,
HostService/HostPoolManager) ensuring related resources are cleaned and edge
cases handled; add tests for new Lease type handling (e.g., LeaseType enum
consumer code) including serialization/deserialization and business logic that
branches on lease type; add leader election tests (e.g., LeaderElector) to
simulate leadership changes and ensure only leader executes critical work; add
tests for DB metrics emission (e.g., DBMetricsCollector) validating metrics
values and tagging; and add cross-module integration/system tests that exercise
interactions between osac-operator and osac-fulfillment-service for
provisioning, deletion propagation and org workflows, using mocks for external
systems, deterministic time control for backoff tests, and CI flaky-test
mitigation (retries/timeouts). Ensure test suites cover both happy and failure
paths and add appropriate test files and CI job updates to run them for both
submodules.
🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 639f24c2-7e00-46be-a24f-f47c9c9a9f95

📥 Commits

Reviewing files that changed from the base of the PR and between 1df6a30 and 1cd5b6a.

📒 Files selected for processing (2)
  • base/osac-fulfillment-service
  • base/osac-operator

Comment thread base/osac-operator
@@ -1 +1 @@
Subproject commit 6df2a1ed6882690c784645f0043dc1881ffc4557
Subproject commit f81b015385154c341d5c5af5734722b3935c1127

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Address JIRA target version warning.

The CI bot flagged that the referenced JIRA issue (MGMT-23507) is missing the expected target version "4.22.0" for the target branch. Please update the JIRA issue to include the correct target version to ensure proper release tracking.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@base/osac-operator` at line 1, Update the JIRA issue MGMT-23507 to include
the target version "4.22.0" for the target branch: open the JIRA ticket
MGMT-23507 and set its Target Version (or Fix Version/s) field to "4.22.0", save
the change, and ensure any related metadata (components/labels) required by CI
for release tracking are present so the bot no longer flags the missing target
version.

@openshift-ci-robot

openshift-ci-robot commented Apr 12, 2026

Copy link
Copy Markdown

@eranco74: This pull request references MGMT-23507 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

  • Update fulfillment-service submodule from 5587c36 to 80e77b6 (23 new commits)
  • Update osac-operator submodule from f4f99a7 to f81b015 (29 new commits)
  • osac-aap already at latest main — no change needed

Notable changes included

  • SecurityGroup provisioning support (completing networking API coverage)
  • Subnet deletion state propagation (MGMT-23637)
  • Networking retry with exponential backoff (MGMT-23624)
  • Organizations API (MGMT-22987)
  • Host/HostPool removal from both services
  • Lease type in private API
  • Leader election, database metrics, and various fixes

Test plan

  • Deploy with updated submodules and verify all networking resources (VirtualNetwork, Subnet, SecurityGroup, NetworkClass) work end-to-end
  • Verify Host/HostPool removal doesn't break existing deployments

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
  • Updated internal service components to their latest versions.

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.

@eranco74

Copy link
Copy Markdown
Contributor Author

@tzumainn tzumainn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yeah - sorry, I should have considered that!

@openshift-ci

openshift-ci Bot commented Apr 13, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eranco74, tzumainn

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants