| Summary: | cfme appliance image on rhv4 (ovirt) defaults eth0 to "rhevm" network. | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | amogh <amavinag> |
| Component: | Build | Assignee: | Satoe Imaishi <simaishi> |
| Status: | CLOSED WONTFIX | QA Contact: | Dave Johnson <dajohnso> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.7.0 | CC: | cpelland, dajohnso, jhardy, jprause, obarenbo |
| Target Milestone: | GA | ||
| Target Release: | cfme-future | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | rhev:appliance:build | ||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Cause: In rhv40, the default management network has changed to "ovirtmgmt" from "rhevm"
Consequence: the appliance vm on rhv4.0, does not get the network/ip automatically assigned.
Workaround (if any): We now provide qcow2 image as well as ova. Using qcow2 image is the current workaround?
Result:
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-02 14:29:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | CFME Core | Target Upstream Version: | |
|
Description
amogh
2016-10-21 05:27:32 UTC
This issue was reported upstream here: https://github.com/ManageIQ/manageiq/issues/358 Imagefactory has the value set to 'rhevm'. Since that option isn't exposed, we're not able to change either. Will check where imagefactory bug is tracked internally. A solution is being discussed... We now provide qcow2 image as well as ova. Although ova image still has this problem, can we lower priority/severity as using qcow2 image will be an easy workaround? Dear customer, The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. If you have any concerns about this, please let us know. Thanks and regards! Dear customer, The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. If you have any concerns about this, please let us know. Thanks and regards! |