Deployed MR's changes were not applied
Summary
During production#6325 (closed) (10 Feb 2022), we found that the changes in gitlab-org/gitlab!79815 (merged) had not been applied on gprd even though the MR was deployed as part of the 14.8.202202032350-4d6a836c3dd.b7e215b24d8
package (deployed to gprd on 4 Feb 2022).
iwiedler@file-01-stor-gprd.c.gitlab-production.internal:~$ ls -lah /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/ci/parsers/security/validators/schemas/
total 84K
drwxr-xr-x 2 root root 4.0K Feb 10 09:02 .
drwxr-xr-x 3 root root 4.0K Feb 10 09:02 ..
lrwxrwxrwx 1 root root 83 Feb 2 06:33 14.0.0 -> ../../../../../../../ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/14.0.0
lrwxrwxrwx 1 root root 83 Feb 2 06:33 14.0.1 -> ../../../../../../../ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/14.0.1
lrwxrwxrwx 1 root root 83 Feb 2 06:33 14.0.2 -> ../../../../../../../ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/14.0.2
lrwxrwxrwx 1 root root 83 Feb 2 06:33 14.0.3 -> ../../../../../../../ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/14.0.3
lrwxrwxrwx 1 root root 83 Feb 2 06:33 14.0.4 -> ../../../../../../../ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/14.0.4
lrwxrwxrwx 1 root root 83 Feb 2 06:33 14.0.5 -> ../../../../../../../ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/14.0.5
lrwxrwxrwx 1 root root 83 Feb 2 06:33 14.0.6 -> ../../../../../../../ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/14.0.6
lrwxrwxrwx 1 root root 83 Feb 2 06:33 14.1.0 -> ../../../../../../../ee/lib/ee/gitlab/ci/parsers/security/validators/schemas/14.1.0
Related Incident(s)
Originating issue(s): production#6325 (closed)
Desired Outcome/Acceptance criteria
Understand what prevented the change from being applied, and fix any bugs.
Associated Services
Corrective Action Issue Checklist
-
link the incident(s) this corrective action arose out of -
give context for what problem this corrective action is trying to prevent from re-occurring -
assign a severity label (this is the highest sev of related incidents, defaults to 'severity::4') -
assign a priority (this will default to 'priority::4')
Edited by Reuben Pereira