| Summary: | [RFE] hosted-engine deployment should support IPv6 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Tom Gamull <tomg> | ||||||
| Component: | ovirt-hosted-engine-setup | Assignee: | Simone Tiraboschi <stirabos> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Michael Burman <mburman> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 4.0.0 | CC: | apinnick, cshao, danken, huzhao, lsurette, mavital, mburman, qiyuan, sbonazzo, sborella, stirabos, weiwang, yaniwang, ycui | ||||||
| Target Milestone: | ovirt-4.3.0 | Keywords: | FutureFeature | ||||||
| Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ovirt-hosted-engine-setup-2.3.0 | Doc Type: | Enhancement | ||||||
| Doc Text: |
The current release of the self-hosted engine supports deployment with static IPv6.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-05-08 12:32:03 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Bug Depends On: | 1571216, 1618676 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Description
Tom Gamull
2016-09-01 01:45:51 UTC
Created attachment 1196575 [details]
vdsm logs from RHEL7.2 same issue
Verified on - ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch ovirt-ansible-hosted-engine-setup-1.0.11-1.el7ev.noarch 4.3.1.1-0.1.el7 vdsm-4.30.9-1.el7ev.x86_64 using rhvh-4.3.0.5-0.20190225.0+1 and rhvm-appliance-4.3-20190220.2.el7.x86_64 Verified with and over an IPv6 static address only 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/RHEA-2019:1050 |