Bug 1186859
| Summary: | compute profile network interfaces do not show libvirt network options | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Shannon Hughes <shughes> |
| Component: | WebUI | Assignee: | Marek Hulan <mhulan> |
| WebUI sub component: | Foreman | QA Contact: | Tazim Kolhar <tkolhar> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | bbuckingham, bkearney, cwelton, djuran, mhulan, ohadlevy, tkolhar |
| Version: | 6.0.7 | Keywords: | Triaged |
| Target Milestone: | Unspecified | ||
| 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 05:22:25 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1115190 | ||
|
Description
Shannon Hughes
2015-01-28 17:35:42 UTC
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. Reproduced in Satellite 6.0.7, it's already fixed in last compose Satellite 6.1.0. This fix was indirect, fixed as part of http://projects.theforeman.org/issues/6857 (commit 1dd18c340e1a43feb3280a8e680324d59ff32b49). Btw another workaround for 6.0.7 is to open compute profile again from the list, so the JS is properly loaded. Since this bug is set to Sat 6.1.0+ and fix is already there, I'm changing this to MODIFIED. please provide verification steps thanks Based on initial comment "when creating a new compute profile for libvirt instances and the network type is changed from Physical Bridge to Virtual NAT, the network dropdown box is not updated with the libvirt virtual network options." 1. Make sure you have libvirt compute resource 2. Navigate to Infrastructure -> Compute profiles 3. Create new profile (give it a name) 4. On next screen select libvirt resource (from step 1) 5. Set network type to be "Virtual (NAT)" 6. verify that Network field below values changed to whatever you have in your libvirt when you change network type (step 5) hope this helps VERIFIED: # rpm -qa | grep foreman foreman-postgresql-1.7.2.15-1.el6_6sat.noarch foreman-ovirt-1.7.2.15-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.3-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.7-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch foreman-1.7.2.15-1.el6_6sat.noarch foreman-gce-1.7.2.15-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-debug-1.7.2.15-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.4-1.el6_6sat.noarch foreman-selinux-1.7.2.13-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch foreman-compute-1.7.2.15-1.el6_6sat.noarch ruby193-rubygem-foreman_docker-1.2.0.7-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.9-1.el6_6sat.noarch foreman-libvirt-1.7.2.15-1.el6_6sat.noarch foreman-proxy-1.7.2.4-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 ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch foreman-vmware-1.7.2.15-1.el6_6sat.noarch Network field below values changes 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 |