Comments (5)
@eivantsov When you first create a Subscription
, an InstallPlan
resource should be generated. You should be able run kubectl -n openshift-operators get installplans
to see if any have been created. You can also check if any CSVs have been created in openshift-operators by running kubectl -n openshift-operators get csvs
.
from operator-lifecycle-manager.
@njhale thanks
somehow, I have got 1000s of install plans - oc delete --all installplans -n=openshift-operators
is deleting them 10 mins already :) Not sure how I ended up with that many installplans objects. Re-provisioning a cluster sounds like the best way for me to proceed.
from operator-lifecycle-manager.
@njhale now on a fresh cluster, it worked for my custom operator.
Now, I have installed Prometheus operator, and this time status is unknown. No installplan
is created at all. There is no ClusterServiceVersion too.
Not sure if it's relevant but logs from pod catalog-operator-859bf87cd5-cm5zp
say:
E0207 17:47:56.669006 1 queueinformer_operator.go:155] Sync "openshift-operators" failed: {che alpha {installed-custom-global-operators openshift-operators}} not found: CatalogSource {installed-custom-global-operators openshift-operators} not found
And indeed:
eugene@ivantsoft ~/go/src/github.com/operator-framework/operator-marketplace/scripts (master) $ oc get CatalogSource -n=openshift-operators
NAME AGE
installed-community-global-operators 15m
Che is a custom operator that I have added by creating a new OperatorSource:
apiVersion: marketplace.redhat.com/v1alpha1
kind: OperatorSource
metadata:
name: che-operator
namespace: openshift-marketplace
spec:
type: appregistry
endpoint: https://quay.io/cnr
registryNamespace: eivantsov
displayName: "Community Operators"
publisher: "Red Hat"
And the operator was successfully installed and works as expected.
I did not delete or modify any CRs. Just added a custom operator with the above yaml.
from operator-lifecycle-manager.
@njhale thanks
somehow, I have got 1000s of install plans -
oc delete --all installplans -n=openshift-operators
is deleting them 10 mins already :) Not sure how I ended up with that many installplans objects. Re-provisioning a cluster sounds like the best way for me to proceed.
We merged a fix for this in OLM though I'm not sure it's made its way to the installer yet. You could run one of the oc admin release
commands to figure out what OLM images are included.
Now, I have installed Prometheus operator, and this time status is unknown. No
installplan
is created at all. There is no ClusterServiceVersion too.
Could you run oc get packagemanifests -n openshift-operators -o yaml
?
from operator-lifecycle-manager.
This bug has been fixed and is available in all of the latest releases (upstream and ocp). Closing, but feel free to re-open if there's still an issue somewhere.
from operator-lifecycle-manager.
Related Issues (20)
- OLM happily creates duplicate `PackageManifest` resources in the same namespace HOT 3
- Resolution error `constraints not satisfiable: no operator found from catalog` is not cleared after CatalogSource is made available again HOT 1
- OperatorGroup documentation with label selectors provides incorrect example format
- nil pointer panic when deleting a CSV HOT 4
- Subscription Conditions should be set to false, instead of being removed.
- Cannot render multiple bundles with same name in semver template
- Allow force recreate of controller-manager pods through CSV upgrade options and be smarter about upgrade monitoring
- CSV stuck in install loop with auth-delegator already exists error
- OLM generate bundle silently drops k8s resources existing in manifests HOT 5
- InstallPlan is missing expected OwnerReference to Subscription HOT 1
- I want to use my privet registry for all images
- The catalog source pod can not migrate when the node becomes NotReady HOT 2
- Subscription is stuck when installing same operator multiple times into different namespaces at different dates
- Improve Makefile to avoid unnecessarily shelling out multiple times for the same variables
- support cacheless catalogsources
- Deployment "olm/packageserver" never appears on install HOT 1
- Startup Probe kills "/bin/opm serve" process and prevents operatorhubio pod to start HOT 1
- Unpin prometheus library versions from go.mod
- Unpin google.golang.org/grpc from go.mod
- Move away from actions/create-release@v1 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from operator-lifecycle-manager.