-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚑️ hotfix GC first deploy #2899
🚑️ hotfix GC first deploy #2899
Conversation
…(ops adds deploy prefix) service could not start because hostname was too long. Error message was container init caused: sethostname: invalid argument: unknown
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
…as not recognized
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Codecov Report
@@ Coverage Diff @@
## master #2899 +/- ##
========================================
- Coverage 79.3% 76.1% -3.3%
========================================
Files 673 673
Lines 27624 27633 +9
Branches 3218 3220 +2
========================================
- Hits 21928 21040 -888
- Misses 4946 5899 +953
+ Partials 750 694 -56
Flags with carried forward coverage won't be shown. Click here to find out more.
|
What do these changes do?
Following problems were detected
hostname: "{{.Node.Hostname}}-{{.Service.Name}}-{{.Task.Slot}}"
was too long.container init caused: sethostname: invalid argument: unknown
ws-garbage-collector
garbage_collector
could not load json-schema for project which is normally init by theprojects
plugin (which is off in this config)projects
plugin setup functions such that thegarbage_collector
can init the parts it needs so it can safely useprojects_api
interface.Related issue/s
How to test
Checklist