Bug 1247387
Summary: | Enabling errata email notification without configuring email server breaks syncs, publishing and promotions | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Og Maciel <omaciel> |
Component: | Other | Assignee: | Mike McCune <mmccune> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Tazim Kolhar <tkolhar> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | Unspecified | CC: | chpeters, cwelton, mmccune, tkolhar |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-12 16:05:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Og Maciel
2015-07-27 21:03:08 UTC
Created redmine issue http://projects.theforeman.org/issues/11228 from this bug VERIFIED # rpm -qa | grep foreman foreman-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.1-1.el7sat.noarch foreman-vmware-1.7.2.33-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-postgresql-1.7.2.33-1.el7sat.noarch foreman-debug-1.7.2.33-1.el7sat.noarch foreman-gce-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.18-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.19-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch foreman-proxy-1.7.2.5-1.el7sat.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-ovirt-1.7.2.33-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-compute-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.15.4-1.el7sat.noarch foreman-libvirt-1.7.2.33-1.el7sat.noarch steps: 1. Use the web ui and subscribe the admin user to all available notification emails 2. Create a custom product (or use an existing one) and synchronize it; better yet, use an existing content view and try to publish it the task is successful This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015. |