Red Hat Bugzilla – Bug 1124435
Editing host shows an organization/location when none is set on the host
Last modified: 2017-02-23 16:09:48 EST
Description of problem: 2 Issues: 1) menu item 'Hosts -> All hosts ' indicates you have NO hosts when Org / Region set via Org / Location tab despite the server in question having the correct 'Organization' and 'Location' set on the Host->All Hosts->host->Edit tab (which cannot be changed). 2) The Host->All Hosts->host->Properties view for Location and Organization is out of sync with the Location / Organization settings in Host->All Hosts->host->Edit (It is set correctly in the Edit tab (and can't be changed) but blank in the Properties tab).
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
The issues described are actually correct behaviour, but stem from the edit screen (which is used as a point of reference in the description) incorrectly showing an org/loc when none is actually set. It's probably defaulting to the first in the list rather than showing a blank entry.
Connecting redmine issue http://projects.theforeman.org/issues/6832 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/6832 has been closed ------------- Anonymous Applied in changeset commit:65292474dcf224acf68d3b23741548553bf34629.
VERIFIED: # rpm -qa | grep foreman rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch foreman-proxy-1.7.2.3-1.el6_6sat.noarch foreman-ovirt-1.7.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.1-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch ruby193-rubygem-foreman_abrt-0.0.5-2.el6_6sat.noarch foreman-compute-1.7.2.10-1.el6_6sat.noarch foreman-libvirt-1.7.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.6-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.6-1.el6_6sat.noarch foreman-selinux-1.7.2.8-1.el6_6sat.noarch foreman-gce-1.7.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman_docker-1.2.0.3-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.9-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-debug-1.7.2.10-1.el6_6sat.noarch foreman-vmware-1.7.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.8-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch foreman-1.7.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.2-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-postgresql-1.7.2.10-1.el6_6sat.noarch
This bug is slated to be released with Satellite 6.1.
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/RHSA-2015:1592