[release-4.13] OCPBUGS-20219: Correct upgrade for conflict packages. #12472
Conversation
** The yum module was originally having issues with upgrades (conflicts). Yum had a swap but the issues persisted. A custom workaround was used by downloading RPMs. The process worked except for upgrades. It appeared that the evs-vswitchd daemon was not correctly restarting causing lost connections during the upgrade process. The DNF module will use the --allowerasing option to remove and install the package at the same time, avoiding the issue. ** Also noting that there were sometimes issues when the upgrade for openvswitch would upgrade to a package of the same version. This problem has also been tested and works better with the DNF module.
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-19871 has been cloned as Jira Issue OCPBUGS-20219. Will retitle bug to link to clone. 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. |
openshift-ci
bot
changed the title
openshift-ci-robot
added
the
jira/severity-important
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci-robot
added
the
jira/valid-bug
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-20219, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-20219, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
/label cherry-pick-approved |
openshift-ci
bot
added
the
cherry-pick-approved
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: barbacbd, openshift-cherrypick-robot The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/test e2e-aws-workers-rhel8 |
1 similar comment
|
/test e2e-aws-workers-rhel8 |
|
/retest |
|
/label backport-risk-assessed |
openshift-ci
bot
added
the
backport-risk-assessed
|
/test e2e-aws-workers-rhel8 |
|
@gpei I am tempted to skip this test as it doesn't appear the issue is related to openshift ansible or any ansible playbook. However I am hesitant to let it be swept under the rug. Any thoughts? |
|
@barbacbd yeah, I totally understood. I searched around the failing test /test e2e-aws-workers-rhel8 |
|
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-20219: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-20219 has been moved to the MODIFIED state. 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. |
|
/cherry-pick release-4.12 |
|
@gpei: new pull request created: #12473 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. |
This is an automated cherry-pick of #12470
/assign gpei