You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior:
build successful How to reproduce it (minimal and precise):
run make -j4 with current code from master branch
File(s) to submit:
Cluster CR (custom resource), typically called cluster.yaml, if necessary
Operator's logs, if necessary
Crashing pod(s) logs, if necessary
To get logs, use kubectl -n <namespace> logs <pod name>
When pasting logs, always surround them with backticks or use the insert code button from the Github UI.
Read Github documentation if you need help.
Environment:
OS (e.g. from /etc/os-release): MacOS, golang ver 1.17
Kernel (e.g. uname -a):
Cloud provider or hardware configuration:
Rook version (use rook version inside of a Rook Pod):
Storage backend version (e.g. for ceph do ceph -v):
Kubernetes version (use kubectl version):
Kubernetes cluster type (e.g. Tectonic, GKE, OpenShift):
The text was updated successfully, but these errors were encountered:
Is this a bug report or feature request?
Deviation from expected behavior:
make -j4
produces an error message on go mod commandI managed to bypass by adding a replace as
But I would assume it's not a proper fix.
Expected behavior:
build successful
How to reproduce it (minimal and precise):
run
make -j4
with current code from master branchFile(s) to submit:
cluster.yaml
, if necessaryTo get logs, use
kubectl -n <namespace> logs <pod name>
When pasting logs, always surround them with backticks or use the
insert code
button from the Github UI.Read Github documentation if you need help.
Environment:
uname -a
):rook version
inside of a Rook Pod):ceph -v
):kubectl version
):The text was updated successfully, but these errors were encountered: