-
Notifications
You must be signed in to change notification settings - Fork 463
configure-ovs: improvements & reset openvswitch configuration on every boot #2864
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.
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
configure-ovs: improvements & reset openvswitch configuration on every boot #2864
Conversation
ec013db to
c45196d
Compare
|
/assign @trozet PTAL |
|
@sinnykumari: GitHub didn't allow me to assign the following users: PTAL. Note that only openshift members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. DetailsIn 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. |
a7e4801 to
f097b0e
Compare
f097b0e to
8268322
Compare
addd92d to
d44d021
Compare
|
/retest |
|
/test ? |
|
@jcaamano: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
DetailsIn 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. |
|
/test e2e-metal-ipi-ovn-dualstack |
7e3520f to
ea612ff
Compare
* On error, clean up any configuration to avoid interference. This configuration will be saved on a temporary directory for troubleshooting. * Consolidated logic to rollback any applied configuration, to activate a connection profile, reload NM, print network state information and exit handling. * Avoid using `nmcli device connect` as it will generate a persistent connection profile if there wasn't any, ipossibly changing the state the node was initially deployed with. Signed-off-by: Jaime Caamaño Ruiz <[email protected]>
Signed-off-by: Jaime Caamaño Ruiz <[email protected]>
ea612ff to
9e3e74d
Compare
trozet
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
/assign @kikisdeliveryservice |
|
/retest |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@jcaamano: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
8 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/skip |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
Improvements for configure-ovs script
configuration will be saved on a temporary directory for
troubleshooting.
a connection profile, reload NM, print network state information and
exit handling.
nmcli device connectas it will generate a persistentconnection profile if there wasn't any, ipossibly changing the state
the node was initially deployed with.
configure-ovsto rebuild the ovs configuration on every boot.This allows to take in new network configuration that administrator
intends to apply to the cluster on day-2.
Signed-off-by: Jaime Caamaño Ruiz [email protected]