Bug 1394817
| Summary: | It's not possible see Network when creating one new compute profile / libvirt computer resource | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Waldirio M Pinheiro <wpinheir> | ||||||
| Component: | Compute Resources - libvirt | Assignee: | Sebastian Gräßl <sgraessl> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Kedar Bidarkar <kbidarka> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.2.4 | CC: | bbuckingham, dlobatog, jcallaha, kbidarka, mhulan, sjagtap | ||||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||||
| Target Release: | Unused | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| URL: | http://projects.theforeman.org/issues/18468 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-02-21 17:06:43 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: |
|
||||||||
|
Description
Waldirio M Pinheiro
2016-11-14 13:49:22 UTC
Created attachment 1220429 [details]
step by step - video
Created redmine issue http://projects.theforeman.org/issues/18468 from this bug Upstream bug assigned to sgraessl Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18468 has been resolved. This issue is now fixed, tested as per steps mentioned in the initial bug description. Verified with Sat6.3-snap24. Will attach the screenshot shortly Created attachment 1354346 [details]
libvirt networking dropdown
As seen from the screenshot the dropdown is visible at creation time too.
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-2018:0336 |