56 lines
2.0 KiB
Plaintext
56 lines
2.0 KiB
Plaintext
{
|
|
"comments": [
|
|
{
|
|
"unresolved": false,
|
|
"key": {
|
|
"uuid": "b9823b5e_7de6836c",
|
|
"filename": "/PATCHSET_LEVEL",
|
|
"patchSetId": 2
|
|
},
|
|
"lineNbr": 0,
|
|
"author": {
|
|
"id": 28464
|
|
},
|
|
"writtenOn": "2024-04-01T14:27:16Z",
|
|
"side": 1,
|
|
"message": "Please note that upgrades handling is implemented in a \u0027shortly to come\u0027 alarm introduction and handling update.\n\nNote: There is no plan to patch back this update.",
|
|
"revId": "7b777b76da4c87dbbad2848528c2516808d92fda",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
|
},
|
|
{
|
|
"unresolved": true,
|
|
"key": {
|
|
"uuid": "58cbed8d_e92589b4",
|
|
"filename": "fm-doc/fm_doc/events.yaml",
|
|
"patchSetId": 2
|
|
},
|
|
"lineNbr": 581,
|
|
"author": {
|
|
"id": 9926
|
|
},
|
|
"writtenOn": "2024-04-03T13:33:28Z",
|
|
"side": 1,
|
|
"message": "note that this could affect nfv orchestration \n\ne.g. certain alarms are allowed during patch orchestration https://opendev.org/starlingx/nfv/src/commit/3399c7fc541ae3b5bf4e7d2d2d2bc8b4aca21c08/nfv/nfv-vim/nfv_vim/strategy/_strategy.py#L1387",
|
|
"revId": "7b777b76da4c87dbbad2848528c2516808d92fda",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
|
},
|
|
{
|
|
"unresolved": false,
|
|
"key": {
|
|
"uuid": "9eb07285_18e81d14",
|
|
"filename": "fm-doc/fm_doc/events.yaml",
|
|
"patchSetId": 2
|
|
},
|
|
"lineNbr": 581,
|
|
"author": {
|
|
"id": 28464
|
|
},
|
|
"writtenOn": "2024-04-08T10:46:50Z",
|
|
"side": 1,
|
|
"message": "Yes, that was why it was made management affecting. The pxeboot network is needed for patching/upgrade.\n\nIf there is a specific orchestration strategy you think this alarm should be ignored with please state. Note, alarm is cleared when locked.",
|
|
"parentUuid": "58cbed8d_e92589b4",
|
|
"revId": "7b777b76da4c87dbbad2848528c2516808d92fda",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
|
}
|
|
]
|
|
} |