)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9926,"name":"John Kung","email":"john.kung@windriver.com","username":"jkung"},"change_message_id":"f99e807a8703958948b8111a62172fd4fcda5d71","unresolved":true,"context_lines":[{"line_number":9,"context_line":"This reverts commit f096dcf15903a3b962182f5b85d173a0b1523dd2."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Reason for revert: Issues were found in bootstrap phase."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Change-Id: I2fb58880a847d89338e4483d6abb4c65e9f3a3a3"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"fd4d32d6_cbe7e88e","line":12,"updated":"2021-12-15 17:20:36.000000000","message":"This isnt currently linked to any LP","commit_id":"218387d74b6c6bfbd45f417ee1299a53ddee706c"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":28558,"name":"Ghada Khalil","email":"ghada.khalil@windriver.com","username":"gkhalil"},"change_message_id":"adff2394ae0c215b97130a6b071866ed25e5eb16","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f96e8eb3_903094f1","updated":"2021-12-15 17:30:24.000000000","message":"What is the LP describing the issue introduced by the original commit? Why is this being seen now when the original commit was merged weeks ago?","commit_id":"218387d74b6c6bfbd45f417ee1299a53ddee706c"},{"author":{"_account_id":30852,"name":"Dan Voiculeasa","email":"Dan.Voiculeasa@windriver.com","username":"dvoicule"},"change_message_id":"e380c0ffc86a2d30925dc856cf37b4788630bab4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c47b2e33_6e310682","in_reply_to":"3f96dad4_3101523b","updated":"2021-12-15 18:45:49.000000000","message":"There is no need for an LP, the original one can be used, there is no new issue.\nI discovered during Debian integration when bootstrap reached that point. Seems StarlingX load wasn\u0027t tested since 26th, maybe more.\n\nAl, the capabilities were always there. I checked the 24th Nov load sysinv-api patch call during bootstrap. Called the logic of the new code with the params from 24th which failed, which would have failed the bootstrap. \n\n24th load:\ncontroller-0:~$ cat /etc/build.info \n###\n### StarlingX\n###     Built from master\n###\n\nOS\u003d\"centos\"\nSW_VERSION\u003d\"21.12\"\nBUILD_TARGET\u003d\"Host Installer\"\nBUILD_TYPE\u003d\"Formal\"\nBUILD_ID\u003d\"20211124T041933Z\"\n\nJOB\u003d\"STX_build_layer_flock_master_master\"\nBUILD_BY\u003d\"starlingx.build@cengn.ca\"\nBUILD_NUMBER\u003d\"683\"\nBUILD_HOST\u003d\"starlingx_mirror\"\nBUILD_DATE\u003d\"2021-11-24 04:19:33 +0000\"\n\nFLOCK_OS\u003d\"centos\"\nFLOCK_JOB\u003d\"STX_build_layer_flock_master_master\"\nFLOCK_BUILD_BY\u003d\"starlingx.build@cengn.ca\"\nFLOCK_BUILD_NUMBER\u003d\"683\"\nFLOCK_BUILD_HOST\u003d\"starlingx_mirror\"\nFLOCK_BUILD_DATE\u003d\"2021-11-24 04:19:33 +0000\"\n\nDISTRO_OS\u003d\"centos\"\nDISTRO_JOB\u003d\"STX_build_layer_distro_master_master\"\nDISTRO_BUILD_BY\u003d\"starlingx.build@cengn.ca\"\nDISTRO_BUILD_NUMBER\u003d\"701\"\nDISTRO_BUILD_HOST\u003d\"starlingx_mirror\"\nDISTRO_BUILD_DATE\u003d\"2021-11-24 02:33:57 +0000\"\n\nCOMPILER_OS\u003d\"centos\"\nCOMPILER_JOB\u003d\"STX_build_layer_compiler_master_master\"\nCOMPILER_BUILD_BY\u003d\"starlingx.build@cengn.ca\"\nCOMPILER_BUILD_NUMBER\u003d\"764\"\nCOMPILER_BUILD_HOST\u003d\"starlingx_mirror\"\nCOMPILER_BUILD_DATE\u003d\"2021-11-23 00:00:00 +0000\"\n\nansible.log:\n2021-12-03 12:54:31,424 p\u003d10601 u\u003dsysadmin |  TASK [bootstrap/persist-config : Saving config in sysinv database] *************\n2021-12-03 12:54:31,424 p\u003d10601 u\u003dsysadmin |  Friday 03 December 2021  12:54:31 +0000 (0:00:00.330)       0:07:01.420 *******\n\n\ncontroller-0:~$ cat /var/log/sysinv-api.log  | grep capabilities\nsysinv 2021-12-03 12:54:36.437 82601 INFO sysinv.api.hooks.auditor [req-5da35f5c-e789-421f-b5ea-dd169974d2db c01931b003e64b98885fd4bdf1e5ae58 fd4f5829a7d5428aacd09b18695f7fd2] ::ffff:127.0.0.1 \"PATCH /v1/isystems/981ba2b2-f802-4345-8931-4081e66b05b5 HTTP/1.0\" status: 200 len: 1089 time: 0.208024024963 POST: [{u\u0027path\u0027: u\u0027/system_mode\u0027, u\u0027value\u0027: u\u0027simplex\u0027, u\u0027op\u0027: u\u0027replace\u0027}, {u\u0027path\u0027: u\u0027/region_name\u0027, u\u0027value\u0027: u\u0027RegionOne\u0027, u\u0027op\u0027: u\u0027replace\u0027}, {u\u0027path\u0027: u\u0027/service_project_name\u0027, u\u0027value\u0027: u\u0027services\u0027, u\u0027op\u0027: u\u0027replace\u0027}, {u\u0027path\u0027: u\u0027/distributed_cloud_role\u0027, u\u0027value\u0027: None, u\u0027op\u0027: u\u0027replace\u0027}, {u\u0027path\u0027: u\u0027/capabilities\u0027, u\u0027value\u0027: {u\u0027https_enabled\u0027: False, u\u0027vswitch_type\u0027: u\u0027none\u0027, u\u0027region_config\u0027: False, u\u0027sdn_enabled\u0027: False, u\u0027shared_services\u0027: u\u0027[]\u0027}, u\u0027op\u0027: u\u0027replace\u0027}, {u\u0027path\u0027: u\u0027/system_type\u0027, u\u0027value\u0027: u\u0027All-in-one\u0027, u\u0027op\u0027: u\u0027replace\u0027}, {u\u0027path\u0027: u\u0027/timezone\u0027, u\u0027value\u0027: u\u0027UTC\u0027, u\u0027op\u0027: u\u0027replace\u0027}] host:127.0.0.1:6385 agent:Python-httplib2/0.9.2 (gzip) user: admin tenant: admin domain: Default\n\nA snippet of the investigation was shown in: https://review.opendev.org/c/starlingx/config/+/819038","commit_id":"218387d74b6c6bfbd45f417ee1299a53ddee706c"},{"author":{"_account_id":28558,"name":"Ghada Khalil","email":"ghada.khalil@windriver.com","username":"gkhalil"},"change_message_id":"3210addd4d7a39501e15d682d310b8a96b860d88","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"cb2f9b53_2f20046c","in_reply_to":"c47b2e33_6e310682","updated":"2021-12-15 19:19:09.000000000","message":"Actually we do need LPs for any newly reported issues. That\u0027s the process we follow, especially when the issue reported is not exactly, the one initially fixed. Also stx sanity is run daily and has been green for several runs in Dec, so the statement that \"seems StarlingX load wasn\u0027t tested since 26th, maybe more.\" is not accurate. Based on the fact, that the issue is reported from Debain testing, this is likely the contributing factor here","commit_id":"218387d74b6c6bfbd45f417ee1299a53ddee706c"},{"author":{"_account_id":33667,"name":"Rafael Camargos","email":"RafaelLucas.Camargos@windriver.com","username":"rcamargo"},"change_message_id":"e1e06073ffe40ad5c45553eb080860121daf7a73","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3f96dad4_3101523b","in_reply_to":"f96e8eb3_903094f1","updated":"2021-12-15 17:55:38.000000000","message":"The issue was reported on https://review.opendev.org/c/starlingx/config/+/819038 by Dan Voiculeasa and Al Bailey. I\u0027ve dumped the report in the LP below and linked it here.\n\nhttps://bugs.launchpad.net/starlingx/+bug/1954940","commit_id":"218387d74b6c6bfbd45f417ee1299a53ddee706c"},{"author":{"_account_id":15435,"name":"Al Bailey","email":"albailey1974@gmail.com","username":"albailey"},"change_message_id":"11e6d8a8d2c1e33d0bee9317b808466780c63ca8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f5813ebd_a1d2d28a","updated":"2021-12-15 18:21:55.000000000","message":"I believe both the revert (and/or) the fix will need to be ported to stx/6 branch if we determine that whatever the steps to reproduce this issue are things that a typical user will do  (passing capabilities into the bootstrap)","commit_id":"bf8be875e7883000d2b87dad00161a6a3369f8ef"}]}