Bug 1767677 - Master recovery procedure can't work on disconnected install
Summary: Master recovery procedure can't work on disconnected install
Keywords:
Status: CLOSED DUPLICATE of bug 1797038
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.2.z
Assignee: Andrea Hoffer
QA Contact: ge liu
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-01 01:41 UTC by Neeraj
Modified: 2023-09-07 20:54 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-12 21:36:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Neeraj 2019-11-01 01:41:33 UTC
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

Comment 1 rehan 2019-12-05 09:35:46 UTC
Any update on this ?

Comment 3 Tony Garcia 2020-01-10 21:12:40 UTC
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!


Note You need to log in before you can comment on or make changes to this bug.