Update patch set 6

Patch Set 6: Workflow-1

(1 comment)

Patch-set: 6
Reviewer: Gerrit User 28464 <28464@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
Label: Workflow=-1, 6d9b5d9b3d65560b45313f70c17e12eebf74471b

b152653a83c069a027bd5bcf369afa9e029478de

@@ -0,0 +1,27 @@
+{
+  "comments": [
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "e89b419f_85ac10af",
+        "filename": "mtce/src/maintenance/mtcNodeComp.cpp",
+        "patchSetId": 6
+      },
+      "lineNbr": 383,
+      "author": {
+        "id": 28464
+      },
+      "writtenOn": "2024-03-24T13:18:19Z",
+      "side": 1,
+      "message": "Noticing the mtcClient get a socket rx socket bind failure on controller-0 just following the pxeboot install from external install server when trying to bind to the oam (install) interface that at that point looks like the management interface.\n\nThis issue does not fail the install it just periodically logs and retries the bind until the unlock occurs. I don\u0027t like the failure logs. Investigating a code change to better deal with this case.\n\nsetup_pxeboot_rx_socket :Error : failed to bind 128.224.54.156:2119 to socket\n\nThe above address is the oam assigned address, not a pxeboot network address.\n \nThe code should try and detect and avoid setting up the pxeboot network on the install interface following a system install from an external pxeboot server.",
+      "range": {
+        "startLine": 383,
+        "startChar": 5,
+        "endLine": 383,
+        "endChar": 29
+      },
+      "revId": "b152653a83c069a027bd5bcf369afa9e029478de",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    }
+  ]
+}