[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eGoogle Distributed Cloud air-gapped 1.9.10 has been released, offering enhanced features as detailed in the product overview.\u003c/p\u003e\n"],["\u003cp\u003eThe update includes the Canonical Ubuntu OS image version 20240114, which addresses numerous security vulnerabilities and requires all nodes to be upgraded.\u003c/p\u003e\n"],["\u003cp\u003eMultiple security vulnerabilities have been patched in both the OS image and container images within this release, improving overall system security.\u003c/p\u003e\n"],["\u003cp\u003eThe release also fixes specific issues, such as Grafana displaying an empty \u003ccode\u003einvalid upstream\u003c/code\u003e error and firewall blocks between the Operations Suite Infrastructure - Core Services (OIC) and the Operations organization, as well as several upgrade related errors.\u003c/p\u003e\n"],["\u003cp\u003eThe base image \u003ccode\u003egcr.io/distroless/base\u003c/code\u003e has been updated to digest \u003ccode\u003esha256:d08c10f03c27271160993f294e0eb120af71217d0cf4587c484cc5b7cb3fe5ee\u003c/code\u003e in order to apply the latest security patches.\u003c/p\u003e\n"]]],[],null,["# Google Distributed Cloud air-gapped release notes\n\n\u003cbr /\u003e\n\nFebruary 08, 2024 \\[GDC 1.9.10\\]\n--------------------------------\n\n*** ** * ** ***\n\n\nGoogle Distributed Cloud air-gapped 1.9.10 is now released.\n\nSee the [product overview](/distributed-cloud/hosted/docs/latest/gdch/overview) to learn about the features of Google Distributed Cloud air-gapped.\n\n*** ** * ** ***\n\n\nUpdated Canonical Ubuntu OS image version to 20240114 to apply the latest security patches and important updates. To take advantage of the bug and security vulnerability fixes, you must upgrade all nodes with each release. The following security vulnerabilities are fixed:\n\n- [CVE-2017-16516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16516)\n- [CVE-2020-14394](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14394)\n- [CVE-2020-24165](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24165)\n- [CVE-2021-3638](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3638)\n- [CVE-2022-1725](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1725)\n- [CVE-2022-1771](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1771)\n- [CVE-2022-1897](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1897)\n- [CVE-2022-2000](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2000)\n- [CVE-2022-24795](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24795)\n- [CVE-2023-1544](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1544)\n- [CVE-2023-2861](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2861)\n- [CVE-2023-3180](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3180)\n- [CVE-2023-33460](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33460)\n- [CVE-2023-3354](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3354)\n- [CVE-2023-3446](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3446)\n- [CVE-2023-3817](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3817)\n- [CVE-2023-29491](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29491)\n- [CVE-2023-36054](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-36054)\n- [CVE-2023-38408](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38408)\n- [CVE-2023-39804](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-39804)\n- [CVE-2023-46246](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-46246)\n- [CVE-2023-48231](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48231)\n- [CVE-2023-48233](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48233)\n- [CVE-2023-48234](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48234)\n- [CVE-2023-48235](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48235)\n- [CVE-2023-48236](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48236)\n- [CVE-2023-48237](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48237)\n- [CVE-2023-48795](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48795)\n- [CVE-2023-5088](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-5088)\n- [CVE-2023-7104](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-7104)\n\n*** ** * ** ***\n\n\nThe following container image security vulnerabilities are fixed:\n\n- [CVE-2021-46848](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46848)\n- [CVE-2022-2097](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2097)\n- [CVE-2022-3094](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3094)\n- [CVE-2022-3821](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3821)\n- [CVE-2022-4304](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4304)\n- [CVE-2022-4415](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4415)\n- [CVE-2022-4450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4450)\n- [CVE-2022-4883](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4883)\n- [CVE-2022-29458](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29458)\n- [CVE-2022-32221](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32221)\n- [CVE-2022-43552](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-43552)\n- [CVE-2022-44617](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-44617)\n- [CVE-2022-46285](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-46285)\n- [CVE-2022-47629](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-47629)\n- [CVE-2023-0215](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0215)\n- [CVE-2023-0286](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0286)\n- [CVE-2023-0361](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0361)\n- [CVE-2023-0464](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0464)\n- [CVE-2023-0465](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0465)\n- [CVE-2023-0466](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0466)\n- [CVE-2023-2650](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2650)\n- [CVE-2023-2828](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2828)\n- [CVE-2023-3138](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3138)\n- [CVE-2023-3341](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3341)\n- [CVE-2023-3446](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3446)\n- [CVE-2023-3817](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3817)\n- [CVE-2023-23916](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23916)\n- [CVE-2023-27533](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-27533)\n- [CVE-2023-27535](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-27535)\n- [CVE-2023-27536](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-27536)\n- [CVE-2023-27538](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-27538)\n- [CVE-2023-28321](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28321)\n- [CVE-2023-28484](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28484)\n- [CVE-2023-29469](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29469)\n- [CVE-2023-29491](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29491)\n- [CVE-2023-34969](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-34969)\n- [CVE-2023-36054](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-36054)\n- [CVE-2023-40303](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40303)\n- [CVE-2023-43785](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-43785)\n- [CVE-2023-43786](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-43786)\n- [CVE-2023-43787](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-43787)\n- [CVE-2023-43788](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-43788)\n- [CVE-2023-43789](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-43789)\n\n*** ** * ** ***\n\nUpdated the `gcr.io/distroless/base` base image to digest `sha256:sha256:d08c10f03c27271160993f294e0eb120af71217d0cf4587c484cc5b7cb3fe5ee` to apply the latest security patches and important updates.\n\n*** ** * ** ***\n\nGoogle Distributed Cloud air-gapped 1.9.10 fixes an\nissue where Grafana displays an empty `invalid upstream` error.\n\n*** ** * ** ***\n\nGoogle Distributed Cloud air-gapped 1.9.10 fixes an\nissue where firewall blocks traffic between the Operations Suite Infrastructure - Core Services (OIC) and the Operations organization.\n\n*** ** * ** ***\n\n**Upgrade**:\n\n- The `NodeUpgradeTask` for the node is stuck at `NodeMaintainCompleted` step for a longer period (more than 30mins)\n- The `zp-aa-bm08` node of the root admin cluster shows a provisioning error and cannot finish because the registry is unhealthy.\n\n- The `gpcbackup-agent-0` pod fails with the error message `failed to stage volume: iSCSI login failed`.\n\n- The upgrade is stuck at `AdminClusterHealth` postflight check.\n\n\u003cbr /\u003e\n\n*** ** * ** ***\n\n**VM Backup and Restore**:\n\n- Role-based access control (RBAC) and schema settings in the VM manager is stopping users from starting VM backup and restore processes.\n| **Important:** To access the URLs listed on this page, you must connect to the internet. The URLs are provided to access outside of your air-gapped environment."]]