Bug 1998300
| Summary: | CNV VMs do not contain the cluster domain name in the FQDN | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Dan Yocum <dyocum> |
| Component: | Networking | Assignee: | oshoval |
| Status: | CLOSED ERRATA | QA Contact: | Adi Zavalkovsky <azavalko> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.6.6 | CC: | azavalko, cnv-qe-bugs, dholler, fdeutsch, phoracek, sgott |
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | virt-operator-container-v4.10.0-195 hco-bundle-registry-container-v4.10.0-597 | Doc Type: | Enhancement |
| Doc Text: |
Feature:
VMs can be now exposed to their FQDN, including the cluster domain name.
Reason:
Without this fix, VMs were only aware of their hostname. That alone in some cases was not enough to identify if the VM runs in development or production clusters.
Result:
If `subdomain` is set on the VMI spec, the VM will be configured with its FQDN, including the domain name.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-16 15:55:26 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: | |||
|
Description
Dan Yocum
2021-08-26 19:14:06 UTC
Verified. OCP Version - 4.10.0-0. CNV Version - 4.10.0. Deployed a VM with a service. [cnv-qe-jenkins@n-****-mhnpv-executor bz1998300]]$ oc expose svc/vmi-cirros -n ad route.route.openshift.io/vmi-cirros exposed [cnv-qe-jenkins@n-****-mhnpv-executor bz1998300]]$ oc get route -n ad NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD vmi-cirros vmi-cirros-ad.apps.n-****.cnv-qe.rhcloud.com vmi-cirros 8000 None Newly deployed route contains clusters FQDN. Bug not verified Thanks Adi working on a fix https://github.com/kubevirt/kubevirt/pull/6964 the subdomain wasn't propagated correctly https://github.com/kubevirt/kubevirt/pull/6964 was merged to upstream Working on another fix: adding the missing subdomain to the right search entry https://github.com/kubevirt/kubevirt/pull/6985 (in order to support custom DNS, and cases in which the node has an additional entries that would be propagated to the pod's resolv.conf) https://github.com/kubevirt/kubevirt/pull/6985 was merged upstream (this was the last pending PR) https://github.com/kubevirt/kubevirt/pull/7033 is the backport of https://github.com/kubevirt/kubevirt/pull/6985 to release-0.49 Verified. OCP version - 4.10. virt-opartor-container-v.4.10.0-196 Deployed a Fedora vm with a headless service. resolv.conf - # Generated by NetworkManager search mysubdomain.***.svc.cluster.local ***.svc.cluster.local svc.cluster.local cluster.local nameserver ***.30.0.10 VM's hostname also modified accordingly [fedora@test-vm ~]$ hostname -f test-vm.mysubdomain.***.svc.cluster.local 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 (Moderate: OpenShift Virtualization 4.10.0 Images security and bug fix update), 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-2022:0947 |