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
Bug 1803232: Fixed hardcoded ingress VIP password #1380
Bug 1803232: Fixed hardcoded ingress VIP password #1380
Conversation
/retest |
I'm not very familiar with keepalived; only skimmed some of the docs. But we're just changing from a truly hardcoded password to one that is easily guessable. Is it expected that in practice vrrpd is on a trusted network or something? |
/assign yboaron |
/lgtm |
/test e2e-openstack |
/lgtm |
/retest |
/lgtm |
/assign kikisdeliveryservice |
we need a BZ for this /hold |
/skip |
/retitle Bug 1803232: Fixed hardcoded ingress VIP password |
@e-minguez: This pull request references Bugzilla bug 1803232, which is valid. The bug has been moved to the POST 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. |
/approve |
ty @celebdor ! /approve |
/retest Please review the full test history for this PR and help us cut down flakes. |
13 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
Is there any way to skip unrelated tests? |
e2e-gcp-op failure could be related to #1545 (comment) |
/retest Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
@e-minguez: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
@e-minguez: All pull requests linked via external trackers have merged. Bugzilla bug 1803232 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. |
@runcom: new pull request created: #1550 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. |
Fixes #1379
- What I did
The current keepalived ingress VIP password is hardcoded so I've changed to follow the other VIP passwords.
- How to verify it
Deploy a cluster and observe the
/etc/keepalived/keepalived.conf
file- Description for the changelog
Fixed hardcoded ingress VIP password