-
Notifications
You must be signed in to change notification settings - Fork 107
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
[BUG][2.0.0] Rook/Ceph - Pod remains in ContainerCreating state when using StorageClass from Rook/Ceph cluster #3184
Comments
K8s cluster provisioned within AWS and access 2 the control plane obtained.
|
Rook operator deployed `root@prefix-7-norbix-kubernetes-master-vm-0:~/persistent_storage# k get all -n rook-ceph NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE NAME READY UP-TO-DATE AVAILABLE AGE NAME DESIRED CURRENT READY AGE |
Closing the ticket since its mismatch in default epiphany configuration for kubernetes cluster. Clarification:
For users working with Rook on Epiphany cluster, and trying to use Fix in the code, which will enable setting that flag by users when initializing cluster will be added in Epiphany 2.0.1, see the ticket for more information: #3190 |
Describe the bug
Scenario: simple Epiphany cluster with 1 master and 3 kubernetes worker nodes, configured to use Rook. See input_manifest.yml used for deploying the cluster: input_manifest.txt
After deploying the cluster, using example from Rook documentation - Block Storage - we try to deploy example app - wordpress.
After running
kubectl apply -f wordpress.yml
, wordpress pod remains ContainerCreating state. That pod is using default rook StorageClass.Note that Object Storage (one that imitates S3 API) is working fine with the default configuration.
Note that Block Storage which is reason of that Bug is able to provision the volume to the pod if cluster has:
See commands to enable that state:
How to reproduce
ContainerCreating
stateExpected behavior
Expected Behavior
When deploying any app that will consume Block Storage, pod will be created, in ready state, and will be able to consume that persistent block storage.
Config files
input_manifest.txt
Environment
epicli version: [
epicli --version
]2.0.0
Additional context
DoD checklist
The text was updated successfully, but these errors were encountered: