BZ2149119: Cron job limitation in_MTC 1.7.6 #53871
Conversation
openshift-ci
bot
added
the
size/XS
|
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/23751 |
|
@pranavgaikwad Please review this PR. |
|
LGTM |
|
/label MTC |
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
adellape
added
the
peer-review-in-progress
| @@ -25,3 +25,4 @@ This release has the following known issues: | |||
| * `MigPlan` custom resource does not display a warning when an AWS gp2 PVC has no available space. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1963927[*BZ#1963927*]) | |||
| * Direct and indirect data transfers do not work if the destination storage is a PV that is dynamically provisioned by the AWS Elastic File System (EFS). This is due to limitations of the AWS EFS Container Storage Interface (CSI) driver. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2085097[*BZ#2085097*]) | |||
| * Block storage for IBM Cloud must be in the same availability zone. See the link:https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-faq[IBM FAQ for block storage for virtual private cloud]. | |||
| * MTC 1.7.6 cannot migrate cron jobs from source clusters that support v1beta1 CronJob to OCP 4.12+ clusters, which do not support v1beta1 CronJob. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2149119[*BZ#2149119*]) | |||
There was a problem hiding this comment.
OCP 4.12+
->
{product-title} 4.12 and later
| @@ -25,3 +25,4 @@ This release has the following known issues: | |||
| * `MigPlan` custom resource does not display a warning when an AWS gp2 PVC has no available space. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1963927[*BZ#1963927*]) | |||
| * Direct and indirect data transfers do not work if the destination storage is a PV that is dynamically provisioned by the AWS Elastic File System (EFS). This is due to limitations of the AWS EFS Container Storage Interface (CSI) driver. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2085097[*BZ#2085097*]) | |||
| * Block storage for IBM Cloud must be in the same availability zone. See the link:https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-faq[IBM FAQ for block storage for virtual private cloud]. | |||
| * MTC 1.7.6 cannot migrate cron jobs from source clusters that support v1beta1 CronJob to OCP 4.12+ clusters, which do not support v1beta1 CronJob. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2149119[*BZ#2149119*]) | |||
There was a problem hiding this comment.
There's a mixture of "cron jobs" and "CronJob". You could change them all to lower case "cron job(s)" (no markup) as a general reference, or for the later ones that mention the API version you could do "v1beta1 CronJob objects". See general reference vs object reference in the API object formatting repo guidelines.
You might also consider marking up v1beta1, as I see it often is elsewhere in the repo. E.g., "that support the v1beta1 API version of CronJob objects".
There was a problem hiding this comment.
@adellape Thank you! Please take a look now.
adellape
added
peer-review-done
sbeskin-redhat
force-pushed
the
BZ2149119_CronJob_limitation_in_MTC_176
branch
from
af2b1e8
to
6085034
Compare
|
The This is because your PR targets the If the update in your PR does NOT apply to version 4.13 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
|
@bergerhoffer Can this PR be merged? |
|
@sbeskin-redhat Can you add the 'merge-review-needed' label when you're ready for this to be merged? I can see that there are 4 commits though, so you'll need to squash at least before sending it. Thanks! |
|
The This is because your PR targets the If the update in your PR does NOT apply to version 4.14 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
/remove-lifecycle stale |
openshift-ci
bot
removed
the
lifecycle/stale
sbeskin-redhat
force-pushed
the
BZ2149119_CronJob_limitation_in_MTC_176
branch
from
b035560
to
316e294
Compare
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
mjpytlak
added
merge-review-in-progress
|
@sbeskin-redhat did you get approval from @pranavgaikwad outside of this PR? Looks like we are still waiting on it here. |
|
@mjpytlak |
|
/cherrypick enterprise-4.14 |
|
@mjpytlak: new pull request created: #64386 In response to this:
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/test-infra repository. |
|
/cherrypick enterprise-4.13 |
|
@mjpytlak: new pull request created: #64387 In response to this:
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/test-infra repository. |
|
/cherrypick enterprise-4.12 |
|
@mjpytlak: new pull request created: #64388 In response to this:
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/test-infra repository. |
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2149119
MTC 1.7.6
OCP 4.12+
Preview: https://53871--docspreview.netlify.app/openshift-enterprise/latest/migration_toolkit_for_containers/mtc-release-notes.html#known-issues-1-7_mtc-release-notes