Known Issues and Limitations in Cloudera Data Science Workbench 1.9.0
This topic lists the current known issues and limitations in Cloudera Data Science Workbench 1.9.0.
-
There is an issue with installing and upgrading CDSW in an airgapped environment where docker service has no access to the k8s docker repository or has no proxy set. .
Workaround:
The following steps must be executed after deploying the CDSW parcel and DOCKER role is started but the MASTER, APPLICATION, and WORKER roles are not yet started. In case of an RPM install, this needs to be done after starting the
dockerd
service but before starting the CDSW master node.- Pull the missing
etcd
image to local docker repo in a node that has access to thek8s.gcr.io
docker repository.# docker pull k8s.gcr.io/etcd:3.3.15-0
- Save the missing
etcd
image.# docker save k8s.gcr.io/etcd:3.3.15-0 -o etcd.tar
- Copy tarball to the CDSW master node.
# scp etcd.tar <user>@<node>:<location>/etcd.tar
- SSH in to the CDSW master node and load the image to the local docker repo.
# docker load -i <location>/etcd.tar
- Pull the missing
For
previous versions, see:
- Known Issues in Cloudera Data Science Workbench 1.8.x
- Known Issues in Cloudera Data Science Workbench 1.7.x
- Known Issues in Cloudera Data Science Workbench 1.6.x
- Known Issues in Cloudera Data Science Workbench 1.5.x
- Known Issues in Cloudera Data Science Workbench 1.4.x
- Known Issues in Cloudera Data Science Workbench 1.3.x
- Known Issues in Cloudera Data Science Workbench 1.2.x
- Known Issues in Cloudera Data Science Workbench 1.1.x.