Skip to content
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

Merged

Conversation

cgwalters
Copy link
Member

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.


@cgwalters
Copy link
Member Author

(only compile tested locally)

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 8, 2022
@cgwalters cgwalters force-pushed the log-ignition-provisioning branch 3 times, most recently from 3d72716 to ceaa278 Compare March 9, 2022 02:03
@cgwalters
Copy link
Member Author

Yep, looks good, see e.g. this log:

CoreOS aleph version: mtime=2022-01-25 12:16:35.638 +0000 UTC build=410.84.202201251210-0 imgid=rhcos-410.84.202201251210-0-qemu.x86_64.qcow2
Ignition provisioning: time=2022-03-09T02:18:02Z

Copy link
Contributor

@kikisdeliveryservice kikisdeliveryservice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one q

if err := json.Unmarshal(contents, &ignProvisioning); err != nil {
return err
}
fmt.Printf("Ignition provisioning: time=%v\n", ignProvisioning.ProvisioningDate)
Copy link
Contributor

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?

Copy link
Member Author

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.
@cgwalters
Copy link
Member Author

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 10, 2022

@cgwalters: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-disruptive a7f99eb link false /test e2e-aws-disruptive
ci/prow/e2e-aws-upgrade-single-node a7f99eb link false /test e2e-aws-upgrade-single-node
ci/prow/e2e-vsphere-upgrade a7f99eb link false /test e2e-vsphere-upgrade
ci/prow/e2e-gcp-op-single-node a7f99eb link false /test e2e-gcp-op-single-node
ci/prow/e2e-aws-serial a7f99eb link false /test e2e-aws-serial

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.

@kikisdeliveryservice
Copy link
Contributor

thanks!

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 10, 2022

[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:
  • OWNERS [cgwalters,kikisdeliveryservice]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants