Bug 1070364
| Summary: | foreman: filer foreman server from host list | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Dafna Ron <dron> | ||||
| Component: | foreman | Assignee: | Angus Thomas <athomas> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Ami Jeain <ajeain> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.0 | CC: | dcleal, mburns, rhos-maint, yeylon | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | Installer | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-04-29 15:06:56 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: | |||||||
| Attachments: |
|
||||||
I disagree with arbitrarily filtering it. The only danger is that somebody might decide to reconfigure their Foreman server as an OpenStack host, which won't end well. With a simple change to openstack-foreman-installer, the Puppet agent could be disabled on the Foreman host and so it won't show up. However in the future we're likely to manage the Foreman host through Foreman itself, so it's quite possible this would have to be reverted. It may be best to reject this BZ. This is a low priority issue and we're only fixing critical issues at this point. |
Created attachment 868103 [details] screen shot Description of problem: After installing foreman we can see the foreman server host in the host's list. To avoid any issues and since there is no point in listing the server in the hsots list I suggest filtering it from the view. Version-Release number of selected component (if applicable): foreman-proxy-1.3.0-3.el6sat.noarch How reproducible: 100% Steps to Reproduce: 1. install foreman server for openstack 2. go to hosts in UI 3. Actual results: the server itself is listed under the hosts list Expected results: we should filter it to avoid any issues. Additional info: as you can see in the screen shot, my foreman server dhcp163-108.scl.lab.tlv.redhat.com is shown under the host list [root@dhcp163-108 ~]# rpm -qa |grep foreman foreman-1.3.0.2-1.el6sat.noarch openstack-foreman-installer-1.0.4-1.el6ost.noarch foreman-selinux-1.3.0-1.el6sat.noarch rubygem-foreman_api-0.1.6-1.el6sat.noarch foreman-mysql-1.3.0.2-1.el6sat.noarch foreman-mysql2-1.3.0.2-1.el6sat.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-5.el6ost.noarch foreman-installer-1.3.0-1.el6sat.noarch foreman-proxy-1.3.0-3.el6sat.noarch