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.

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

DeplymentController uses an unusual construct for getByKey #15928

Open
soltysh opened this issue Aug 23, 2017 · 4 comments
Open

DeplymentController uses an unusual construct for getByKey #15928

soltysh opened this issue Aug 23, 2017 · 4 comments
Labels
component/apps kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2 sig/kube-origin

Comments

@soltysh
Copy link
Contributor

soltysh commented Aug 23, 2017

I found this

if errors.IsNotFound(err) {
glog.V(4).Infof("Replication controller %q has been deleted", key)
return nil, nil
}
which I had to fix in image controller in #15927.

I'm guessing @tnozicka you'll be the best person to address the same issue in deployments. Generally getByKey should not interpret errors.

@tnozicka
Copy link
Contributor

Yes, that seems ugly. Not sure if that is a bug since it's a private function so as long as the deployer controller checks for it properly, should work; although it's error prone.

@soltysh
Copy link
Contributor Author

soltysh commented Aug 30, 2017

although it's error prone.

That's why you need to fix it. I did the same in images.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 18, 2018
@soltysh
Copy link
Contributor Author

soltysh commented Mar 5, 2018

/remove-lifecycle stale
/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 5, 2018
@tnozicka tnozicka removed their assignment Mar 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/apps kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2 sig/kube-origin
Projects
None yet
Development

No branches or pull requests

4 participants