Skip to content

Log level inconsistency in v1.5 #2938

@davemazur

Description

@davemazur

Previous versions (<v1.5) used debug, info, warning and error strings when setting the log level via:
% velero version -v {debug, info, warning, error}

This is also the understanding from the team - see below.

Velero-log-error-slack

In 1.5, the help is looking for a number:
% velero help
-v, --v Level number for the log level verbosity

If I enter:
% velero version -v debug

I get the following error which shows it is trying to convert from string to int:
An error occurred: invalid argument "debug" for "-v, --v" flag: strconv.ParseInt: parsing "debug": invalid syntax

My thoughts on the issue are:

  1. revert back to debug, info, warning, error strings in the code and modify help
  2. modify help to define a min/max/default integer log level and what level corresponds to debug, info, warning, error (i.e. level 0=info, level 10 = debug, default level = x, etc)

I did the following and did not notice a change in log level from 0-5. I noticed an increase at level 6 and also at level 10.

Velero-log-level-error

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • 👍 for "I would like to see this bug fixed as soon as possible"
  • 👎 for "There are more important bugs to focus on right now"

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions