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.

Sign up for GitHub

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

Jump to bottom

[bashible] remove selinux enable step #709

Merged
merged 1 commit into from
Jan 31, 2022
Merged

[bashible] remove selinux enable step #709

merged 1 commit into from
Jan 31, 2022

Conversation

RomanenkoDenys
Copy link
Member

@RomanenkoDenys RomanenkoDenys commented Jan 31, 2022 •
edited by z9r5

Description

Remove selinux enable step.

Why do we need it, and what problem does it solve?

If Selinux is disabled on node, step fails.

Changelog entries

module: bashible
type: fix
description:  "Remove SELinux enabling step."

@konstantin-axenov konstantin-axenov changed the base branch from main to release-1.30 January 31, 2022 15:35
@konstantin-axenov konstantin-axenov added this to the v1.30.3 milestone Jan 31, 2022
@konstantin-axenov
Copy link
Member

konstantin-axenov commented Jan 31, 2022 •
edited

This is already fixed in main by #542, but can't be back ported.

@konstantin-axenov konstantin-axenov added the skip/documentation-validation Skip documentation validation in pull request label Jan 31, 2022
@konstantin-axenov konstantin-axenov merged commit 660e318 into release-1.30 Jan 31, 2022
@konstantin-axenov konstantin-axenov deleted the fix-selinux branch January 31, 2022 19:59
@deckhouse-BOaTswain deckhouse-BOaTswain mentioned this pull request Jan 31, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@konstantin-axenov konstantin-axenov konstantin-axenov approved these changes

Assignees
No one assigned
Labels
skip/documentation-validation Skip documentation validation in pull request type/bug
Projects
None yet
Milestone
v1.30.3
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@RomanenkoDenys @konstantin-axenov