Unable to bring the edgehub and edge agent modules as recently IOT hub got updated with DigiCert G2 root from Baltimore root

Question

Hi Team,

Recently IOT hub got updated with DigiCert G2 root from Baltimore root. After the device is not coming up if I try to install new machine also. The ssl certificates which we are generating it was working fine with Baltimore root.

Not sure if any modifications are required.

How i am generating certificates?

Configuration checks
--------------------
√ config.yaml is well-formed - OK
‼ config.yaml has well-formed connection string - Warning
    Device not configured with manual provisioning, in this configuration 'iotedge check' is not able to discover the device's backing IoT Hub.
    To run connectivity checks in this configuration please specify the backing IoT Hub name using --iothub-hostname switch if you have that information.
    If no hostname is provided, all hub connectivity tests will be skipped.
√ container engine is installed and functional - OK
√ config.yaml has correct hostname - OK
× config.yaml has correct URIs for daemon mgmt endpoint - Error
    Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.9.3' locally
    1.0.9.3: Pulling from azureiotedge-diagnostics
    31603596830f: Pulling fs layer
    6e51d6ed8c58: Pulling fs layer
    31603596830f: Verifying Checksum
    31603596830f: Download complete
    31603596830f: Pull complete
    6e51d6ed8c58: Download complete
    6e51d6ed8c58: Pull complete
    Digest: sha256:770251145e61afd6f1bca701a585eb5c79f9b400ad0702956f0219b0bb5cb539
    Status: Downloaded newer image for mcr.microsoft.com/azureiotedge-diagnostics:1.0.9.3
    Error: could not execute list-modules request: an error occurred trying to connect: Connection refused (os error 111)
‼ latest security daemon - Warning
    Installed IoT Edge daemon has version 1.0.9.3 but 1.1.15 is the latest stable version available.
    Please see https://aka.ms/iotedge-update-runtime for update instructions.
√ host time is close to real time - OK
√ container time is close to host time - OK
‼ DNS server - Warning
    Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
    Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
    You can ignore this warning if you are setting DNS server per module in the Edge deployment.
√ production readiness: identity certificates expiry - OK
‼ production readiness: certificates - Warning
    The Edge device is using self-signed automatically-generated development certificates.
    They will expire in 89 days (at 2023-09-12 08:32:54 UTC) causing module-to-module and downstream device communication to fail on an active deployment.
    After the certs have expired, restarting the IoT Edge daemon will trigger it to generate new development certs.
    Please consider using production certificates instead. See https://aka.ms/iotedge-prod-checklist-certs for best practices.
√ production readiness: container engine - OK
‼ production readiness: logs policy - Warning
    Container engine is not configured to rotate module logs which may cause it run out of disk space.
    Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
    You can ignore this warning if you are setting log policy per module in the Edge deployment.
× production readiness: Edge Agent's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeAgent container
× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeHub container

Connectivity checks

sudo iotedge list

[centosjunetest@centosjunetest centosInstall_3c13de2f-0436-4171-89eb-b91667289358-centosjunetest]$ sudo iotedge list
A module runtime error occurred
        caused by: Could not list modules
        caused by: an error occurred trying to connect: Connection refused (os error 111)

[centosjunetest@centosjunetest centosInstall_3c13de2f-0436-4171-89eb-b91667289358-centosjunetest]$
[centosjunetest@centosjunetest centosInstall_3c13de2f-0436-4171-89eb-b91667289358-centosjunetest]$
[centosjunetest@centosjunetest centosInstall_3c13de2f-0436-4171-89eb-b91667289358-centosjunetest]$
[centosjunetest@centosjunetest centosInstall_3c13de2f-0436-4171-89eb-b91667289358-centosjunetest]$ sudo iotedge list
A module runtime error occurred
        caused by: Could not list modules
        caused by: an error occurred trying to connect: Connection refused (os error 111)

[centosjunetest@centosjunetest centosInstall_3c13de2f-0436-4171-89eb-b91667289358-centosjunetest]$ sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
[centosjunetest@centosjunetest centosInstall_3c13de2f-0436-4171-89eb-b91667289358-centosjunetest]$

Let me know if i am missing anything here?

Thanks,
Narendra