Opni Chart does not supply a default release name in Rancher
Daemonslayer2048 opened this issue · comments
Summary:
I am attempting to install an Opni demo via the Rancher UI by following the instructions provided here: https://opni.io/installation/opni
It would appear when following these instructions with the values provided below, results in nothing more than CRDs being deployed. No workload of any type is deployed.
Values Provided:
- Hostname: "opni.test.lan"
- Service Type: "ClusterIP"
- Auth Provider: "noauth"
Logs:
helm upgrade --install=true --namespace=opni --timeout=10m0s --values=/home/shell/helm/values-opni-crd-0.12.1.yaml --version=0.12.1 --wait=true opni-crd /home/shell/helm/opni-crd-0.12.1.tgz
checking 26 resources for changes
Looks like there are no changes for CustomResourceDefinition "alertingclusters.core.opni.io"
Looks like there are no changes for CustomResourceDefinition "bootstraptokens.core.opni.io"
Looks like there are no changes for CustomResourceDefinition "datapreppers.logging.opni.io"
Looks like there are no changes for CustomResourceDefinition "gateways.core.opni.io"
Patch CustomResourceDefinition "grafanadashboards.grafana.opni.io" in namespace
Patch CustomResourceDefinition "grafanadatasources.grafana.opni.io" in namespace
Patch CustomResourceDefinition "grafananotificationchannels.grafana.opni.io" in namespace
Patch CustomResourceDefinition "grafanas.grafana.opni.io" in namespace
Looks like there are no changes for CustomResourceDefinition "keyrings.core.opni.io"
Patch CustomResourceDefinition "logadapters.logging.opni.io" in namespace
Looks like there are no changes for CustomResourceDefinition "loggingclusterbindings.logging.opni.io"
Looks like there are no changes for CustomResourceDefinition "loggingclusters.core.opni.io"
Looks like there are no changes for CustomResourceDefinition "monitoringclusters.core.opni.io"
Looks like there are no changes for CustomResourceDefinition "multiclusterrolebindings.logging.opni.io"
Looks like there are no changes for CustomResourceDefinition "multiclusterusers.logging.opni.io"
Looks like there are no changes for CustomResourceDefinition "natsclusters.core.opni.io"
Patch CustomResourceDefinition "opensearchclusters.opensearch.opster.io" in namespace
Looks like there are no changes for CustomResourceDefinition "opensearchrepositories.logging.opni.io"
Looks like there are no changes for CustomResourceDefinition "opniclusters.ai.opni.io"
Looks like there are no changes for CustomResourceDefinition "opniopensearches.logging.opni.io"
Looks like there are no changes for CustomResourceDefinition "preprocessors.logging.opni.io"
Looks like there are no changes for CustomResourceDefinition "pretrainedmodels.ai.opni.io"
Looks like there are no changes for CustomResourceDefinition "recurringsnapshots.logging.opni.io"
Looks like there are no changes for CustomResourceDefinition "rolebindings.monitoring.opni.io"
Looks like there are no changes for CustomResourceDefinition "roles.monitoring.opni.io"
Looks like there are no changes for CustomResourceDefinition "snapshots.logging.opni.io"
beginning wait for 26 resources with timeout of 10m0s
Release "opni-crd" has been upgraded. Happy Helming!
2023-11-21T10:53:38.152239937-06:00 NAME: opni-crd
2023-11-21T10:53:38.152245721-06:00 LAST DEPLOYED: Tue Nov 21 16:53:35 2023
2023-11-21T10:53:38.152258457-06:00 NAMESPACE: opni
2023-11-21T10:53:38.152261634-06:00 STATUS: deployed
2023-11-21T10:53:38.152265151-06:00 REVISION: 2
2023-11-21T10:53:38.152267890-06:00 TEST SUITE: None
2023-11-21T10:53:38.155118785-06:00 ---------------------------------------------------------------------
SUCCESS: helm upgrade --install=true --namespace=opni --timeout=10m0s --values=/home/shell/helm/values-opni-crd-0.12.1.yaml --version=0.12.1 --wait=true opni-crd /home/shell/helm/opni-crd-0.12.1.tgz
2023-11-21T10:53:38.164128701-06:00 ---------------------------------------------------------------------
2023-11-21T10:53:38.164132789-06:00 helm upgrade --install=true --namespace=opni --timeout=10m0s --values=/home/shell/helm/values-opni-0.12.1.yaml --version=0.12.1 --wait=true /home/shell/helm/opni-0.12.1.tgz
Error: "helm upgrade" requires 2 arguments
2023-11-21T10:53:38.192701309-06:00
2023-11-21T10:53:38.192705592-06:00 Usage: helm upgrade [RELEASE] [CHART] [flags]
You'll need to manually enter a release name for the chart; it's possible that our chart is missing some configuration that rancher needs in order to auto-generate a default release name.
Looks like you are correct, I appreciate the response.
@Daemonslayer2048 What would you think about repurposing this ticket to request that a default release name be provided. If you encountered this issue, I'm sure others will as well.
I think there are two options really:
- Create a default release name
- Update the docs
I can repurpose the ticket no problem, just thought I would toss out the 2nd option before doing so.
Either is valid with option one being the preference for most people probably.
We can reuse this issue to track the chart fix. 👍