Skip to content

Log the storage class name, not its pointer, in filesystem overhead - #4320

Merged
kubevirt-prow[bot] merged 1 commit into
kubevirt:mainfrom
fjvbn2003:fs-overhead-log-sc-name
Oct 22, 2026
Merged

kubevirt-prow[bot] merged 1 commit into
kubevirt:mainfrom
fjvbn2003:fs-overhead-log-sc-name

Conversation

@fjvbn2003

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

GetFilesystemOverheadForStorageClass passes the *string storage class name to klog.V(3).Info, which joins its
arguments with fmt.Sprint. At -v=3 the two "storage class not found" lines therefore print the pointer address
and no spaces:

Storage class0x7035abda0020not found, trying default storage class

This switches both lines to Infof with the dereferenced name (ptr.Deref, already imported in this file):

Storage class "local-path" not found, trying default storage class

Which issue(s) this PR fixes:
None filed; found while reading the code.

Special notes for your reviewer:
Log-only change. go vet ./pkg/controller/common/ is clean and go test ./pkg/controller/common/ passes
(43 of 43 specs, golang:1.27.2, -mod=vendor).

AI disclosure: I used Claude (Anthropic) to help find and write this change; I reviewed it and reproduced the log
output above. The commit carries an Assisted-by trailer.

Release note:

NONE

GetFilesystemOverheadForStorageClass passes the *string storage class
name to klog.V(3).Info, which joins its arguments with fmt.Sprint. The
log line therefore shows the pointer address and no spaces, e.g.
"Storage class0x7035abda0020not found, trying default storage class".
Use Infof with the dereferenced name instead.

Assisted-by: Claude <[email protected]>
Signed-off-by: YoungjuKim <[email protected]>
@kubevirt-prow kubevirt-prow Bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Oct 19, 2026
@kubevirt-prow

kubevirt-prow Bot commented Oct 19, 2026

Copy link
Copy Markdown

Hi @fjvbn2003. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

@akalenyu akalenyu left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

/approve
/lgtm
thanks!

@kubevirt-prow kubevirt-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 20, 2026
@kubevirt-prow

kubevirt-prow Bot commented Oct 20, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akalenyu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@kubevirt-prow kubevirt-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 20, 2026
@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 50.213%. remained the same — fjvbn2003:fs-overhead-log-sc-name into kubevirt:main

@fjvbn2003

Copy link
Copy Markdown
Contributor Author

/retest-required

@kubevirt-prow

kubevirt-prow Bot commented Oct 21, 2026

Copy link
Copy Markdown

@fjvbn2003: PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test.

Details

In response to this:

/retest-required

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-sigs/prow repository.

@fjvbn2003

Copy link
Copy Markdown
Contributor Author

The one failure in e2e-ceph-wffc is DataImportCron … with snapshot sources [test_id:10033], which this log-only change doesn't touch (545/546 passed). Could someone /retest-required, please? Thanks!

@akalenyu

Copy link
Copy Markdown
Collaborator

/override pull-containerized-data-importer-e2e-ceph-wffc

@kubevirt-prow

kubevirt-prow Bot commented Oct 22, 2026

Copy link
Copy Markdown

@akalenyu: Overrode contexts on behalf of akalenyu: pull-containerized-data-importer-e2e-ceph-wffc

Details

In response to this:

/override pull-containerized-data-importer-e2e-ceph-wffc

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-sigs/prow repository.

@kubevirt-prow
kubevirt-prow Bot merged commit b2e1e1e into kubevirt:main Oct 22, 2026
21 checks passed
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants