Open pjamenaja opened 3 years ago
This is probably because of the UpdateStateTimeout
which is fixed to 30 (seconds).
Are there any plans to resolve this issue ?
@superseb: What happens if the UpdateStateTimeout
will increased to 60 or more seconds?
@amuntean-godaddy: We run in the same issue...
RKE version: v1.2.4
Docker version: (
docker version
,docker info
preferred) 19.3.14Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred) NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/"CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7"
3.10.0-1160.11.1.el7.x86_64
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) VSphere
cluster.yml file: rancher-cluster.yaml.txt 02_issue.yaml.txt
Steps to Reproduce: run : rke up --config rancher-cluster.yaml
Results:
Hi,
I think the RKE seems to have the issue with a big addon file. This is the YAML file I used 02_issue.yaml.txt in the addons_include: section and got the warning shown below.
This is my RKE config file (with masked some fields) rancher-cluster.yaml.txt
Thanks, Seub