Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BACKPORT][v1.6.4][TASK] Install the latest grpc_health_probe at build time #9716

Open
github-actions bot opened this issue Oct 25, 2024 · 1 comment
Open

[BACKPORT][v1.6.4][TASK] Install the latest grpc_health_probe at build time #9716

github-actions bot opened this issue Oct 25, 2024 · 1 comment
Assignees
@c3y1huang
Labels
area/build-package Build & Package related area/security System or volume data access security kind/backport Backport request kind/task General task request to fulfill another primary request priority/0 Must be implement or fixed in this release (managed by PO)
Milestone
v1.6.4

Comments

@github-actions
Copy link

backport #9714
@github-actions github-actions bot added area/build-package Build & Package related area/security System or volume data access security kind/backport Backport request kind/task General task request to fulfill another primary request priority/0 Must be implement or fixed in this release (managed by PO) labels Oct 25, 2024
@github-actions github-actions bot added this to the v1.6.4 milestone Oct 25, 2024
@c3y1huang c3y1huang self-assigned this Oct 28, 2024
This was referenced Oct 28, 2024
Merged
Merged
@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Oct 28, 2024 •
edited by c3y1huang
Loading

Pre Ready-For-Testing Checklist

  • Where is the reproduce steps/test steps documented?
    The reproduce steps/test steps are at:

  • Is there a workaround for the issue? If so, where is it documented?
    The workaround is at:

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at:

  • Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
    The PR is at:

  • Which areas/issues this PR might have potential impacts on?
    Area build
    Issues

  • If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
    The LEP PR is at

  • If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
    The UI issue/PR is at

  • If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
    The documentation issue/PR is at

  • If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)
    The automation skeleton PR is at
    The automation test case PR is at
    The issue of automation test case implementation is at (please create by the template)

  • If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
    The engine automation PR is at

  • If labeled: require/manual-test-plan Has the manual test plan been documented?
    The updated manual test plan is at

  • If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
    The compatibility issue is filed at

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

@c3y1huang c3y1huang

Labels
area/build-package Build & Package related area/security System or volume data access security kind/backport Backport request kind/task General task request to fulfill another primary request priority/0 Must be implement or fixed in this release (managed by PO)
Projects
Longhorn Sprint
Status: Review
Milestone
v1.6.4
Development

No branches or pull requests
2 participants
@c3y1huang @longhorn-io-github-bot