)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28223,"name":"Cedric Jeanneret","display_name":"cjeanner (Tengu)","email":"cjeanner@redhat.com","username":"cjeanner"},"change_message_id":"425e8982d34cdb26cf70c7daa223711c537b31cf","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"81f0c9c7_5f413ced","updated":"2022-07-11 09:37:12.000000000","message":"That\u0027s an open door to broken host imho, and a lot of useless support... There are some constraints with installed packages on the host vs container.\nIMHO, the right way would be: scale out, run update.\nThis would ensure consistency across the deployed OC.\n\nAnother solution would be to update the OC image before they are used for new hosts. That should be easily possible, especially for cases where CU are using satellite or any other tool ensuring consistency across packages on an infra.","commit_id":"3fbf8173113f41fdb2fb56fb06ee3c0c80ba2c07"},{"author":{"_account_id":7144,"name":"James Slagle","email":"jslagle@redhat.com","username":"slagle"},"change_message_id":"f001c44ed5fb2baea3847ed0c0a84da0e29a9595","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"f3c0e263_e0427cd2","updated":"2022-06-14 20:04:52.000000000","message":"i\u0027m not sure about this. for one, package update is necessarily related to satellite registration, i\u0027m not sure we want this logic here. also, we can\u0027t just allow operators to update packages whenever as it typically requires some orchestration. what if they unexpectedly pull a new kernel?\n\ni understand they have to opt-in to this variable, but it\u0027s also likely operators could forget they have it set in an environment file.","commit_id":"3fbf8173113f41fdb2fb56fb06ee3c0c80ba2c07"},{"author":{"_account_id":7144,"name":"James Slagle","email":"jslagle@redhat.com","username":"slagle"},"change_message_id":"e8a5cd25b9ce5b05daaa81a35672ece4ed3652be","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"e818b301_8926ba03","in_reply_to":"9addd22b_95cd1635","updated":"2022-06-21 11:42:03.000000000","message":"i think there are a lot of unknowns here. However the end result is not all that different from using pre-deployed nodes with a base image and satellite, and getting the latest packages on a deployment. I\u0027d still want to see some input from update/upgrades here if this feature is something they want to take on supporting, as I think just adding it to this role feels a little backdoor\u0027ish.","commit_id":"3fbf8173113f41fdb2fb56fb06ee3c0c80ba2c07"},{"author":{"_account_id":7130,"name":"David Hill","email":"davidchill@hotmail.com","username":"dhill"},"change_message_id":"120675de6c4d48a58eba154256716f7f7a8fe8d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"9addd22b_95cd1635","in_reply_to":"f3c0e263_e0427cd2","updated":"2022-06-14 23:18:37.000000000","message":"Well it\u0027s mostly our customers using Satellite or Capsules that are requesting this in order to avoid a perhaps minor update after scaling nodes ... As they argue that they might have to reboot the nodes after and that after the first boot and registration I think we usually reboot at deployment time, this would probably install at most a few packages that would have been added to their satellite view because of async releases that are not always included in the overcloud image.   I feel the same way about this change as you do and I\u0027m concerned about operators forgeting about this setting and installing more packages than they would really have wanted to install but the thing is, they\u0027re really adament of this feature.  We can drop it if you\u0027d prefer.","commit_id":"3fbf8173113f41fdb2fb56fb06ee3c0c80ba2c07"}],"tasks/satellite.yml":[{"author":{"_account_id":7353,"name":"Kevin Carter","email":"kevin@cloudnull.com","username":"cloudnull"},"change_message_id":"6f29f19960121283b8cb5f6a4394a23e3fef2cff","unresolved":true,"context_lines":[{"line_number":118,"context_line":"  yum:"},{"line_number":119,"context_line":"    name: \"*\""},{"line_number":120,"context_line":"    state: latest"},{"line_number":121,"context_line":"  when:"},{"line_number":122,"context_line":"    - rhsm_package_update is defined and rhsm_package_update|bool \u003d\u003d True"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"372e3544_e45c7cfc","line":122,"range":{"start_line":121,"start_character":0,"end_line":122,"end_character":73},"updated":"2022-05-31 12:21:05.000000000","message":"I\u0027d write this as \n\n  when:\n    - rhsm_package_update is defined\n    - rhsm_package_update | bool","commit_id":"7cc48415ca489494cc181cd5ea22eba6fe62145b"}]}