{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":188471573,"defaultBranch":"master","name":"cloud-platform-deployment-manager","ownerLogin":"Wind-River","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2019-05-24T18:44:40.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/15164491?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1726841919.0","currentOid":""},"activityList":{"items":[{"before":"f5e20a8e4e7e40b79480186d344bdcb3188b886f","after":null,"ref":"refs/heads/stable/v24.09.0","pushedAt":"2024-09-20T14:18:39.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"}},{"before":"f5e20a8e4e7e40b79480186d344bdcb3188b886f","after":"c6ca781fafe491d162f8cc712c8dd7458b2f4d13","ref":"refs/heads/master","pushedAt":"2024-09-18T18:33:26.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"hugonicodemos","name":"Hugo Nicodemos","path":"/hugonicodemos","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1226763?s=80&v=4"},"commit":{"message":"When kubectl delete crd is executed its getting timed out (#402)\n\nThe CRD finalizer is removed to make sure no the command is not timed out\r\n\r\nTest Cases:\r\nPASS- kubectl delete should not timeout\r\n\r\nSigned-off-by: vineela-pachchipulusu ","shortMessageHtmlLink":"When kubectl delete crd is executed its getting timed out (#402)"}},{"before":null,"after":"f5e20a8e4e7e40b79480186d344bdcb3188b886f","ref":"refs/heads/stable/v24.09.0","pushedAt":"2024-09-18T17:16:59.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Update factory install config workflow\n\nAs the factory install workflow changes: starting from fully deployed\nsystem to only the active controller was deployed. This commit updates\nthe configuration workflow to align with the starting point: using the\nday-1 operation rather than day-2 operation to config the system.\n\nThis commit:\n1. Removes the strategy related code for configuration post factory\ninstall.\n2. Update all the resources' reconclied status to \"false\" once to\nunblock the reconcliation.\n3. Set the configuration post factory install finalized post the\nunlock of the active controller.\n\nWith this change, the configuration post factory install should no\nlonger trigger a vim strategy to orchestrate the lock/unlock of the\nhosts.\n\nAdditional requests:\n1 the host should be locked before applying the configMap to start the\nconfiguration.\n2 the administrative status should be set to \"unlock\" to trigger the\nunlock of the host.\n\nTest plan:\n1. Deploy an active controller of a DX system, lock the controller.\n2. Apply the configMap to trigger the configuration.\n3. Verify the host can be reconfigured and unlocked by DM.\n4. Verify the host can be reconciled post unlock.\n\nSigned-off-by: Yuxing Jiang ","shortMessageHtmlLink":"Update factory install config workflow"}},{"before":"18aa91937b71d1e6ffa11d7ff87015c1265db699","after":"f5e20a8e4e7e40b79480186d344bdcb3188b886f","ref":"refs/heads/master","pushedAt":"2024-09-17T18:48:21.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"},"commit":{"message":"Update factory install config workflow\n\nAs the factory install workflow changes: starting from fully deployed\nsystem to only the active controller was deployed. This commit updates\nthe configuration workflow to align with the starting point: using the\nday-1 operation rather than day-2 operation to config the system.\n\nThis commit:\n1. Removes the strategy related code for configuration post factory\ninstall.\n2. Update all the resources' reconclied status to \"false\" once to\nunblock the reconcliation.\n3. Set the configuration post factory install finalized post the\nunlock of the active controller.\n\nWith this change, the configuration post factory install should no\nlonger trigger a vim strategy to orchestrate the lock/unlock of the\nhosts.\n\nAdditional requests:\n1 the host should be locked before applying the configMap to start the\nconfiguration.\n2 the administrative status should be set to \"unlock\" to trigger the\nunlock of the host.\n\nTest plan:\n1. Deploy an active controller of a DX system, lock the controller.\n2. Apply the configMap to trigger the configuration.\n3. Verify the host can be reconfigured and unlocked by DM.\n4. Verify the host can be reconciled post unlock.\n\nSigned-off-by: Yuxing Jiang ","shortMessageHtmlLink":"Update factory install config workflow"}},{"before":"de3086596b96011ae2b94aa67c96a85132e8392e","after":"18aa91937b71d1e6ffa11d7ff87015c1265db699","ref":"refs/heads/master","pushedAt":"2024-09-17T13:18:48.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"},"commit":{"message":"Add N-1 Support for Subcloud Configuration\n\nDue to USM, the load-import functionality has been\nreplaced with software upload. In the software upload\nprocess for N-1 loads, deployment-manager files are\nno longer present in /opt/platform/software_version.\n\nWe are checking for the presence of DM deploy files\nin the /opt/platform/deploy/ directory.\nIf these files are found, the DM files (playbook,\noverrides, helm-chart) will be updated in the payload.\n\nIf the files are not found in the specified directory,\nthe process will then search for them in an alternative\nlocation at /usr/local/share/applications/ on the\nsystem controller. If located there, these files will\nupdate the DM files in the payload, and the\nuser_uploaded_artifacts flag will be set to false,\nindicating that the files were not manually uploaded by the user.\n\nSince the system controller playbook is updated in the payload\nrather than the subcloud, this means the system controller\nplaybook (version 24.09) will be executed within the subcloud\nconfiguration version 22.12.\n\nTo address this, the playbook now verifies whether the host\nversion is less than 24.09, if the subcloud and user has not\nuploaded DM artifacts then helm based Deployment-manager is install.\n\nTest-Plan:\nA) PASS: Deploy AIO-SX successfully.\n\nB) Set-up\nDC-libvirt 24.09 system controller 22.12 subcloud\n\n1. Uploaded 22.12 DM artifacts using\n dcmanager subcloud deploy upload DM-chart, overrides,\n playbook.\n2. Added a 22.12 subcloud using dcmanager subcloud add.\n Validated the uploaded artifacts are picked up for\n configuration.\n3. Helm based DM and DM monitor is running.\n4. Deleted the DM artifacts present on the subcloud in\n /usr/local/share/applications/\n5. Recong a subcloud using dcmanager subcloud deploy config,\n validated the uploaded DM artifacts are picked up for\n configuration.\n6. Helm based DM and DM monitor is running.\n\n1. Not uploaded 22.12 DM artifacts using\n2. Added a 22.12 subcloud using dcmanager subcloud add.\n Validated the DM helm-chart and overrides are picked from\n sublcoud for configuration, and playbook from system controller.\n3. Helm based DM and DM monitor is running.\n4. Recong a subcloud using dcmanager subcloud deploy config,\n Validated the DM helm-chart and overrides are picked from\n sublcoud for configuration, and playbook from system controller.\n5. Helm based DM and DM monitor is running.\n\nC) Set-up\nDC-libvirt 24.09 system controller 24.09 subcloud.\n\n1. Not uploaded 24.09 DM artifacts using\n dcmanager subcloud deploy upload DM-chart, overrides,\n playbook.\n2. Added a 24.09 subcloud using dcmanager subcloud add.\n3. System application based DM and DM monitor is running.\n4. Recong a subcloud using dcmanager subcloud deploy config.\n5. System application based DM and DM monitor is running.\n\nSigned-off-by: sbhardwa ","shortMessageHtmlLink":"Add N-1 Support for Subcloud Configuration"}},{"before":"1c55c5acdef2ace691ae1fa7481312493ffe4e12","after":"de3086596b96011ae2b94aa67c96a85132e8392e","ref":"refs/heads/master","pushedAt":"2024-09-13T13:47:30.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"hugonicodemos","name":"Hugo Nicodemos","path":"/hugonicodemos","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1226763?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved (#390)\n\nBelow blocks are skipped when reconfig_flag is true:\r\n1) Search administrativeState into host resource\r\n2) Wait until unlock task triggered\r\n\r\nThereby, playbook doesn't attempt to apply the config during\r\n'deploy resume' and henceforth any unresolved errors persist\r\nbut it reports deploy status as 'complete' which is incorrect.\r\n\r\nTest Cases:\r\n1. PASS: Run subcloud add with deploy-config. Make sure there is\r\n an error condition that will cause DM playbook to fail.\r\n Run deploy resume, it should report error.\r\n2. PASS: Run subcloud add with deploy-config. Make sure there is\r\n no error condition and DM playbook shall pass.\r\n Run deploy resume, it should skip above mentioned tasks.\r\n3. PASS: Day-2 operation tested with controller-0 unlocked for\r\n 'system' resource.\r\n4. PASS: Day-2 operation tested with controller-0 locked for\r\n 'host' resource.\r\n\r\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved (#390)"}},{"before":"d9325dd0a6323294e8e9df20402249432e6dce20","after":null,"ref":"refs/heads/dev/65305-2","pushedAt":"2024-09-13T13:29:40.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"}},{"before":"b52ba2fbba6a34a497d08c4c7473c3aa202cdca3","after":null,"ref":"refs/heads/dev/65810","pushedAt":"2024-09-13T13:29:39.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"}},{"before":"db9fabaea55f5aa5093364419752bf0652d1658b","after":"757eb2fc896e12fb8583bcf581e21e7ede462342","ref":"refs/heads/dev/65305","pushedAt":"2024-09-13T10:28:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases:\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n3. PASS: Day-2 operation tested with controller-0 unlocked for\n 'system' resource.\n4. PASS: Day-2 operation tested with controller-0 locked for\n 'host' resource.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"92fc627283d82df6a0bed6c6a62339dd764d990d","after":"db9fabaea55f5aa5093364419752bf0652d1658b","ref":"refs/heads/dev/65305","pushedAt":"2024-09-12T11:32:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases: (Need to retest)\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n3. PASS: Day-2 operation tested with controller-0 unlocked for\n 'system' resource.\n4. PASS: Day-2 operation tested with controller-0 locked for\n 'host' resource.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"1ca0143d04267658221481f331bfee3d24edb3b8","after":"92fc627283d82df6a0bed6c6a62339dd764d990d","ref":"refs/heads/dev/65305","pushedAt":"2024-09-11T14:16:48.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases: (Need to retest)\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n3. PASS: Day-2 operation tested with controller-0 unlocked for\n 'system' resource.\n4. PASS: Day-2 operation tested with controller-0 locked for\n 'host' resource.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"232bea94ac3cfaae4c3efc463a5b4648ef70f588","after":"1ca0143d04267658221481f331bfee3d24edb3b8","ref":"refs/heads/dev/65305","pushedAt":"2024-09-11T14:15:47.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases:\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n3. PASS: Day-2 operation tested with controller-0 unlocked for\n 'system' resource.\n4. PASS: Day-2 operation tested with controller-0 locked for\n 'host' resource.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"81da45c0eaf8d7b6b13b0c6e18a001fb0780e572","after":"232bea94ac3cfaae4c3efc463a5b4648ef70f588","ref":"refs/heads/dev/65305","pushedAt":"2024-09-11T14:01:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases:\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n3. PASS: Day-2 operation tested with controller-0 unlocked for\n 'system' resource.\n4. PASS: Day-2 operation tested with controller-0 locked for\n 'host' resource.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"267506df75723d418b831e4e01da378be66df48d","after":"1c55c5acdef2ace691ae1fa7481312493ffe4e12","ref":"refs/heads/master","pushedAt":"2024-09-10T13:25:38.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"enzocandotti","name":null,"path":"/enzocandotti","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17912346?s=80&v=4"},"commit":{"message":"Enable playbook task for ignoring unreachable servers (#399)\n\nDM playbook failed due to second reboot on standard subcloud.\r\nPlaybook has block for when system reboot twice but it was not\r\ngetting triggered. When server is unreachable, task status is\r\nset to unreachable instead of failed. From ansible 2.7, it is\r\npossible to use ignore_unreachable.\r\n\r\nTest Cases:\r\n1. PASS: Run dcmanager add from system controller. Deployment\r\n config is applied successfully on controller-0 with server\r\n rebooting twice. 'deploy status' shall be 'complete' for the\r\n subcloud.\r\n2. PASS: Deploy AIO-SX successfully.\r\n\r\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Enable playbook task for ignoring unreachable servers (#399)"}},{"before":"cb24e3faec2c1b04b79fc0f5e904a4443c8ef4b2","after":"267506df75723d418b831e4e01da378be66df48d","ref":"refs/heads/master","pushedAt":"2024-09-06T22:45:16.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"hugonicodemos","name":"Hugo Nicodemos","path":"/hugonicodemos","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1226763?s=80&v=4"},"commit":{"message":"kubectl delete host resource failed by cmd timeout (#400)\n\nThe kubectl delete host is getting stuck and failed by cmd timeout till the\r\nfinalizer is manually deleted in the STANDARD setup\r\nand during the deletion of the compute host\r\n\r\nTest Cases:\r\nPASS- kubectl delete host should not timeout\r\n\r\nSigned-off-by: vineela-pachchipulusu ","shortMessageHtmlLink":"kubectl delete host resource failed by cmd timeout (#400)"}},{"before":null,"after":"b52ba2fbba6a34a497d08c4c7473c3aa202cdca3","ref":"refs/heads/dev/65810","pushedAt":"2024-09-04T10:55:39.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Enable playbook task for ignoring unreachable servers\n\nDM playbook failed due to second reboot on standard subcloud.\nPlaybook has block for when system reboot twice but it was not\ngetting triggered. When server is unreachable, task status is\nset to unreachable instead of failed. From ansible 2.7, it is\npossible to use ignore_unreachable.\n\nTest Cases:\n1. Pending: Run dcmanager add from system controller. Deployment\n config is applied successfully on controller-0 with server\n rebooting twice. 'deploy status' shall be 'complete' for the\n subcloud.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Enable playbook task for ignoring unreachable servers"}},{"before":"400cf2b96e6048392238c4d135b721266eba2914","after":"cb24e3faec2c1b04b79fc0f5e904a4443c8ef4b2","ref":"refs/heads/master","pushedAt":"2024-09-03T23:07:12.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"},"commit":{"message":"Disable route compare when reconfig\n\nThis commit disables the route comparison when it is a reconfiguration\nscenario, avoids triggering the lock request in the day-2 operation.\n\nAfter this change, the route can still be compared during initial\ndeployment or on a enabled host when reconfiguring the host.\n\nTest plan:\n1. Initial deployment of AIOSX subcloud with admin network.\n2. Reconfigure the admin network(multi-netting), verified the routes\nupdate not causing reboot.\n\nSigned-off-by: Yuxing Jiang ","shortMessageHtmlLink":"Disable route compare when reconfig"}},{"before":"6acfa5753295fc80330e768edac643031d70ae6a","after":"400cf2b96e6048392238c4d135b721266eba2914","ref":"refs/heads/master","pushedAt":"2024-09-03T13:13:32.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"},"commit":{"message":"Restrict Filesystem Removal\n\nDespite ceph host filesystem is optional and allowed to be created,\nits removal is only supported in specific situations and should not be\naddressed by Deployment Manager.\n\nThis commit also resolves a reconcile error due to automatic creation of\nceph host filesystem using Ceph bare metal.\n\nIncludes:\n- Creates the FileSystemDeletionAllowed list excluding ceph.\n- Updates the \"Should return false when in and other storage is not equal\n and have allowed filesystem types\" feature test to use the\n image-conversion instead of ceph.\n- Creates a new feature test expecting the reconcile to be true when the\n extra filesystem is ceph.\n\nSigned-off-by: Hediberto C Silva ","shortMessageHtmlLink":"Restrict Filesystem Removal"}},{"before":null,"after":"d9325dd0a6323294e8e9df20402249432e6dce20","ref":"refs/heads/dev/65305-2","pushedAt":"2024-08-27T13:18:04.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases:\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n3. PASS: Day-2 operation tested with controller-0 unlocked for\n 'system' resource.\n4. PASS: Day-2 operation tested with controller-0 locked for\n 'host' resource.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"75f858db11d25d9120376af0ecebf2183636393f","after":"6acfa5753295fc80330e768edac643031d70ae6a","ref":"refs/heads/master","pushedAt":"2024-08-26T14:13:02.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"hugonicodemos","name":"Hugo Nicodemos","path":"/hugonicodemos","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1226763?s=80&v=4"},"commit":{"message":"Improved host controller file UT upto 46.7% (#392)\n\nUnit test cases for host controller\r\n- Test cases written for utility funcitons in host controller\r\n- Test coverage for host_controller_test.go is 46.7%\r\n\r\nSigned-off-by: vineela-pachchipulusu ","shortMessageHtmlLink":"Improved host controller file UT upto 46.7% (#392)"}},{"before":"ed7cd613f13b76d3511f841ad92badd85ac53e3f","after":"81da45c0eaf8d7b6b13b0c6e18a001fb0780e572","ref":"refs/heads/dev/65305","pushedAt":"2024-08-23T11:14:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases:\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n3. PASS: Day-2 operation tested with controller-0 unlocked for\n 'system' resource.\n4. PASS: Day-2 operation tested with controller-0 locked for\n 'host' resource.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"ae36177983c33d53476685f697c4e2b074e0b7d4","after":"ed7cd613f13b76d3511f841ad92badd85ac53e3f","ref":"refs/heads/dev/65305","pushedAt":"2024-08-23T10:35:36.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases:\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n3. PASS: Day-2 operation tested with controller-0 unlocked for\n 'system' resource.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"b83007a87b719513159c999e445a7f2fd84c5d83","after":"ae36177983c33d53476685f697c4e2b074e0b7d4","ref":"refs/heads/dev/65305","pushedAt":"2024-08-23T05:53:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases: (TBD)\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"35a45154f5f3bb95cfb03357025bc5b75827bbb7","after":"75f858db11d25d9120376af0ecebf2183636393f","ref":"refs/heads/master","pushedAt":"2024-08-22T20:39:37.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"},"commit":{"message":"Limit resource consumption\n\nThis commit limits the resource comsumption.\n\nFurther, due to the system configuration collection may impact the\nsysinv-api heavily, this commit raise the threshhold of the DM pod\nrestart caused by the liveness probe and readiness probe.\n\nThis commit also disabled the leader election if the replica is less\nthan 2.\n\nTest plan:\n1. Deploy AIOSX/DX subcloud, ensure the playbook not failed due to the\nslow down of the limited resource.\n2. Trigger day-2 operation on the SX and DX subcloud, ensure the Day-2\noperation not failed in this limited resource configuration.\n3. Soak the DM in a special 1 platform core system, monitor the DM pod\nno longer restarted frequently due to probe failure.\n\nSigned-off-by: Yuxing Jiang ","shortMessageHtmlLink":"Limit resource consumption"}},{"before":"53e16ce3f0ce472286d428d56063b2aa1084779f","after":null,"ref":"refs/heads/dev/dual-stack-networking","pushedAt":"2024-08-15T20:02:07.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"}},{"before":"6a1192c7249d9820c22f236d5f52bfc528fb4990","after":null,"ref":"refs/heads/revert-363-dev/dual-stack-networking","pushedAt":"2024-08-15T20:02:05.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"}},{"before":"3823e974009b70e014681bebadf59601b6f0b834","after":"b83007a87b719513159c999e445a7f2fd84c5d83","ref":"refs/heads/dev/65305","pushedAt":"2024-08-15T15:35:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases: (TBD)\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":null,"after":"3823e974009b70e014681bebadf59601b6f0b834","ref":"refs/heads/dev/65305","pushedAt":"2024-08-14T14:09:56.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"sselvara1","name":null,"path":"/sselvara1","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/124687812?s=80&v=4"},"commit":{"message":"Report error for 'deploy resume' when issue is unresolved\n\nBelow blocks are skipped when reconfig_flag is true:\n1) Search administrativeState into host resource\n2) Wait until unlock task triggered\n\nThereby, playbook doesn't attempt to apply the config during\n'deploy resume' and henceforth any unresolved errors persist\nbut it reports deploy status as 'complete' which is incorrect.\n\nTest Cases: (TBD)\n1. PASS: Run subcloud add with deploy-config. Make sure there is\n an error condition that will cause DM playbook to fail.\n Run deploy resume, it should report error.\n2. PASS: Run subcloud add with deploy-config. Make sure there is\n no error condition and DM playbook shall pass.\n Run deploy resume, it should skip above mentioned tasks.\n\nSigned-off-by: sselvara1 ","shortMessageHtmlLink":"Report error for 'deploy resume' when issue is unresolved"}},{"before":"188fa38d661ed5bbff0cb735c5008351cd769375","after":"35a45154f5f3bb95cfb03357025bc5b75827bbb7","ref":"refs/heads/master","pushedAt":"2024-07-30T15:15:57.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"},"commit":{"message":"DM playbook does not allow custom DM app path as input\n\nDM pods are set up on systems by the DM playbook by applying the DM app\ntarball,which is provided on /usr/local/share/applications/helm/ on WRCP ISOs.\n\nHowever, the app tarball path variable used on the playbook is not\nconfigurable.\nFor instance, if the dev moves the tarball from the original location\nand sets the 'manager_app_chart' variable in the overrides, the playbook will\nfail.\n\nThis isn't a major issue on WRCP ISOs, but it makes the playbook unusable on\nSTX.\n\nTest plan:\n1. PASS- Build all the packages\n2. PASS- Build the iso\n3. PASS- Create the AIO-SX VM\n4. PASS- Aio-SX running\nDM system app is up\nPick the default dm overrides\nRemove the DM system application\nDelete the DM system application\nTransffered the dm_app_helm_chart from the /usr/local/share/applications/helm/ to the /home/sysadmin/ path\nUpdate the dm overrides file\nExecute the playbook command with the dm overrides\nValidate that dm overrides are picked correctly and DM is installed\nDM system application is running\n\nSigned-off-by: vineela-pachchipulusu ","shortMessageHtmlLink":"DM playbook does not allow custom DM app path as input"}},{"before":"279dab8d7db6a63a2707a2a0382b9e246ae4a2c2","after":"188fa38d661ed5bbff0cb735c5008351cd769375","ref":"refs/heads/master","pushedAt":"2024-07-18T17:35:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"yjian118","name":"Yuxing Jiang","path":"/yjian118","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/43456284?s=80&v=4"},"commit":{"message":"Fix format issue in README.md","shortMessageHtmlLink":"Fix format issue in README.md"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0yMFQxNDoxODozOS4wMDAwMDBazwAAAAS8DEHz","startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0yMFQxNDoxODozOS4wMDAwMDBazwAAAAS8DEHz","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNy0xOFQxNzozNTozMi4wMDAwMDBazwAAAASDL-z1"}},"title":"Activity ยท Wind-River/cloud-platform-deployment-manager"}