Red Hat Bugzilla – Bug 1223987
WebUI: Changing release version in content host errored
Last modified: 2016-07-27 05:15:46 EDT
Created attachment 1028432 [details] production.log error Description of problem: WebUI: Changing release version in content host errored Version-Release number of selected component (if applicable): Sat 6.1 GA Snap 5 How reproducible: Always Steps to Reproduce: 1. Go to Hosts -> Content Host -> Select a Content Host -> Details Tab -> Change Release Version (I changed it from blank to 7Server) Actual results: UI says Save successful but there was an error in production.log Expected results: No errors Additional info:
Suresh, does the change get saved despite the error in the log?
(In reply to Brad Buckingham from comment #3) > Suresh, does the change get saved despite the error in the log? Yes it gets saved.
if this gets saved and is only an error message, not a blocker.
This seems like it's a problem with candlepin? If not please feel free to move back to katello.
This is just a fairly common situation being incorrectly logged as an error when it shouldn't be. Fixed already in candlepin 2.0, I'm not sure when this gets picked up though but I know Tom has been looking into it. In any case an error that is safe to ignore.
VERIFIED: # rpm -qa | grep foreman hp-dl360g7-01.lab.eng.brq.redhat.com-foreman-proxy-1.0-1.noarch foreman-release-1.11.0-0.develop.201511161350git860ef06.el7.noarch foreman-vmware-1.11.0-0.develop.201511161350git860ef06.el7.noarch foreman-debug-1.11.0-0.develop.201511161350git860ef06.el7.noarch foreman-libvirt-1.11.0-0.develop.201511161350git860ef06.el7.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch foreman-postgresql-1.11.0-0.develop.201511161350git860ef06.el7.noarch hp-dl360g7-01.lab.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch foreman-1.11.0-0.develop.201511161350git860ef06.el7.noarch foreman-ovirt-1.11.0-0.develop.201511161350git860ef06.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch foreman-proxy-1.11.0-0.develop.201511161424gitf24be74.el7.noarch foreman-compute-1.11.0-0.develop.201511161350git860ef06.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch hp-dl360g7-01.lab.eng.brq.redhat.com-foreman-client-1.0-1.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201511111650gitdda13df.el7.noarch foreman-gce-1.11.0-0.develop.201511161350git860ef06.el7.noarch foreman-release-scl-1-1.el7.x86_64 tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch steps: 1. Go to Hosts -> Content Host -> Select a Content Host -> Details Tab -> Change Release Version (I changed it from blank to 7Server) No errors in production log
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501