Project

Profile

Help

Bug #6309

Check turn off SElinux on centos boxes

Added by Kirill Yudenok over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Kirill Yudenok
Category:
-
Sprint/Milestone:
Start date:
04.06.2015
Due date:
26.11.2015
% Done:

100%

Estimated time:
Target branch:
Test scenario:

Description

- for centos needed to turn off selinux and if it already turned off - recipes failed!
- check if selinux already turned off

History

#1 Updated by Kirill Krinkin about 5 years ago

  • Sprint/Milestone set to backlog

#2 Updated by Kirill Yudenok almost 5 years ago

  • Due date set to 26.11.2015
  • Status changed from New to Assigned
  • Assignee set to Kirill Yudenok
  • Sprint/Milestone changed from backlog to 0.6

#3 Updated by Kirill Yudenok almost 5 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

- branch: 6503_docker_setup

#4 Updated by Timofey Turenko almost 5 years ago

  • Status changed from Resolved to Reopened

I guess it should not be in 6503_docker_setup!
Even if it was found only for Docker case, SELinux issue can be a general issue for all providers.
Reopening, please create separate branch and pull request

#5 Updated by Kirill Krinkin over 4 years ago

  • Sprint/Milestone changed from 0.6 to 0.82

#6 Updated by Kirill Krinkin over 4 years ago

  • Sprint/Milestone changed from 0.82 to 0.83

#7 Updated by Kirill Krinkin over 4 years ago

  • Sprint/Milestone changed from 0.83 to 0.82

#8 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Reopened to Active / In progress

#9 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Active / In progress to Ask for information
  • Assignee changed from Kirill Yudenok to Timofey Turenko
  • SElinux turn off code already in galera, mariadb, maxscale recipes of integration branch
  • It is necessary to move it to a separate branch?
  • I will test it again

#10 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Ask for information to Resolved
  • Assignee changed from Timofey Turenko to Kirill Yudenok
  • already in integration and tested

#11 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF