-
Notifications
You must be signed in to change notification settings - Fork 1.5k
FIX - OpenMetadata ops bulk deploy via API #24508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Gitar analyzes/fixes CI failures, runs prompts as workflows and addresses comments starting with Rules 1 🎸Gitar Rules🎸 PR Summary Enhancement: Comprehensive technical summary already in PR description ➖ Flaky Test Auto-Retry: Multiple flaky tests detected but all unrelated to PR changes ⚙️ Options:
|
CI failed for e379143: Python 3.12 CI failure is unrelated to PR changes - pyodbc dependency compilation issue with deprecated Python C APIIssueThe Root CauseThe
These deprecated APIs were removed as part of PEP 623. DetailsError excerpt from the build logs: Why This is Unrelated to PR #24508This PR only modifies Java backend code:
No Python dependencies or ingestion code was modified. This is a pre-existing infrastructure issue with Python 3.12 compatibility. Suggested FixThe solution is to upgrade Reply with |
| if (serverUrl == null) { | ||
| throw new RuntimeException("SERVER_HOST_API_URL not configured"); | ||
| } | ||
| LOG.info("Deploying pipelines to server URL: {}", serverUrl); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add details which runner we are deploying to? log it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we have some debugs on HybridServiceClient that we can turn into info to have control on where different ops are landing. that would be on collate repo directly, let me do that on an other ongoing PR
CI failed for dd625fc: Multiple Playwright E2E test failures in AutoPilot feature tests - all unrelated to PR changes which modify Java ingestion pipeline backend code only.IssuePlaywright CI job
Root CauseThese failures are unrelated to the PR changes. The PR modifies:
The failures are in frontend E2E tests testing the AutoPilot UI feature, which is completely separate from the backend Java changes in this PR. The test expectations are hardcoded to expect specific pipeline counts (3 successful pipelines), but the actual UI is showing different counts (4 and 5), indicating either:
DetailsThe test at await expect(
page.getByTestId('agent-status-summary-item-Successful')
.getByTestId('pipeline-count')
).toHaveText('3');But the actual UI shows 4 pipelines on first attempt and 5 on retry, suggesting the test environment has leftover data from other test runs. The Airflow test expects a specific success message that never appears, likely due to timing issues or the AutoPilot agent run not completing within the expected timeframe. Additionally, 3 other tests were marked as flaky (Login, Tag, Users tests), further indicating test infrastructure instability rather than code issues. Suggested FixThe fix should be applied to the test suite, not the PR code:
The PR changes are backend-only and cannot cause frontend E2E test failures in the AutoPilot feature tests. Reply with |
|



Describe your changes:
If we try to execute the deploy-pipelines directly in a hybrid setup, the deploy-pipelines pod in ArgoCD won't have the websocket connection to the hybrid runner to propagate the deployment operations
Fixes #2386, Fixes #2398
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>Summary by Gitar
PipelineServiceClientwebsocket-based deployment with HTTP API calls to/api/v1/services/ingestionPipelines/bulk/deploygetIngestionBotToken()inOpenMetadataOperations.javaretrieves and decrypts ingestion-bot JWT from secrets managerHttpClientwith 30s connect timeout and 2min request timeout for API callsDELETE /{id}/pipelineStatus/{runId}inIngestionPipelineResource.javaremoves specific pipeline status recordsdeleteExtensionByKey()inEntityTimeSeriesDAO.javasupports MySQL and PostgreSQL JSON queries for time-series data deletion