+++ This bug was initially created as a clone of Bug #1965026 +++

Description of problem:
Installation using CRs with dual stack fails to present persistent IPv6 DHCP requests. 

Version-Release number of selected component (if applicable):
4.8

How reproducible:
Every time


Steps to Reproduce:
1. Create dual stack deployment CR
Define CR for dual stack deployment:

apiVersion: extensions.hive.openshift.io/v1beta1
kind: AgentClusterInstall
metadata:
  name: dual-ocp-aci 
  namespace: assisted-installer
  annotations: {"agent-install.openshift.io/install-config-overrides": "{\"networking\": {\"networkType\": \"OVNKubernetes\", \"machineNetwork\": [{\"cidr\": \"10.19.32.192/26\"}, {\"cidr\": \"2620:52:0:1343::/64\"}], \"clusterNetwork\": [{\"cidr\": \"10.128.0.0/14\", \"hostPrefix\": 23}, {\"cidr\": \"fd01::/48\", \"hostPrefix\": 64}], \"serviceNetwork\": [\"172.30.0.0/16\", \"fd02::/112\"]}}"}
spec:
  clusterDeploymentRef:
    name: dual-ocp-sno
  imageSetRef:
    name: openshift-4.8 
  networking:
    clusterNetwork:
      - cidr: "10.128.0.0/14" 
        hostPrefix: 23
    serviceNetwork:
      - "172.30.0.0/16"
    machineNetwork:
      - cidr: "10.19.32.192/26"


2. Deploy cluster. Look for 

ipv6.dhcp-duid=ll

Here:
https://github.com/openshift/assisted-service/blob/7dac3fb956cc7c477cf79aa024ba4813ac85000e/internal/ignition/ignition.go#L809

AI should parse and return when an IPv6 address is found. 

https://github.com/openshift/assisted-service/blame/902a54d507dc4661d0ca2977114dc8500f52ee05/internal/network/utils.go#L22-L26


Actual results:
DHCPv6 sends IP address via DUID that includes timestamp and will change. 

Expected results:
DHCPv6 sends IP address via MAC address that will not change and can be reserved. 

Additional info:
Can provide kubeconfig for dual stack install if need be.

--- Additional comment from Ronnie Lazar on 2021-05-26 15:33:44 UTC ---

Currently we do not support dual stack.
We will add support for it for 4.9

--- Additional comment from Ronnie Lazar on 2021-05-26 15:35:53 UTC ---

Will be handled as part of https://issues.redhat.com/browse/MGMT-6670