diff --git a/5abe96e9cbc1a3a9e517e9f8acf4d7533ab576a7 b/5abe96e9cbc1a3a9e517e9f8acf4d7533ab576a7
index 011bf2ea..209b6c5c 100644
--- a/5abe96e9cbc1a3a9e517e9f8acf4d7533ab576a7
+++ b/5abe96e9cbc1a3a9e517e9f8acf4d7533ab576a7
@@ -104,6 +104,24 @@
       "parentUuid": "e6181112_194f38fd",
       "revId": "5abe96e9cbc1a3a9e517e9f8acf4d7533ab576a7",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "1e2ab5cd_9d83ade7",
+        "filename": "/PATCHSET_LEVEL",
+        "patchSetId": 1
+      },
+      "lineNbr": 0,
+      "author": {
+        "id": 26721
+      },
+      "writtenOn": "2022-05-14T13:43:42Z",
+      "side": 1,
+      "message": "Thanks Takashi for your comments. \n\nYes, we use puppet module in the host(VM) level to generate config files. And kolla container will mount the config files/folder during its runtime. In that case, if we keep the default kolla image uid/gid, we should use the same one to start the container from the host(VM). This is a natural transistion for us, because we are migarting our services from VM to container. And we deployed the service on VM using puppet module before and it worked well, so now we just want to start the service as a container without changing other things. \n\nAnd as you replied in another change I made (https://review.opendev.org/c/openstack/puppet-ceilometer/+/841528), maybe adding uid/gid as configurable parameter will be easier solution?",
+      "parentUuid": "3e4f3062_2c383b6c",
+      "revId": "5abe96e9cbc1a3a9e517e9f8acf4d7533ab576a7",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
     }
   ]
 }
\ No newline at end of file