-
Notifications
You must be signed in to change notification settings - Fork 394
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
daemon: bootimage and ignition logging #2994
daemon: bootimage and ignition logging #2994
Conversation
(only compile tested locally) |
3d72716
to
ceaa278
Compare
Yep, looks good, see e.g. this log:
|
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.
one q
pkg/daemon/coreos.go
Outdated
if err := json.Unmarshal(contents, &ignProvisioning); err != nil { | ||
return err | ||
} | ||
fmt.Printf("Ignition provisioning: time=%v\n", ignProvisioning.ProvisioningDate) |
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.
is there are reason to not use glog here?
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.
Makes sense, done!
My immediate motivation is to gather more information in the MCD logs; same reason we log the boots. For coreos layering work, we will be sensitive to the initial bootimage more and may need to update it. Another angle for this is that we could actually plumb this information up into the node object, and from there into the operator/controller and feed it into prometheus and into telemetry, so we start to gather information on e.g. how many clusters have old bootimages. Also log Ignition provisioning information.
ceaa278
to
a7f99eb
Compare
I originally had a two-commit series but accidentally squashed fixes into the second; at this point disentangling that isn't worth it, so just squashed to one commit. |
@cgwalters: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
thanks! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, kikisdeliveryservice The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
daemon: Log data from
/sysroot/.coreos-aleph-version.json
My immediate motivation is to gather more information in the MCD
logs; same reason we log the boots. For coreos layering work,
we will be sensitive to the initial bootimage more and may need
to update it.
Another angle for this is that we could actually plumb this information
up into the node object, and from there into the operator/controller
and feed it into prometheus and into telemetry, so we start
to gather information on e.g. how many clusters have old bootimages.
daemon: Also log Ignition provisioning information
More data is good here; this builds on the previous information
for the bootimage generation time.