-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.14
-
Important
-
No
-
3
-
Sprint 245 - OSIntegration, Sprint 246 - OSIntegration, 248 - Integration & Delivery, 249 - Integration & Delivery, 250 - Integration & Delivery, 251 - Integration & Delivery
-
6
-
False
-
Description of problem:
Running KubeVirt VM with fcos/rhcos that do not receive their hostname over DHCP do not present VM name as hostname as expected from configuration at meta_data.json
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Always
Steps to Reproduce:
1. Populate the following vm --- apiVersion: k8s.cni.cncf.io/v1 kind: NetworkAttachmentDefinition metadata: name: bridge-network annotations: k8s.v1.cni.cncf.io/resourceName: bridge.network.kubevirt.io/br0 spec: config: > { "cniVersion": "0.3.1", "name": "br0-l2", "plugins": [{ "type": "bridge", "bridge": "br0", "ipam": {} }] } --- apiVersion: kubevirt.io/v1 kind: VirtualMachineInstance metadata: name: worker1 spec: architecture: amd64 domain: devices: disks: - disk: bus: virtio name: containerdisk - disk: bus: virtio name: cloudinitdisk interfaces: - bridge: {} name: multus rng: {} machine: type: q35 resources: requests: memory: 512Mi networks: - multus: networkName: bridge-network name: multus terminationGracePeriodSeconds: 5 volumes: - containerDisk: image: quay.io/fedora/fedora-coreos-kubevirt:stable name: containerdisk - cloudInitConfigDrive: userData: '{"ignition":{"version":"3.3.0"},"passwd":{"users":[{"name":"core","passwordHash":"$y$j9T$b7RFf2LW7MUOiF4RyLHKA0$T.Ap/uzmg8zrTcUNXyXvBvT26UgkC6zZUVg3UKXeEp5"}]}}' name: cloudinitdisk
Actual results:
Hostname is no set
Expected results:
Hostname should be set since KubeVirt is configuring it at meta_data.json
Additional info:
- account is impacted by
-
CNV-33668 Configure hosted cluster nodes hostnames over the secondary network
- Closed
- is blocked by
-
OCPBUGS-23473 [4.15] Bootimage bump tracker
- Closed