Skip to content
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

[baremetal & friends] Clean up keepalived script warnings #1911

Merged

Conversation

cybertron
Copy link
Member

Currently we see two ugly messages in the keepalived logs when
starting the service:

WARNING - default user 'keepalived_script' for script execution does
not exist - please create.

and

SECURITY VIOLATION - scripts are being executed but script_security
not enabled.

This patch adds the enable_script_security and script_user options to
our keepalived.conf to suppress those messages.

- Description for the changelog
Add configuration options to clean up keepalived warnings.

Currently we see two ugly messages in the keepalived logs when
starting the service:

WARNING - default user 'keepalived_script' for script execution does
not exist - please create.

and

SECURITY VIOLATION - scripts are being executed but script_security
not enabled.

This patch adds the enable_script_security and script_user options to
our keepalived.conf to suppress those messages.
@kikisdeliveryservice kikisdeliveryservice changed the title Clean up keepalived script warnings [baremetal & friends] Clean up keepalived script warnings Jul 7, 2020
@cybertron
Copy link
Member Author

/cc @mandre @rgolangh @patrickdillon

This should be functionally identical so I'd be shocked if it breaks anything, but it wouldn't be the first time that happened. :-)

@kikisdeliveryservice
Copy link
Contributor

@cybertron as an fyi metal-ipi & scaleup haven't been passing, ovn occasionally passes, so if you don't want to block on them we can skip.

one retest for the road though :)

/retest

@celebdor
Copy link
Contributor

celebdor commented Jul 8, 2020

/lgtm
Thanks. I'll be glad to lose those bothering warnings

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 8, 2020
@cybertron
Copy link
Member Author

@cybertron as an fyi metal-ipi & scaleup haven't been passing, ovn occasionally passes, so if you don't want to block on them we can skip.

There's no rush to get this in. I'm pretty sure these aren't causing any functional problems, they just look ugly in the logs and I wanted to eliminate them as part of the debugging for keepalived 2.0. Once #1909 goes in the metal job should start passing and I can rebase this to pull it in.

@cybertron
Copy link
Member Author

Oh, like the new title too. :-)

@mandre
Copy link
Member

mandre commented Jul 9, 2020

/retest
/test e2e-openstack
/test e2e-ovirt
/test e2e-vsphere

@cybertron
Copy link
Member Author

/test e2e-gcp-upgrade

I'm not seeing a lot of passes for ovirt and vsphere lately, so I doubt their failures are related.

@kikisdeliveryservice
Copy link
Contributor

AFAICT the vpshere job is dead and the ovirt job is semi-dead so those don't have to pass, I can approve and let the bot retest it until it merges for us.. If @mandre also lgtm (the openstack test did pass!)

@kikisdeliveryservice
Copy link
Contributor

/skip

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: celebdor, cybertron, kikisdeliveryservice, mandre

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:
  • OWNERS [kikisdeliveryservice]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kikisdeliveryservice
Copy link
Contributor

Ok approved, let's go baremetal & friends!

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 10, 2020
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 10, 2020

@cybertron: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-ovirt 406392f link /test e2e-ovirt
ci/prow/e2e-vsphere 406392f link /test e2e-vsphere

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.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 1be9c1c into openshift:master Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants