Description of problem:
Master recovery procedure can't work on disconnected install. I have checked this, yes its is downloading from etcd binary from https://storage.googleapis.com/etcd
In etcd-member-recover.sh
~~~
source "/usr/local/bin/openshift-recovery-tools"
~~~
# less /usr/local/bin/openshift-recovery-tools
~~~~
...
# download and test etcdctl from upstream release assets
dl_etcdctl() {
GOOGLE_URL=https://storage.googleapis.com/etcd
DOWNLOAD_URL=${GOOGLE_URL}
echo "Downloading etcdctl binary.."
curl -s -L ${DOWNLOAD_URL}/${ETCD_VERSION}/etcd-${ETCD_VERSION}-linux-amd64.tar.gz -o $ASSET_DIR/tmp/etcd-${ETCD_VERSION}-linux-amd64.tar.gz \
&& tar -xzf $ASSET_DIR/tmp/etcd-${ETCD_VERSION}-linux-amd64.tar.gz -C $ASSET_DIR/shared --strip-components=1 \
&& mv $ASSET_DIR/shared/etcdctl $ASSET_DIR/bin \
&& rm $ASSET_DIR/shared/etcd \
&& $ASSET_DIR/bin/etcdctl version
}
...
Version-Release number of selected component (if applicable):
4.2
Hello Team,
Can we get a status update on this bug?
It's preventing a customer from going live with 4.2 in Prod due to the lack of a disaster recovery process on air gapped clusters.
Thanks in advance!