{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":238749457,"defaultBranch":"master","name":"nfv","ownerLogin":"starlingx","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2020-02-06T17:51:56.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/60524195?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1712666181.0","currentOid":""},"activityList":{"items":[{"before":"77a2dd027fa38180649c8f77d772e34cefb619d1","after":"2e46016364f6e644f5e4480edfc7c6b470beae3d","ref":"refs/heads/master","pushedAt":"2024-06-04T17:53:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Add major release logic\n\nMajor releases have additional requirements around SWACT and which\ncontroller is used for what. This adds that logic.\n\nA major release is decided by the the major and minor sw_versions.\nIf either the major or minor version have changed we will consider it a\nmajor release.\n\nTEST PLAN\nPASS: AIO-DX major release upgrade\n* SWACTs and sorting occur\nPASS: AIO-DX patch release upgrade with value manually changed to false\n* SWACTs and sorting do not occur\n\nStory: 2011045\nTask: 50170\nChange-Id: Ie357ab36622bd5fcca75f66899515534886fada1\nSigned-off-by: Joshua Kraitberg ","shortMessageHtmlLink":"Add major release logic"}},{"before":"ed891561381c5e589547052029f3765bfb577eb1","after":"77a2dd027fa38180649c8f77d772e34cefb619d1","ref":"refs/heads/master","pushedAt":"2024-05-31T20:47:55.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Support async for sw-deploy start and activate\"","shortMessageHtmlLink":"Merge \"Support async for sw-deploy start and activate\""}},{"before":"57b6635fcce43d09a809a669eb7a31ca1c857488","after":"ed891561381c5e589547052029f3765bfb577eb1","ref":"refs/heads/master","pushedAt":"2024-05-31T14:01:50.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Add USM entries to VIM config\n\nThese were not added. They were being autogenerated so there was no\nissue. This will make the definition explicit and stable.\n\nTEST PLAN\nPASS: On SX system, verify values in config\n\nStory: 2011045\nTask: 50207\nChange-Id: I04d0aa92b6f41cd46d137753c854def6e7e694e4\nSigned-off-by: Joshua Kraitberg ","shortMessageHtmlLink":"Add USM entries to VIM config"}},{"before":"053327fe8f072256dc026f62f9643c558dabc4ef","after":"57b6635fcce43d09a809a669eb7a31ca1c857488","ref":"refs/heads/master","pushedAt":"2024-05-22T17:33:48.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"sw-deploy strategy for reboot-required patch-release(AIO-SX)\"","shortMessageHtmlLink":"Merge \"sw-deploy strategy for reboot-required patch-release(AIO-SX)\""}},{"before":"1f05af23e3408ffc7c2c15ed5c817f69e711f818","after":"053327fe8f072256dc026f62f9643c558dabc4ef","ref":"refs/heads/master","pushedAt":"2024-05-22T13:03:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Added rollback option to sw-deploy-strategy\n\nThis allows users to specify if the sw-deploy they want is going to be a\nrollback. Currently, this will fail the strategy because rollback is\nnot implemented.\n\nExamples:\n\nNormal sw-deploy:\nsw-manager sw-deploy-strategy create starlingx-24.09.0\n\nRollback sw-deploy:\nsw-manager sw-deploy-strategy create --rollback\n\nTEST PLAN\nPASS: --rollback option triggers strategy to fail\nPASS: Without --rollback, strategy is not impacted\n\nStory: 2011045\nTask: 50066\nDepends-On: https://review.opendev.org/c/starlingx/nfv/+/916648\nChange-Id: Iba29db17c33699e3ae55ca1258f567ea2428a323\nSigned-off-by: Joshua Kraitberg ","shortMessageHtmlLink":"Added rollback option to sw-deploy-strategy"}},{"before":"93fd832c4bc3b891846f6a5c9ec3476ae1563fc2","after":"1f05af23e3408ffc7c2c15ed5c817f69e711f818","ref":"refs/heads/master","pushedAt":"2024-05-10T20:36:13.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"sw-deploy strategy for in-service patch-release(AIO-SX)\n\nsw-deploy API implementation and create\nstrategy validations.\nThe API implementations are common for\nboth major and minor release.The current\nchanges are tested only on AIO-SX for patch\nrelease(in-service patch)\n\nNew CLI command usage:\nsw-manager sw-deploy-strategy create starlingx-24.03.1\nsw-manager sw-deploy-strategy apply\nsw-manager sw-deploy-strategy abort\nsw-manager sw-deploy-strategy delete\n\nTest Plan:\nPASSED: On SX system, perform end to end sw-deploy strategy\nupdate using in-service patch.\nPASSED: On SX system, provide invalid release as input to\nsw-manager sw-deploy-strategy create command.\nCreate startegy fails.\n\nStory: 2011045\nTask: 49911\n\nChange-Id: I265c8a1f9fbadf04275e0af788614d094c23315c\nSigned-off-by: Vanathi.Selvaraju ","shortMessageHtmlLink":"sw-deploy strategy for in-service patch-release(AIO-SX)"}},{"before":"230aa6fd97a0fe4d861ced4a09203021a5130413","after":"93fd832c4bc3b891846f6a5c9ec3476ae1563fc2","ref":"refs/heads/master","pushedAt":"2024-05-02T17:25:52.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Add new application update steps for k8s upgrades\"","shortMessageHtmlLink":"Merge \"Add new application update steps for k8s upgrades\""}},{"before":"6142d9f11642113cb641d5683e02478c1a011941","after":"230aa6fd97a0fe4d861ced4a09203021a5130413","ref":"refs/heads/master","pushedAt":"2024-04-30T23:05:36.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Remove CentOS/OpenSUSE build support\n\nStarlingX stopped supporting CentOS builds in the after release 7.0.\nThis update will strip CentOS from our code base. It will also remove\nreferences to the failed OpenSUSE feature as well.\n\nStory: 2011110\nTask: 49959\nChange-Id: I294e6943b4c7b95820c98991424f130dc85c22ad\nSigned-off-by: Scott Little ","shortMessageHtmlLink":"Remove CentOS/OpenSUSE build support"}},{"before":"eca1a05b8310cfb2878a1921fe65236fae78ec5b","after":"6142d9f11642113cb641d5683e02478c1a011941","ref":"refs/heads/master","pushedAt":"2024-04-15T18:38:34.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"sw-deploy-strategy backend overhaul\n\nRoughed in sw-deploy by replacing sw-upgrade and adding things as\nneeded. The intention here being is to create the basic stage/step flow\nfor followup reviews.\n\nThere are numerous changes still required to complete the strategy.\n\nTODO in followups:\n* SWACT/unlock retries\n* Fix any broken/new steps (precheck/deploy/hosts_list)\n* Update USM API calls after they are changed\n* Maintain state using USM api responses\n* Major release support, including SWACT to controller-0 if required\n* strategy reentrancy\n\nTEST PLAN\nPASSING: Unit tests\nNOT PASSING: sw-deploy-strategy on AIO-SX\nNOT PASSING: sw-deploy-strategy on system controllers (AIO-DX)\n\nDepends-On: https://review.opendev.org/c/starlingx/nfv/+/914037\nStory: 2011045\nTask: 49783\nChange-Id: If1eb5b45089f4a67d6d88093d0e215e510fd8c55\nSigned-off-by: Joshua Kraitberg ","shortMessageHtmlLink":"sw-deploy-strategy backend overhaul"}},{"before":"8dfb971980f14b1fdab1ee993216120ee2aa2ccf","after":"eca1a05b8310cfb2878a1921fe65236fae78ec5b","ref":"refs/heads/master","pushedAt":"2024-04-12T21:18:10.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"sw-manager patch-strategy failed to install due to timeout\n\nAs part of this fix, new parameter ignore_alarm_conditional\nis added, which has the list of stale alarms that needs to\nignored after 30mins.\nAlarm clear wait step checks for stale alarm 750.006 for\n30mins. If the alarm is still not cleared, patch-strategy\nignores the alarm.\nNow, since the stale alarms are monitored for 30mins,\nthe overall alarm clear timeout is increased to 2400sec.\n\nIn the current case alarm 750.006 is not getting cleared\nand also it is not part of the ignore alarm list\nso the patch-strategy times out.\n\nTest Plan:\nPASSED: Applying a patch - On DX system(VM),\nCreate and apply patch strategy,\nfm alarm-list to have an uncleared alarm(for test purpose\n100.103 - Memory threshold alarm was used). After 30mins\nalarm was ignored and patch strategy successfully applied.\nPASSED: Removing a patch - On DX system(VM),\nCreate and apply patch strategy,\nfm alarm-list to have an uncleared alarm(for test purpose\n100.103 - Memory threshold alarm was used). After 1800sec\nalarm was ignored and patch strategy successfully applied.\nPASSED: On DX system(lab), 4 consecutive patch orchestration\nsuccessfully applied. 750.006 - stale alarm tested.\nPASSED: On DX system, create and apply strategy,\nwith alarm existing on system(not part of ignore list)\nstrategy would wait for 2400sec before timing out.\nPASSED: On DX system, k8s upgrade from v1.21.8 to\nv1.22.5 successfully executed.\n\nCloses-Bug: 2059305\nChange-Id: I7ebaf5a24fa45a7e45f3af7e5ca588ce3ee06156\nSigned-off-by: Vanathi.Selvaraju ","shortMessageHtmlLink":"sw-manager patch-strategy failed to install due to timeout"}},{"before":"3399c7fc541ae3b5bf4e7d2d2d2bc8b4aca21c08","after":"8dfb971980f14b1fdab1ee993216120ee2aa2ccf","ref":"refs/heads/master","pushedAt":"2024-04-09T12:36:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"sw-deploy-strategy to take 'release' parameter\n\nAs part of this task sw-manager sw-deploy-strategy\nis modified to accept 'release' as a mandatory\ninput parameter.controller_type and instance_action\noptional parameters are also added.\n\nThe internal functionalities remain same.\n\nTest Plan:\nPASSED: On DX system, Create sw-deploy strategy\nwithout release input. Strategy creation rejected.\nPASSED: On DX system, Create sw-deploy strategy\nwith invalide release input. Strategy creation\nfailed with 'invalid software release' error.\nPASSED: On DX system, Create sw-deploy strategy\nwith valid release input. Strategy creation\npassed.\nPASSED: Execute upgrade orchestration flow\nsuccessfully with release input parameter.\n\nStory: 2011045\nTask: 49781\n\nChange-Id: If8f72e5b8e1f68602716e32407e0f68702ab7d56\nSigned-off-by: Vanathi.Selvaraju ","shortMessageHtmlLink":"sw-deploy-strategy to take 'release' parameter"}},{"before":"471d1001e0eba0adeba8bdfed020df3f3a0b83f9","after":"3399c7fc541ae3b5bf4e7d2d2d2bc8b4aca21c08","ref":"refs/heads/master","pushedAt":"2024-03-19T21:26:47.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Rename sw-manager upgrade-strategy to sw-deploy-strategy\"","shortMessageHtmlLink":"Merge \"Rename sw-manager upgrade-strategy to sw-deploy-strategy\""}},{"before":"bac2f0a09e35526e0e6cdb6f1b11cde8c848c043","after":"471d1001e0eba0adeba8bdfed020df3f3a0b83f9","ref":"refs/heads/master","pushedAt":"2024-03-19T21:19:14.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Set timeout for KubeHostUpgradeControlPlaneStep to 420s\n\nThe history for KubeHostUpgradeControlPlaneStep timeout of 600s\nwas to give significant headroom in doing control-plane upgrade.\nThis step was known to run long, but we had limited data, so\nwe set the value large. The underlying kubeadm\nUpgradeManifestTimeout was 5 minutes, so timeout larger than\n300s was ineffective.\n\nThis updates KubeHostUpgradeControlPlaneStep timeout\nto 420s. This is intentionally engineered to be larger than\nthe resultant time for sysinv code to reach completion of the\nKubernetes Upgrade control-plane step with retries and\naccounting for failure.\n\nThe timeout is engineered using the following equation.\nThis accounts for retries, hitting kubeadm upgrade timeout\neach try, and some buffer for the sysinv report callback\nmechanism.\n\nnfv_timeout = ImageDownloadTime + retries*\n (UpgradeControlPlaneTimeout + buffer)\n\nFollowing are the engineered parameters:\n\nImageDownloadTime = 0s (images are pre-pull before this step)\nUpgradeManifestTimeout = 3 minutes\nbuffer = 30s\n2 retries\n\nResult:\nEngineered puppet timeout for upgrade control-plane:\n= UpgradeControlPlaneTimeout + buffer = 3*60s + 30s = 210s\n\nEngineered NFV timeout:\n= 0s + 2(180s + 30s) = 420s\n\nTest Plan:\nPASS: Perform orchestrated k8s upgrade, manually STOP kubeadm process\n during k8s upgrade control-plane step. Check logs to verify\n puppet timeout and also verify sysinv attempts retry mechanism\n before nfv timeout.\n\nPartial-Bug: 2056326\n\nChange-Id: I73ab8ea7cd7fc3816372260983c4b54a02cdcc4c\nSigned-off-by: Saba Touheed Mujawar ","shortMessageHtmlLink":"Set timeout for KubeHostUpgradeControlPlaneStep to 420s"}},{"before":"d619a37a6a38b1280e1645617620df5b3101f497","after":"550421627a34fda0e4c331bc4e478d847fa5649b","ref":"refs/heads/r/stx.9.0","pushedAt":"2024-03-15T00:33:47.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Update .gitreview for r/stx.9.0\n\nChange-Id: I01e795310d1c29bce6451ebac700bee7e9bb201b\nSigned-off-by: Scott Little ","shortMessageHtmlLink":"Update .gitreview for r/stx.9.0"}},{"before":"e85f7905c2895d518f6f7096ddbb3af298cf0790","after":"bac2f0a09e35526e0e6cdb6f1b11cde8c848c043","ref":"refs/heads/master","pushedAt":"2024-03-12T14:09:25.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"NFV API to list current strategy type and state.\n\nThis new NFV API will list the current running\nStrategy type and its state.\n\nTest Plan:\nPASSED: On a DX system, Create a strategy of any type.\nAPI should return the strategy type and state.\nPASSED: On a DX system, there are no existing strategies.\nAPI returns none.\nPASSED: Create a Strategy of any type, use REST API\nto get the current active strategy(sample output in\ncomments section).\nPASSED: Orchestrated k8s upgrade with the changes,\n(sample output in the comments section).\nPASSED: Performed three consecutive k8s upgrade\nv1.24.4 - v1.25.3 - v1.26.1 - v1.27.5\n\nStory: 2011045\nTask: 49580\n\nChange-Id: I2e367ccb5f9ff42aa0d912598fb1617a4a7ae0ee\nSigned-off-by: Vanathi.Selvaraju ","shortMessageHtmlLink":"NFV API to list current strategy type and state."}},{"before":"d619a37a6a38b1280e1645617620df5b3101f497","after":"e85f7905c2895d518f6f7096ddbb3af298cf0790","ref":"refs/heads/master","pushedAt":"2024-03-08T19:34:16.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Add retry at nfv orchestration level\"","shortMessageHtmlLink":"Merge \"Add retry at nfv orchestration level\""}},{"before":null,"after":"d619a37a6a38b1280e1645617620df5b3101f497","ref":"refs/heads/r/stx.9.0","pushedAt":"2024-03-07T20:17:04.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Alarm 900.701 raised on failing to remove node taint.\"","shortMessageHtmlLink":"Merge \"Alarm 900.701 raised on failing to remove node taint.\""}},{"before":"d619a37a6a38b1280e1645617620df5b3101f497","after":"0a3943a7e14d01e95ed8ea17042b7fb7c443d2fa","ref":"refs/heads/f/bookworm","pushedAt":"2024-03-06T19:11:47.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Update .gitreview for f/bookworm\n\nChange-Id: Ief8ebf089bdb2b87d1fa593ce23fd83a857d3fb4\nSigned-off-by: Scott Little ","shortMessageHtmlLink":"Update .gitreview for f/bookworm"}},{"before":null,"after":"d619a37a6a38b1280e1645617620df5b3101f497","ref":"refs/heads/f/bookworm","pushedAt":"2024-03-01T17:01:53.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Alarm 900.701 raised on failing to remove node taint.\"","shortMessageHtmlLink":"Merge \"Alarm 900.701 raised on failing to remove node taint.\""}},{"before":"b732e56b43576fffd601175f1abad50399ed3c9c","after":"d619a37a6a38b1280e1645617620df5b3101f497","ref":"refs/heads/master","pushedAt":"2024-02-27T17:42:42.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Alarm 900.701 raised on failing to remove node taint.\"","shortMessageHtmlLink":"Merge \"Alarm 900.701 raised on failing to remove node taint.\""}},{"before":"d730d8edc291a7a2f247f873359c832ad3909d36","after":"b732e56b43576fffd601175f1abad50399ed3c9c","ref":"refs/heads/master","pushedAt":"2024-02-16T01:35:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Account for new Kubernetes upgrade statuses\n\nUpdate the Kubernetes upgrade orchestration code to account for two new\nstatuses: upgrade-starting and upgrade-starting-failed.\n\nThe new statuses were introduced to support updating StarlingX\napplications during the kube-upgrade-start step.\n\nTest Plan:\nPASS: build-pkgs -a && build-image\nPASS: sw-manager kube-upgrade-strategy create --to-version v1.27.5\n sw-manager kube-upgrade-strategy apply\n Check if Kubernetes upgrade started and finished successfully.\n sw-manager kube-upgrade-strategy delete\nPASS: sw-manager kube-upgrade-strategy create --to-version v1.27.5\n sw-manager kube-upgrade-strategy apply\n sw-manager kube-upgrade-strategy abort\n Check if Kubernetes upgrade was successfully aborted.\n sw-manager kube-upgrade-strategy delete\nPASS: Fresh install AIO-SX\n Create a platform-integ-apps updated tarball without the\n metadata.yaml file and copy it over to\n /usr/local/share/applications/helm/.\n sw-manager kube-upgrade-strategy create --to-version v1.27.5\n sw-manager kube-upgrade-strategy apply\n Confirm that the Kubernetes upgrade failed\n Check if Kubernetes upgrade was successfully aborted.\n sw-manager kube-upgrade-strategy delete\nPASS: Fresh install AIO-DX\n Create a platform-integ-apps updated tarball without the\n metadata.yaml file and copy it over to\n /usr/local/share/applications/helm/.\n sw-manager kube-upgrade-strategy create --to-version v1.27.5\n sw-manager kube-upgrade-strategy apply\n Confirm that the Kubernetes upgrade failed\n sw-manager kube-upgrade-strategy delete\n Copy a working platform-integ-apps tarball to\n /usr/local/share/applications/helm/.\n sw-manager kube-upgrade-strategy create --to-version v1.27.5\n sw-manager kube-upgrade-strategy apply\n Confirm that the Kubernetes upgrade was resumed and successfully\n finished.\nPASS: Fresh install AIO-SX with Kubernetes 1.24.4\n sw-manager kube-upgrade-strategy create --to-version v1.27.5\n sw-manager kube-upgrade-strategy apply\n Check if Kubernetes upgrade started and finished successfully.\n\nStory: 2010929\nTask: 49461\n\nDepends-on: https://review.opendev.org/c/starlingx/config/+/905005\n\nChange-Id: I1a8b86c9ecf8cc21a9cb25ee57d6930944cef261\nSigned-off-by: Igor Soares ","shortMessageHtmlLink":"Account for new Kubernetes upgrade statuses"}},{"before":"8af76f954d79b3d8eacc2e0d5fc45c61349031df","after":"d730d8edc291a7a2f247f873359c832ad3909d36","ref":"refs/heads/master","pushedAt":"2024-02-05T13:40:09.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Ignore PTP alarm in vim strategies\n\nThis commit ignores the PTP alarm for SyncE in all the vim strategies\nas it should not impact related operations.\n\nTest-plan:\n1. Manually raise 100.119 alarm by fmClientCli\n2. Verify kube-rootca-update and system-config-update strategies can\nbe created/applied/deleted successfully along with the 100.119 alarm.\n\nCloses-bug: 2051950\nChange-Id: Ie2cc570c28de95802ff1b88e30f3c9f562b3c892\nSigned-off-by: Yuxing Jiang ","shortMessageHtmlLink":"Ignore PTP alarm in vim strategies"}},{"before":null,"after":"8af76f954d79b3d8eacc2e0d5fc45c61349031df","ref":"refs/heads/f/kernel-6.6","pushedAt":"2024-01-25T16:31:08.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Nfv upgrade orchestration for kube-upgrade-storage\"","shortMessageHtmlLink":"Merge \"Nfv upgrade orchestration for kube-upgrade-storage\""}},{"before":"42442c85d9d351de72d2c20d157866a0c8a1c6ff","after":"8af76f954d79b3d8eacc2e0d5fc45c61349031df","ref":"refs/heads/master","pushedAt":"2024-01-09T22:09:45.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Merge \"Nfv upgrade orchestration for kube-upgrade-storage\"","shortMessageHtmlLink":"Merge \"Nfv upgrade orchestration for kube-upgrade-storage\""}},{"before":"71406be649e3dea25c0bd88ae187cd9650d15e79","after":"42442c85d9d351de72d2c20d157866a0c8a1c6ff","ref":"refs/heads/master","pushedAt":"2024-01-02T19:44:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Optimize kubelet upgrade phase using VIM orchestrator.\n\nOptimizing kubelet upgrade by reducing the wait\ntime and adding in more logs for debugging.The\nwait time is removed as we have the additional\nkubelet state check in place (Closes-Bug: 2044209)\nand an existing timeout of 900secs.\n\nTest Plan:\nPASSED: On a DX system, removed the wait time of 60 sec\nand tested 3 consecutive k8s upgrade thrice.\nPASSED: On a DX system, tweaked the code and tested\non the kubelet upgrade retry timeout(900sec).\nPASSED: On a DX system, tweaked code and tested\nthe existing behaviour that retry is not\noccuring in case of failure.\n\nCloses-Bug: 2045776\n\nChange-Id: I321d7eae5ef7ebd29c1c6aca97992e3e20acb457\nSigned-off-by: Vanathi.Selvaraju ","shortMessageHtmlLink":"Optimize kubelet upgrade phase using VIM orchestrator."}},{"before":"6dba3df3e3c4e5f4ae20ae0c4a48ae72e6d6e274","after":"8256c9527313be598421c46ccbdc2033cf8dcd2f","ref":"refs/heads/f/antelope","pushedAt":"2023-12-18T07:13:18.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Update .gitreview for f/antelope\n\nChange-Id: I8a661eb370710417c2845bf7a6e28c8720462a60\nSigned-off-by: Scott Little ","shortMessageHtmlLink":"Update .gitreview for f/antelope"}},{"before":"cdd758efb72d7a17d9f69e79475fdab0791fafc2","after":"71406be649e3dea25c0bd88ae187cd9650d15e79","ref":"refs/heads/master","pushedAt":"2023-11-23T20:04:28.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"K8s upgrade failed in host-unlock phase\n\nK8s upgrade failed in the host-unlock phase\nas kubelet upgrade was ongoing, VIM tries\nto unlock the host before completion of\nkubelet upgrade.\n\nTest Plan:\nPASSED: On a DX system, apply the fix and trigger\nK8s upgrade.\nPASSED: On a SX system, do three consecutive k8s upgrade.\nPASSED: On DX system ,two consecutive k8s upgrade.\n\nCloses-Bug: 2044209\n\nChange-Id: If4bcabcba6aabd1aee6918d73fd6994e94f0b1f8\nSigned-off-by: Vanathi.Selvaraju ","shortMessageHtmlLink":"K8s upgrade failed in host-unlock phase"}},{"before":"9feef4232d378151f52cc56f9d0fe2711b745559","after":"cdd758efb72d7a17d9f69e79475fdab0791fafc2","ref":"refs/heads/master","pushedAt":"2023-11-19T02:16:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Post K8s upgrade DC system controller swacts in a loop\n\nAfter K8s upgrade from 1.22 to 1.23 the system\nswacts in a loop, this occurs as an atrribute\nof the VIM object is not available leading to\nmultiple restarts of VIM service resulting\nin swact.\n\nTest Plan:\nPASSED: Induce condition Kube upgrade object null state\ncausing vim restarts, apply fix, system stabilizes.\n\nCloses-Bug: 2043859\n\nChange-Id: Iccb3106cade1308aa6e9232013366c2b9181557b\nSigned-off-by: Vanathi.Selvaraju ","shortMessageHtmlLink":"Post K8s upgrade DC system controller swacts in a loop"}},{"before":"6dba3df3e3c4e5f4ae20ae0c4a48ae72e6d6e274","after":"9feef4232d378151f52cc56f9d0fe2711b745559","ref":"refs/heads/master","pushedAt":"2023-08-31T15:56:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"sw-manager fails with SSL and CA Cert provided.\n\nWhen sw-manager is used through a secure connection (https\nenabled) either with the remote CLI or within the cluster\nvia the public interface, the operation fails if the\nCertificate Authority's cert is not included among the\nsystem's trusted CAs.\n\nThe sw-manager client lacks implemented methods for\nreferencing a local Certificate Authority Cert during calls.\nTherefore, if the CA is not among the system's trusted CAs,\nall calls made by sw-manager's CLI will fail since\nauthentication in Keystone will also fail.\n\nOther CLIs like fm or platform allow referencing a CA Cert\nvia the \"REQUESTS_CA_BUNDLE\" environment variable. The fix\ninvolves loading, if defined, the CA Cert referenced by\nsuch an environment variable, and adjusting SSL calls to\nverify connections using the provided CA Cert.\n\nTest Plan:\n PASS Fresh Install SX Env\n\n PASS Source openrc.sh file (internal interface).\n PASS sw-manager patch-strategy show\n\n PASS Enable secure mode (https)\n PASS Download OpenStack RC File from Horizon.\n PASS Source RC file inside cluster (public interface).\n PASS Set REQUESTS_CA_BUNDLE with CA-Cert path.\n PASS sw-manager patch-strategy show\n\n PASS Enable secure mode (https)\n PASS Download OpenStack RC File from Horizon.\n PASS Install remote CLI (custom container with changes)\n PASS Source downloaded RC file\n PASS Set REQUESTS_CA_BUNDLE with CA-Cert path.\n PASS sw-manager patch-strategy show\n\nCloses-bug: 2033561\n\nChange-Id: If5b70714cde09bd8c329b976a8148daee9001415\nSigned-off-by: Jorge Saffe ","shortMessageHtmlLink":"sw-manager fails with SSL and CA Cert provided."}},{"before":null,"after":"6dba3df3e3c4e5f4ae20ae0c4a48ae72e6d6e274","ref":"refs/heads/f/antelope","pushedAt":"2023-08-09T20:01:46.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"starlingx-github","name":null,"path":"/starlingx-github","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/60620236?s=80&v=4"},"commit":{"message":"Implement system_config_update orchestration\n\nThis commit adds VIM orchestration for system config update to drive the\nhost swact/lock/unlock once these operations are expected to update the\nsystem config.\n\nCLI: sw-manager kube-rootca-update-strategy\n apply create delete show\n\nTest plan:\n1. Create a system config udpate strategy successfully. --passed\n2. Create a system config update strategy failed if the host resource\ndoesn't exist. --passed\n3. Create a system config update strategy failed if an unexpected alarm\nexists and the strategy alarm restrictions is set as strict. --passed\n4. Create a system config update strategy successfully if an unexpected\nalarm exists and the strategy alarm restrictions is set as relax.\n--passed\n5. Create a system config update strategy failed if a controller offline\nin a DX system. --passed\n6. Create a system config update strategy failed if a storage offline in\na standard system. --passed\n7. Create a system config update strategy successfully if a worker\noffline in a standard system. --passed\n8. Apply a system config update strategy successfully. --passed\n9. Apply a system config update strategy failed if a host failed to\nlock. --passed\n10. Delete a system config update strategy successful if a the strategy\nis complete or failed. --passed\n11. Create a system config update strategy with strategy not required\nfor the host in k8s, verify the host is excluded from the strategy.\n\nStory: 2010719\nTask: 47910\n\nChange-Id: I052bc5b2004f17de870a81c523d0a1f4e422a902\nSigned-off-by: Yuxing Jiang ","shortMessageHtmlLink":"Implement system_config_update orchestration"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEXFE1WwA","startCursor":null,"endCursor":null}},"title":"Activity ยท starlingx/nfv"}