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.

Sign up for GitHub

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

Jump to bottom

Truncate job name of the osd prepare job further to avoid pod generation failure on K8s 1.22 #9312

Merged
merged 2 commits into from Dec 7, 2021
Merged

Truncate job name of the osd prepare job further to avoid pod generation failure on K8s 1.22 #9312

merged 2 commits into from Dec 7, 2021

Commits on Dec 6, 2021

  1. osd: truncate osd prepare job names further 

    In K8s 1.22 there is a bug in the job name generation that
the job name is truncated an additional 10 characters. This can cause an issue
in the generated pod name if it then ends in a non-alphanumeric character. In that case,
we more aggressively generate a hashed job name.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
    @travisn
    travisn committed Dec 6, 2021
    Copy the full SHA
    ee83ca7 View commit details
    Browse the repository at this point in the history

  2. test: generate long node name depending on test suite 

    The generation of a long node name in the integration tests was
being done based on the k8s version. In the past, older K8s versions
did not support the changing name. Now it's more maintainable if
we generate the long name depending on the test suite.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
    @travisn
    travisn committed Dec 6, 2021
    Copy the full SHA
    9d2aa1f View commit details
    Browse the repository at this point in the history