Bug 760892
| Summary: | Config file import fails with PostgreSQL Integrity Error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Mark Round <mark> | ||||
| Component: | Server | Assignee: | Michael Mráka <mmraka> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 1.5 | CC: | slukasik | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | spacewalk-backend-1.6.54-1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-22 16:47:48 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 723481 | ||||||
| Attachments: |
|
||||||
Issue has been fixed in spacewalk master by
commit 447475269def57f0cbd0073d02ca5c167079e67c
760892 - set selinux=None if selinux is disabled
Spacewalk 1.6 has been released. |
Created attachment 541806 [details] Traceback received when importing configuration file. Description of problem: When attempting to import any configuration file from a client, the following error is produced (a full traceback is included below) : IntegrityError: new row for relation "rhnconfiginfo" violates check constraint "vn_rhnconfiginfo_selinux_ctx" SELinux is disabled on the server and client. Version-Release number of selected component (if applicable): 1.5, latest from YUM repository as of 7th December 2011. I have tested with CentOS 5 and 6 clients, the server is running on CentOS 5. All are x86_64 builds. How reproducible: Use the PostgreSQL backend, and attempt to import a configuration file from a client. Actual results: Traceback produced, and "Fatal error in Python code occured [[6]]" displayed in the web UI when viewing the scheduled job status. Expected results: File should be imported correctly. Additional info: See attachment for full traceback email received from the spacewalk server when attempting to import a configuration file (/etc/motd).