Skip to content

Conversation

@mike-nguyen
Copy link
Member

@mike-nguyen mike-nguyen commented Jan 22, 2025

The changes done here will update the RHCOS 4.19 bootimage metadata. Notable changes in the boot image are:

COS-3014 - Move OpenShift installer to use pure RHEL bootimages

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json                \
    --distro rhcos --no-signatures --name rhel-9.6                    \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=9.6.20250121-0                                     \
    aarch64=9.6.20250121-0                                     \
    s390x=9.6.20250121-0                                       \
    ppc64le=9.6.20250121-0

The changes done here will update the RHCOS 4.19 bootimage metadata.
Notable changes in the boot image are:

COS-3014 - Move OpenShift installer to use pure RHEL bootimages

This change was generated using:
```
plume cosa2stream --target data/data/coreos/rhcos.json                \
    --distro rhcos --no-signatures --name rhel-9.6                    \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=9.6.20250121-0                                     \
    aarch64=9.6.20250121-0                                     \
    s390x=9.6.20250121-0                                       \
    ppc64le=9.6.20250121-0
```
@openshift-ci-robot openshift-ci-robot added 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. labels Jan 22, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 22, 2025

@mike-nguyen: This pull request references Jira Issue OCPBUGS-46549, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @aaradhak

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

The changes done here will update the RHCOS 4.19 bootimage metadata. Notable changes in the boot image are:

COS-3014 - Move OpenShift installer to use pure RHEL bootimages

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json                \
   --distro rhcos --no-signatures --name rhel-9.6                    \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=9.6.20250121-0                                     \
   aarch64=9.6.20250121-0                                     \
   s390x=9.6.20250121-0                                       \
   ppc64le=9.6.20250121-0

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 added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 22, 2025
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-46549, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @aaradhak

Details

In response to this:

The changes done here will update the RHCOS 4.19 bootimage metadata. Notable changes in the boot image are:

COS-3014 - Move OpenShift installer to use pure RHEL bootimages

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json                \
   --distro rhcos --no-signatures --name rhel-9.6                    \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=9.6.20250121-0                                     \
   aarch64=9.6.20250121-0                                     \
   s390x=9.6.20250121-0                                       \
   ppc64le=9.6.20250121-0

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 a review from aaradhak January 22, 2025 20:31
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from mike-nguyen. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@jlebon
Copy link
Member

jlebon commented Jan 23, 2025

/retest

@mike-nguyen
Copy link
Member Author

/test e2e-vsphere-host-groups-ovn-custom-no-upgrade

@sdodson
Copy link
Member

sdodson commented Jan 23, 2025

/payload 4.19 nightly blocking

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

@sdodson: trigger 14 job(s) of type blocking for the nightly release of OCP 4.19

  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.19-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-nightly-4.19-fips-payload-scan
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-ipv6
  • periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-ovn-ocp-conformance
  • periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-ovn-ocp-conformance-serial
  • periodic-ci-openshift-release-master-nightly-4.19-e2e-rosa-sts-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0c9d02c0-d98c-11ef-973d-dc1b3c734917-0

@jlebon
Copy link
Member

jlebon commented Jan 23, 2025

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

@jlebon: The following commands are available to trigger required jobs:

/test altinfra-images
/test aro-unit
/test artifacts-images
/test e2e-agent-compact-ipv4
/test e2e-aws-ovn
/test e2e-aws-ovn-edge-zones-manifest-validation
/test e2e-aws-ovn-upi
/test e2e-azure-ovn
/test e2e-azure-ovn-upi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upi
/test e2e-metal-ipi-ovn-ipv6
/test e2e-openstack-ovn
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test gofmt
/test golint
/test govet
/test images
/test integration-tests
/test integration-tests-nodejoiner
/test okd-scos-images
/test openstack-manifests
/test terraform-images
/test terraform-verify-vendor
/test unit
/test verify-codegen
/test verify-vendor

The following commands are available to trigger optional jobs:

/test altinfra-e2e-aws-custom-security-groups
/test altinfra-e2e-aws-ovn
/test altinfra-e2e-aws-ovn-fips
/test altinfra-e2e-aws-ovn-imdsv2
/test altinfra-e2e-aws-ovn-localzones
/test altinfra-e2e-aws-ovn-proxy
/test altinfra-e2e-aws-ovn-shared-vpc
/test altinfra-e2e-aws-ovn-shared-vpc-local-zones
/test altinfra-e2e-aws-ovn-shared-vpc-wavelength-zones
/test altinfra-e2e-aws-ovn-single-node
/test altinfra-e2e-aws-ovn-wavelengthzones
/test altinfra-e2e-azure-capi-ovn
/test altinfra-e2e-azure-ovn-shared-vpc
/test altinfra-e2e-gcp-capi-ovn
/test altinfra-e2e-gcp-ovn-byo-network-capi
/test altinfra-e2e-gcp-ovn-secureboot-capi
/test altinfra-e2e-gcp-ovn-xpn-capi
/test altinfra-e2e-ibmcloud-capi-ovn
/test altinfra-e2e-nutanix-capi-ovn
/test altinfra-e2e-openstack-capi-ccpmso
/test altinfra-e2e-openstack-capi-ccpmso-zone
/test altinfra-e2e-openstack-capi-dualstack
/test altinfra-e2e-openstack-capi-dualstack-upi
/test altinfra-e2e-openstack-capi-dualstack-v6primary
/test altinfra-e2e-openstack-capi-externallb
/test altinfra-e2e-openstack-capi-nfv-intel
/test altinfra-e2e-openstack-capi-ovn
/test altinfra-e2e-openstack-capi-proxy
/test altinfra-e2e-vsphere-capi-multi-vcenter-ovn
/test altinfra-e2e-vsphere-capi-ovn
/test altinfra-e2e-vsphere-capi-static-ovn
/test altinfra-e2e-vsphere-capi-zones
/test azure-ovn-marketplace-images
/test e2e-agent-4control-ipv4
/test e2e-agent-5control-ipv4
/test e2e-agent-compact-ipv4-appliance-diskimage
/test e2e-agent-compact-ipv4-none-platform
/test e2e-agent-compact-ipv6-minimaliso
/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv4-pxe
/test e2e-agent-sno-ipv6
/test e2e-aws-default-config
/test e2e-aws-overlay-mtu-ovn-1200
/test e2e-aws-ovn-custom-iam-profile
/test e2e-aws-ovn-edge-zones
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-heterogeneous
/test e2e-aws-ovn-imdsv2
/test e2e-aws-ovn-proxy
/test e2e-aws-ovn-public-ipv4-pool
/test e2e-aws-ovn-public-ipv4-pool-disabled
/test e2e-aws-ovn-public-subnets
/test e2e-aws-ovn-shared-vpc-custom-security-groups
/test e2e-aws-ovn-shared-vpc-edge-zones
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-techpreview
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-user-provisioned-dns
/test e2e-aws-ovn-workers-rhel8
/test e2e-aws-upi-proxy
/test e2e-azure-default-config
/test e2e-azure-ovn-resourcegroup
/test e2e-azure-ovn-shared-vpc
/test e2e-azure-ovn-techpreview
/test e2e-azurestack
/test e2e-azurestack-upi
/test e2e-crc
/test e2e-external-aws
/test e2e-external-aws-ccm
/test e2e-gcp-default-config
/test e2e-gcp-ovn-byo-vpc
/test e2e-gcp-ovn-heterogeneous
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-xpn
/test e2e-gcp-secureboot
/test e2e-gcp-upgrade
/test e2e-gcp-upi-xpn
/test e2e-gcp-user-provisioned-dns
/test e2e-ibmcloud-ovn
/test e2e-metal-assisted
/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-swapped-hosts
/test e2e-metal-ipi-ovn-virtualmedia
/test e2e-metal-single-node-live-iso
/test e2e-nutanix-ovn
/test e2e-openstack-ccpmso
/test e2e-openstack-ccpmso-zone
/test e2e-openstack-dualstack
/test e2e-openstack-dualstack-upi
/test e2e-openstack-externallb
/test e2e-openstack-nfv-intel
/test e2e-openstack-proxy
/test e2e-openstack-singlestackv6
/test e2e-powervs-capi-ovn
/test e2e-vsphere-host-groups-ovn-custom-no-upgrade
/test e2e-vsphere-multi-vcenter-ovn
/test e2e-vsphere-ovn-multi-network
/test e2e-vsphere-ovn-techpreview
/test e2e-vsphere-ovn-upi-zones
/test e2e-vsphere-ovn-zones
/test e2e-vsphere-ovn-zones-techpreview
/test e2e-vsphere-static-ovn
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-installer-main-altinfra-images
pull-ci-openshift-installer-main-aro-unit
pull-ci-openshift-installer-main-artifacts-images
pull-ci-openshift-installer-main-e2e-aws-ovn
pull-ci-openshift-installer-main-e2e-azure-ovn-resourcegroup
pull-ci-openshift-installer-main-e2e-openstack-ovn
pull-ci-openshift-installer-main-e2e-vsphere-host-groups-ovn-custom-no-upgrade
pull-ci-openshift-installer-main-e2e-vsphere-ovn-multi-network
pull-ci-openshift-installer-main-e2e-vsphere-static-ovn
pull-ci-openshift-installer-main-gofmt
pull-ci-openshift-installer-main-golint
pull-ci-openshift-installer-main-govet
pull-ci-openshift-installer-main-images
pull-ci-openshift-installer-main-okd-scos-e2e-aws-ovn
pull-ci-openshift-installer-main-okd-scos-images
pull-ci-openshift-installer-main-terraform-images
pull-ci-openshift-installer-main-unit
pull-ci-openshift-installer-main-verify-codegen
pull-ci-openshift-installer-main-verify-vendor
Details

In response to this:

/test ?

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 kubernetes-sigs/prow repository.

@sdodson
Copy link
Member

sdodson commented Jan 23, 2025

/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-virtualmedia

@jlebon
Copy link
Member

jlebon commented Jan 23, 2025

/test e2e-agent-compact-ipv4

@andfasano
Copy link
Contributor

/retest-required

@sdodson
Copy link
Member

sdodson commented Jan 24, 2025

/test e2e-metal-ipi-ovn
/test e2e-agent-compact-ipv4
both seemed to fail on upi image builds, unlikely related to this change

@jlebon
Copy link
Member

jlebon commented Jan 24, 2025

Just to surface some investigations on this, I think both those tests (e2e-metal-ipi-ovn and e2e-agent-compact-ipv4) anyway are not testing the right thing. They get their bootimages from https://github.com/openshift/machine-os-images.

So ideally, CI would also rebuild machine-os-images on top of this PR (machine-os-images is built FROM the installer image) and then launch tests with a release payload containing both of those.

Anyway, we did verify ABI quite recently as part of openshift/assisted-installer#899. I didn't test bare metal IPI manually but I also don't expect any issues there based on my understanding. With respect to the node overlay work, the bootstrapping flow is like any other cloud platform compared to ABI.

@andfasano
Copy link
Contributor

andfasano commented Jan 27, 2025

Just to surface some investigations on this, I think both those tests (e2e-metal-ipi-ovn and e2e-agent-compact-ipv4) anyway are not testing the right thing. They get their bootimages from https://github.com/openshift/machine-os-images.

That's right (at least for the compact ABI job). Just as a double-check, this behavior can be observed in the logs

...
2025-01-24 15:40:44 level=info msg=Extracting base ISO from release payload
2025-01-24 15:40:44 level=debug msg=Fetching image from OCP release ([oc adm release info --image-for=machine-os-images --filter-by-os=linux/amd64 --insecure=true registry.build05.ci.openshift.org/ci-op-g6q1xrv5/release@sha256:fbe4abe64fbc83e841a2d33b29504f59630026d5b2a9e0bf3f6870fffbbe8550])
...

So ideally, CI would also rebuild machine-os-images on top of this PR (machine-os-images is built FROM the installer image) and then launch tests with a release payload containing both of those.

Yeah, unfortunately right now the machine-os-images is usually rebuilt on nightlies (or by forcing a dummy commit)

@andfasano
Copy link
Contributor

andfasano commented Jan 27, 2025

/test e2e-agent-sno-ipv6

Kicking off the sno job (since due its current configuration shouldn't fetch the base ISO from the release payload)
I was wrong, using same approach. In the log we also report the mismatch:

...
base ISO version mismatch in release payload. Expected version 9.6.20250121-0 but found 418.94.202410090804-0
...

@sdodson
Copy link
Member

sdodson commented Jan 28, 2025 via email

jlebon added a commit to jlebon/machine-os-images that referenced this pull request Jan 29, 2025
@jlebon
Copy link
Member

jlebon commented Jan 29, 2025

Would a machine-os-images dummy commit and the multi pr test be sufficient to cause those jobs to use these new boot images?

Hmm, I don't think so but let's give it a try!

/testwith openshift/installer/release-4.19/e2e-metal-ipi-ovn openshift/machine-os-images#50

@smg247
Copy link
Member

smg247 commented Jan 29, 2025

/testwith openshift/installer/release-4.19/e2e-metal-ipi-ovn openshift/machine-os-images#50

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 29, 2025

@smg247, testwith: could not generate prow job. ERROR:

no ref for requested test included in command

@smg247
Copy link
Member

smg247 commented Jan 29, 2025

/testwith openshift/installer/main/e2e-metal-ipi-ovn openshift/machine-os-images#50

@sdodson
Copy link
Member

sdodson commented Jan 30, 2025

/test e2e-aws-ovn e2e-gcp-ovn e2e-vsphere-static-ovn e2e-gcp-ovn

@sdodson
Copy link
Member

sdodson commented Jan 30, 2025

/payload-job periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-upgrade-out-of-change periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-upgrade-out-of-change

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2025

@sdodson: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-upgrade-out-of-change
  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-upgrade-out-of-change

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2c3ba970-df2b-11ef-9a02-87a4267de47a-0

@sdodson
Copy link
Member

sdodson commented Jan 30, 2025

/tide refresh

@sdodson
Copy link
Member

sdodson commented Jan 30, 2025

/label acknowledge-critical-fixes-only
/lgtm
/label approved

@openshift-ci openshift-ci bot added acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 30, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 1e5a97e and 2 for PR HEAD 194cc06 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 1c141f0 and 1 for PR HEAD 194cc06 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@mike-nguyen: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-vsphere-host-groups-ovn-custom-no-upgrade 194cc06 link false /test e2e-vsphere-host-groups-ovn-custom-no-upgrade

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jlebon
Copy link
Member

jlebon commented Jan 31, 2025

/retest-required

@sdodson
Copy link
Member

sdodson commented Jan 31, 2025

/override ci/prow/artifacts-images ci/prow/okd-scos-images
Those all passed last time around

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/artifacts-images, ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/artifacts-images ci/prow/okd-scos-images
Those all passed last time around

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 kubernetes-sigs/prow repository.

@sdodson
Copy link
Member

sdodson commented Jan 31, 2025

/tide refresh

@sdodson
Copy link
Member

sdodson commented Jan 31, 2025

/override ci/prow/e2e-openstack-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2025

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-openstack-ovn

Details

In response to this:

/override ci/prow/e2e-openstack-ovn

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 kubernetes-sigs/prow repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 752124e into openshift:main Jan 31, 2025
24 of 26 checks passed
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: Jira Issue OCPBUGS-46549: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-46549 has been moved to the MODIFIED state.

Details

In response to this:

The changes done here will update the RHCOS 4.19 bootimage metadata. Notable changes in the boot image are:

COS-3014 - Move OpenShift installer to use pure RHEL bootimages

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json                \
   --distro rhcos --no-signatures --name rhel-9.6                    \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=9.6.20250121-0                                     \
   aarch64=9.6.20250121-0                                     \
   s390x=9.6.20250121-0                                       \
   ppc64le=9.6.20250121-0

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.19.0-202501311906.p0.g752124e.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.19.0-202501311906.p0.g752124e.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.19.0-202501311906.p0.g752124e.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.19.0-202501311906.p0.g752124e.assembly.stream.el9.
All builds following this will include this PR.

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

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants