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

[dev.icinga.com #10773] chcon partial context error in safe-reload prevents reload #3746

Closed
icinga-migration opened this issue Dec 4, 2015 · 8 comments
Labels
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Dec 4, 2015

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10773

Created by mfriedrich on 2015-12-04 13:58:08 +00:00

Assignee: dgoetz
Status: Resolved (closed on 2015-12-07 09:15:04 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 09:58:21 +00:00 (in Redmine)

Icinga Version: 2.4.1
Backport?: Already backported
Include in Changelog: 1

what i also recognizes is that chcon was included to 
/usr/lib/icinga2/safe-reload, which stops the reload with error
Validating config files: chcon: can't apply partial context to unlabeled 
file ‘/tmp/tmp.XJ3IYjLZPz’

i removed chcon and the config the reload was working again

Changesets

2015-12-04 14:28:16 +00:00 by dgoetz 9989596

Only execute chcon if selinux is enabled and use full context

refs #8332
fixes #10773

2015-12-04 14:42:49 +00:00 by dgoetz 0c8395f

Only execute chcon if selinux is enabled and use full context

refs #8332
fixes #10773

2015-12-04 14:49:36 +00:00 by dgoetz 193eff0

Only execute chcon if selinux is enabled and use full context

fixes #10773

2015-12-07 09:13:40 +00:00 by dgoetz c7c3cce

Only execute chcon if selinux is enabled and use full context

fixes #10773

2016-02-23 08:26:25 +00:00 by dgoetz bbfc734

Only execute chcon if selinux is enabled and use full context

fixes #10773
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Dec 4, 2015

Updated by dgoetz on 2015-12-04 14:30:03 +00:00

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

Applied in changeset 9989596.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Dec 4, 2015

Updated by mfriedrich on 2015-12-04 14:38:30 +00:00

  • Status changed from Resolved to Assigned
  • Assigned to set to dgoetz
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Dec 4, 2015

Updated by dgoetz on 2015-12-04 14:45:03 +00:00

  • Status changed from Assigned to Resolved

Applied in changeset 0c8395f.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Dec 7, 2015

Updated by mfriedrich on 2015-12-07 08:37:22 +00:00

  • Status changed from Resolved to Assigned
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Dec 7, 2015

Updated by mfriedrich on 2015-12-07 09:14:01 +00:00

  • Target Version set to 2.5.0
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Dec 7, 2015

Updated by dgoetz on 2015-12-07 09:15:04 +00:00

  • Status changed from Assigned to Resolved

Applied in changeset c7c3cce.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 25, 2016

Updated by mfriedrich on 2016-01-25 10:39:46 +00:00

  • Target Version changed from 2.5.0 to 2.4.2
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 23, 2016

Updated by gbeutner on 2016-02-23 09:58:21 +00:00

  • Backport? changed from Not yet backported to Already backported
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.