OCPBUGS-36483: Fix new added node issue #607
Conversation
openshift-ci-robot
added
jira/severity-moderate
|
@Vincent056: This pull request references Jira Issue OCPBUGS-36483, which is invalid:
Comment 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
approved
/etc/kubernetes/static-pod-resource is being created after a new node is being added, this cause the link count change in the aide checks and resulting a failures. The PR added a init pod to check for that before running aide daemonset.
Vincent056
force-pushed
the
new_fix_node
branch
from
dc35b5a to
b3e8dc5
Compare
|
/label qe-approved |
openshift-ci
bot
added
the
qe-approved
| fi`, | ||
| }, | ||
| SecurityContext: &corev1.SecurityContext{ | ||
| Privileged: &priv, |
There was a problem hiding this comment.
Does this need to be privileged? Or can we reduce the permissions required to run this container?
|
/retest |
|
@Vincent056: The following test failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhmdnd, Vincent056 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 |
I think this fixes the instability of the scaling e2e test @rhmdnd |
|
@Vincent056: Jira Issue OCPBUGS-36483: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-36483 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 openshift-eng/jira-lifecycle-plugin repository. |
/etc/kubernetes/static-pod-resourceis being created after a new node is added, this cause the link count change in the aide checks and resulting a failures. The PR added a init pod to check for that before running aide daemonset.