LOG-5862: Validation rule causing error on install

[cahartma]

Description

The validation error can also be verified by trying to applying the CRD to the cluster. I was not able to reproduce the "CRD is not present" errors, but I am assuming the first (validation) error is causing the requirementStatus to fail as well.

Also adding a shortname back into the CRD. In case of upgrade scenario, user can now use obsclf (until we remove the old CRD)

/cc @Clee2691 @vparfonov
/assign @jcantrill

Links

• https://issues.redhat.com/browse/LOG-5862

[openshift-ci-robot]

@cahartma: This pull request references LOG-5862 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.8.0" version, but no target version was set.

In response to this:

Description

The validation error can also be verified by trying to applying the CRD to the cluster. I was not able to reproduce the "CRD is not present" errors, but I am assuming the first (validation) error is causing the requirementStatus to fail as well.

Also adding a shortname back into the CRD. In case of upgrade scenario, user can now use obsclf (until we remove the old CRD)

/cc @Clee2691 @vparfonov
/assign @jcantrill

Links

• https://issues.redhat.com/browse/LOG-5842

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@cahartma: This pull request references LOG-5862 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.8.0" version, but no target version was set.

In response to this:

Description

The validation error can also be verified by trying to applying the CRD to the cluster. I was not able to reproduce the "CRD is not present" errors, but I am assuming the first (validation) error is causing the requirementStatus to fail as well.

Also adding a shortname back into the CRD. In case of upgrade scenario, user can now use obsclf (until we remove the old CRD)

/cc @Clee2691 @vparfonov
/assign @jcantrill

Links

• https://issues.redhat.com/browse/LOG-5862

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cahartma

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 [cahartma]

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

[jcantrill]

/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 1db0661 and 2 for PR HEAD eeb3b43 in total

[openshift-ci]

@cahartma: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.