MR: Pending <!-- The first line of the MR must be one of the following: 1. `MR: Pending` 2. `MR: <MR link with trailing +>`, and the first description line of the MR should be `Issue: <Issue link with trailing +>` 3. `MR: No MR` For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#1-to-1-relationship-of-issues-to-mrs --> <!-- The following sections should be filled out as part of the refinement process before the issue is prioritized. For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#2-pre-iteration-planning-meeting --> ## Description The following discussion from !139209 should be addressed: - [ ] @cwoolley-gitlab started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/139209#note_1706489871): (+1 comment) > @vtak When testing this locally, I got the following error in the agent logs: > > ``` > {"level":"error","time":"2023-12-22T18:42:16.853-0700","msg":"Error when applying config","mod_name":"remote_development","error":"task failed (action: \"Inventory\", name: \"inventory-add-0\"): Operation cannot be fulfilled on configmaps \"workspace-4-1-vhwjm8-workspace-inventory\": the object has been modified; please apply your changes to the latest version and try again","inventory_name":"workspace-4-1-vhwjm8-workspace-inventory","inventory_namespace":"gl-rd-ns-4-1-vhwjm8","agent_id":4} > ``` > > I had two running workspaces at the time, and I was connected to one of them, but this error seemed to only happen for _ONE_ of the workspaces, and it was not the one that I was connected to. > > This happened twice, both times I updated the `default_resources_per_workspace_container.requests`. > > However, it still seemed to get the changes applied to both containers in each workspace pod. ## Acceptance Criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [Describe another requirement needed to complete this issue.] - [ ] [Add additional acceptance criteria as needed.] ## Technical Requirements TODO: Fill out or delete [If applicable, please list out any technical requirements for this feature/enhancement.] ## Design Requirements TODO: Fill out or delete [If applicable, please provide a link to the design specifications for this feature/enhancement.] ## Impact Assessment TODO: Fill out or delete [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.] ## User Story TODO: Fill out or delete [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.] <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#-remote-development-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->