Gitlab-ci Failure for sub-module update #49
Closed
opened 2025-02-25 18:31:57 +00:00 by jon_nfc
·
39 comments
No Branch/Tag Specified
Labels
Clear labels
Bug
Used in discussion about a bug in comments or commits
CVE-2023-5764
Denotes items related to the CVE
CodeReview
Used in comments (issues/MR/commits) to denote code review related items
Documentation
Documentation items
Feature
Used in discussion about a Feature in comments or commits
Lint
Used in comments (issues/MR/commits) to denote lint tasks todo, done, fixed
Privacy
Used in comments (issues/MR/commits) to denote privacy related items
Security
Used in comments (issues/MR/commits) to denote Security related items
breaking-change
label used to denote that the issue/Merge Request does/will introduce a breaking change
bug::reproducable
Given to an issue when the bug has been confirmed as re-producable. Can also be used in comments and commits.
bug::unable to reproduce
Given to an issue when the bug that is not able to be reproduced. Can also be used in comments and commits.
code review::complete
code review::not started
code review::rejected
code review::underway
difficulty::Full Development
Level 3. Difficulty representing that the task to complete must be planned and created.
difficulty::Good First Issue
Level 1. Difficulty representing that the task is very simple and with limited knowledge can be completed.
difficulty::Prior Knowledge
Level 2. Difficulty representing that the task requires some prior knowledge of either the technology or the project for task completion.
documentation::complete
Issues, Merge Requests
documentation::no change required
Issues, Merge Requests and used to denote no documentation changes required
documentation::not started
Issues, Merge Requests
documentation::stalled
Issues, Merge Requests
documentation::underway
Issues, Merge Requests
impact::0
impact::1
impact::2
impact::3
impact::4
impact::5
ops::ansible-roles
OPS project tag
ops::automation
ops::gitlab-ci
OPS project tag
ops::marcas
OPS project tag
ops::python-gitlab-management
OPS project tag
ops::website
priority::0
priority::1
priority::2
priority::3
priority::4
priority::5
stage::Ready for Development
stage::develop
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::feedback required
stage::planning
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::test
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stale
Label given to issues/merge requests that are considered stale due to no collaboration and is a mark for closure.
triage
Tag given to issues/merge requests requiring triaging by the team.
triage::not_confidential
This tag is given by the triage bot so that URLs can be added to an issue/comment. A triage policy for NFC wide should remove this label.
type::CI / CD
type::automation
This type is used to denote an automation job
type::bug
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::compliance
type::discussion
Type for Issues. Can also be used in discussion in comments.
type::documentation
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::feature
type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::invalid
label given to tickets that require no action or are deem as invalid.
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::question
Type for Issues. Can also be used in discussion in comments.
type::security
Type for Issues and Merge Requests.
type::specification
Design specification
workflow::complete
Issues, Merge Requests
workflow::not ready
workflow::not ready::blocked
workflow::not started
Issues, Merge Requests
workflow::ready to commence
Issues, Merge Requests
workflow::stalled
Label given to issues/merge requests where no work has occured in x days iaw triage policy.
workflow::underway
Issues, Merge Requests
workflow::underway::develop
Area/CI-CD
Documentation changes
Area/Documentation
Documentation changes
Area/Security
This is security issue
Area/Testing
Issue or pull request related to testing
Bug
Failure to Confirm
Bug exists due to not confirming/testing code
Bug
Regression
THe bug is a regression of a feature
Bug
To be Confirmed
This bug is not confirmed
Bug
Unable to Reproduce
A developer can not re-create/re-produce the bug
Compat/Breaking
Breaking change that won't be backward compatible
Impact
Critical
1
The impact is critical in that it is blocking or prevents usage.
Impact
High
2
The impact requires that changes be made for continuted usage.
Impact
Low
4
The impact requires the user approach from a different angle for continued usage.
Impact
Medium
3
The impact requires a workaround for continued usage.
Impact
Very Low
5
The impact has a slight effect on usage.
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Priority
Very High
1
The priority is critical
Priority
Very Low
5
The priority is very low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Type
Bug
Something is not working
Type
Epic
Epic User Story
Type
Feature
Feature / Module
Type
Incident
Something occured related to a service
Type
RFE
Request for Enhancement
Type
Task
A work item that must be done
Urgency
Low
4
Prioritize this amoungst your list of things to do.
Urgency
Major
1
Urgency is so high it should have been dealt with last week.
Urgency
Medium
3
Start as soon as possible.
Urgency
Very High
2
Urgency is high enough to warrant near immediate commencement.
Urgency
Very Low
5
Add this to your list of things to do.
No Label
Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/gitlab-ci#49
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Gitlab-ci had an update. All subsequent jobs that conducted a gist submodule update failed.
Failed on stage
TASK [git_configuration : Comment on Merge Request]error unknown due to no logging being available due to secret leak.Links
879c3e18fb/tasks/submodule_update.yaml (L587-600)assigned to @jon_nfc
mentioned in merge request docker-mail!67
mentioned in merge request nofusscomputing/ops!83
mentioned in merge request nofusscomputing/projects/ansible/collections/phpipam_scan_agent!21
mentioned in merge request nofusscomputing/projects/ansible/nfc_glpi!23
mentioned in merge request nofusscomputing/projects/ansible/git_configuration!152
mentioned in merge request kubernetes_monitoring!26
mentioned in merge request docker-glpi!41
mentioned in merge request docker-bind!24
mentioned in merge request nofusscomputing/projects/ansible/docker_management!38
mentioned in merge request nofusscomputing/projects/ansible/common!24
mentioned in merge request docker-buildx-qemu!46
mentioned in merge request nofusscomputing/projects/ansible/ansible-roles!192
mentioned in merge request nofusscomputing/projects/ansible/collections/firewall!32
mentioned in merge request nofusscomputing/projects/ansible/ansible_playbooks!110
mentioned in merge request nofusscomputing/projects/ansible/ansible_test!24
mentioned in merge request nofusscomputing/projects/ansible/ansible_docker_os!28
changed the severity to Critical - S1
changed due date to February 28, 2025
added 30s of time spent
mentioned in commit nofusscomputing/projects/ansible/git_configuration@a83a9ce4f5e854b72b1381a4429a0ac4a497389c
bug found in task duration calculation see nofusscomputing/projects/ansible/git_configuration@a83a9ce4f5e854b72b1381a4429a0ac4a497389c
mentioned in merge request nofusscomputing/projects/ansible/execution_environment!267
fix pushed through to ansible-ee in nofusscomputing/projects/ansible/execution_environment!267
added 2h of time spent
subtracted 1h of time spent
mentioned in merge request nofusscomputing/infrastructure/configuration-management/itil_runbooks!8
mentioned in merge request kubernetes_monitoring!27
it's unknown if the image is actually being pulled from dockerhub as the behavior of the script has not changed.
mentioned in commit nofusscomputing/projects/ansible/execution_environment@f2fb6a3540ec12a8092159d888bc3a77b47d5359
mentioned in commit nofusscomputing/projects/ansible/git_configuration@d91b68fd66785c6c96ec2ff0d04005b6e79e7b58
mentioned in commit nofusscomputing/projects/ansible/execution_environment@36e58ca7bec023f69a36ad46eebb0edae2c30e15
mentioned in commit
224ef83157mentioned in merge request nofusscomputing/projects/ansible/execution_environment!268
update ansible playbook to output env vars before starting to aid in debugging container. ansible-ee container has already been updated to be built to add the build sha to it's env vars.
marking incident as resolved.
changed the incident status to Resolved by closing the incident
added 2h of time spent
changed the incident status to Resolved