Skip to content

Pull requests: openshift/assisted-service

New pull request New
30 Open 7,237 Closed
30 Open 7,237 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

NO-ISSUE: [release-ocm-2.10] Bump OCP versions: 4.15, 4.12, 4.13 approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
#7330 opened Feb 18, 2025 by danmanor Loading…
@gamli75
7
NO-ISSUE: [master] Bump OCP versions: 4.18, 4.19 approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
#7326 opened Feb 18, 2025 by danmanor Loading…
@gamli75
9
MGMT-19939: Allow using the rootfs install method to add nodes approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
#7325 opened Feb 17, 2025 by carbonin Loading…
9 of 20 tasks
@carbonin @rccrdpccl
10
[release-ocm-2.10] MGMT-19857: Validate that no_proxy does not contain duplicate entries approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
#7323 opened Feb 17, 2025 by openshift-cherrypick-robot Loading…
@carbonin @gamli75
7
[release-ocm-2.11] MGMT-19856: Validate that no_proxy does not contain duplicate entries approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
#7322 opened Feb 17, 2025 by openshift-cherrypick-robot Loading…
@carbonin @gamli75
11
OCPEDGE-1311: add two node openshift deployment api-review Categorizes an issue or PR as actively needing an API review. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
#7321 opened Feb 17, 2025 by qJkee Loading…
5 of 20 tasks
@carbonin
8
MGMT-19622: Proxy setting with special characters are ignored when minimal ISO is used jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
#7315 opened Feb 16, 2025 by dudyas6 Loading…
7 of 20 tasks
12
Aanatl mgmt 19423 api-review Categorizes an issue or PR as actively needing an API review. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
#7312 opened Feb 14, 2025 by andrej1991 • Draft
4 of 20 tasks
3
MGMT-19887: Add Histogram Metric for Host Monitoring Time do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
#7307 opened Feb 13, 2025 by rivkyrizel • Draft
2 of 20 tasks
20
[release-ocm-2.11] ACM-16099: Bump moby/moby version to close CVE-2024-36620 api-review Categorizes an issue or PR as actively needing an API review. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
#7294 opened Feb 8, 2025 by omer-vishlitzky Loading…
2 of 20 tasks
9
MGMT-19840: Gather operational metrics from installercache approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
#7281 opened Feb 6, 2025 by paul-maidment Loading…
2 of 20 tasks
17
MGMT-19830: Enable installation of OCP clusters in vSphere environments with user-managed LB approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
#7272 opened Feb 4, 2025 by danmanor • Draft
9 of 20 tasks
14
MGMT-19773: block forbidden hostname do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
#7270 opened Feb 4, 2025 by zszabo-rh • Draft
8 of 20 tasks
3
[release-4.18] OCPBUGS-49743: dnsmasq service on OCP SNO fails to read /etc/resolv.conf file during system startup approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
#7257 opened Feb 2, 2025 by openshift-cherrypick-robot Loading…
@adriengentil @mlorenzofr @gamli75
5
Red Hat Konflux update assisted-service-rhel9-acm-ds-main do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
#7240 opened Jan 29, 2025 by red-hat-konflux bot Loading…
4
Red Hat Konflux update assisted-service-rhel8-acm-ds-main do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
#7239 opened Jan 29, 2025 by red-hat-konflux bot Loading…
4
WIP: NO-JIRA: Validate the CPU architectures set by users in the CRs api-review Categorizes an issue or PR as actively needing an API review. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
#7224 opened Jan 24, 2025 by aleskandro Loading…
5
NO-ISSUE: Add OpenShift AI AMD operator bundle api-review Categorizes an issue or PR as actively needing an API review. approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
#7222 opened Jan 23, 2025 by jhernand Loading…
8 of 20 tasks
7
MGMT-19148: Revert add OLM operator setup jobs finalizing stage (#6933)" api-review Categorizes an issue or PR as actively needing an API review. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
#7219 opened Jan 23, 2025 by jhernand Loading…
5 of 20 tasks
7
[WIP] Feature support dep1 approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
#7216 opened Jan 22, 2025 by eifrach • Draft
2 of 20 tasks
6
OCPBUGS-45244: Bump moby from v26.0.0 to v27.2.1 approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
#7189 opened Jan 14, 2025 by jkaurredhat Loading…
2 of 20 tasks
@gamli75
3
NO-ISSUE: Update Konflux references approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. konflux size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
#7176 opened Jan 11, 2025 by red-hat-konflux bot Loading…
1 task
6
OCPBUGS-46184: Bump golang.org/x/crypto to 0.31.0 backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
#7110 opened Dec 17, 2024 by jkaurredhat Loading…
2 of 20 tasks
5
OCPBUGS-46188: Update crypto to 0.31 backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
#7107 opened Dec 17, 2024 by jkaurredhat Loading…
2 of 20 tasks
@paul-maidment
13
MGMT-18230: Bump to go version 1.22 approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/dependency-change Categorizes issue or PR as related to changing dependencies size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
#7011 opened Nov 19, 2024 by paul-maidment • Draft
2 of 20 tasks
@adriengentil
9
ProTip! Follow long discussions with comments:>50.