Project

General

Profile

Actions

Bug #14234

closed

Cannot connect to qpid denials

Added by Lukas Zapletal over 8 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
Normal
Category:
SElinux
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1185401

Our automation noticed that /var/log/messages contained several errors related to celery not being able to connect to qpid. The symptoms were shown by basically pegging the system and preventing us from connecting to the web UI after a few preliminary tests were run.

Justin has spent some time looking into it and it seems that python processes are not able to read the CA file. Since our automation uses SELinux in enforcing mode, the moment we turned off SELinux the issues disappeared.

Actions #1

Updated by Eric Helms over 8 years ago

  • Translation missing: en.field_release set to 86
Actions #2

Updated by Lukas Zapletal over 8 years ago

  • Status changed from New to Rejected

This was already implemented in pulp:

optional_policy(`
gen_require(`
type celery_t;
')
ifdef(`distro_rhel6', `
miscfiles_manage_cert_files(celery_t)
',`
miscfiles_manage_generic_cert_files(celery_t)
')
')

Actions

Also available in: Atom PDF