Skip to content

Operator with webhook deployment fails with flipping states #1793

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

Closed
srinivasannanduri opened this issue Oct 5, 2020 · 3 comments
Closed
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@srinivasannanduri
Copy link

Bug Report

What did you do?
We tried installing an operator with webhooks using OLM from OperatorHub (Openshift). However, we missed specifying the ports in the CSV. The installation of operator succeeded with no errors in the Operator / Webhook containers / pods but the Operator installation never succeeded.

What did you expect to see?
Operator SDK fails during validation that the required elements / values are missing in the CSV

What did you see instead? Under which circumstances?
Installation of the operator went through but there is an error in OLM operator
[webhooks[0].clientConfig.service.port: Invalid value: 0: port is not valid: must be between 1 and 65535, inclusive,

Environment
v1.0.0

  • Kubernetes version information:

Kubernetes Version: v1.18.3+6c42de8

  • Kubernetes cluster kind:

Client Version: openshift-clients-4.5.0-202006231303.p0-4-gb66f2d3a6
Server Version: 4.5.8
Kubernetes Version: v1.18.3+6c42de8

Possible Solution

Additional context
Add any other context about the problem here.

@stale
Copy link

stale bot commented Dec 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 4, 2020
@openshift-ci-robot openshift-ci-robot added triage/unresolved Indicates an issue that can not or will not be resolved. and removed wontfix labels Dec 5, 2020
@stale
Copy link

stale bot commented Mar 5, 2021

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contribution.
For more help on your issue, check out the olm-dev channel on the kubernetes slack [1] and the OLM Dev Working Group [2] [1] https://kubernetes.slack.com/archives/C0181L6JYQ2 [2] https://github.com/operator-framework/community#operator-lifecycle-manager-wg

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 5, 2021
@stale
Copy link

stale bot commented Mar 15, 2021

This issue has been automatically closed because it has not had any recent activity. Thank you for your contribution.

@stale stale bot closed this as completed Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Development

No branches or pull requests

2 participants