-
Bug
-
Resolution: Not a Bug
-
Normal
-
Logging 5.4.0
-
None
-
False
-
False
-
NEW
-
OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
-
VERIFIED
-
-
Logging (LogExp) - Sprint 214
if the logstack deployment fails on MissingObjectStorageSecret, once the secret is created, the deployment should continue.
Step to Reproduce:
1) deploy loki-operator
2) deploy lokistack without secret. the lokistack raise message '"Missing object storage secret'
$oc get lokistack my-loki -o json
{
"apiVersion": "loki.openshift.io/v1beta1",
"kind": "LokiStack",
"metadata": {
"creationTimestamp": "2022-02-10T03:28:26Z",
"generation": 1,
"name": "my-loki",
"namespace": "openshift-logging",
"resourceVersion": "83760",
"uid": "091154bb-57f8-4b63-af17-e72c912fbf1b"
},
"spec": {
"managementState": "Managed",
"replicationFactor": 2,
"size": "1x.extra_small",
"storage": {
"secret": {
"name": "credsecret"
}
},
"storageClassName": "gp2",
"template": {
"ingester": {
"nodeSelector": {
"kubernetes.io/os": "linux"
},
"replicas": 3
}
},
"tenants": {
"mode": "openshift-logging"
}
},
"status": {
"components": {},
"conditions": [
{
"lastTransitionTime": "2022-02-10T03:28:26Z",
"message": "Missing object storage secret",
"reason": "MissingObjectStorageSecret",
"status": "False",
"type": "Degraded"
},
{
"lastTransitionTime": "2022-02-10T03:28:26Z",
"message": "All components ready",
"reason": "ReadyComponents",
"status": "True",
"type": "Ready"
}
]
}
}
3) Create secret and wait 10 minutes
$oc get lokistack my-loki NAME AGE my-loki 13m $oc get secret credsecret NAME TYPE DATA AGE credsecret Opaque 5 10m
Actual Result:
The lokistack wasn't deployed in 10 minutes after secret was created
Expect Result:
The lokistack can be deployed after the secret is created.
Additional Info:
recreate lokistack resource or restart loki-operator pod can trigger new deployment
