Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to deploy addon execute job [rke-user-includes-addons]: Failed to save addon ConfigMap #2443

Open
pjamenaja opened this issue Jan 30, 2021 · 3 comments

Comments

@pjamenaja
Copy link

RKE version:
v1.2.4

Docker version: (docker version,docker info preferred)
19.3.14

Operating 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:

...
INFO[0051] [addons] Deploying rke-user-includes-addons
INFO[0051] [addons] Saving ConfigMap for addon rke-user-includes-addons to Kubernetes
WARN[0081] Failed to deploy addon execute job [rke-user-includes-addons]: Failed to save addon ConfigMap
: [addons] Timeout waiting for kubernetes to be ready
INFO[0081] Finished building Kubernetes cluster successfully
...

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.

WARN[0081] Failed to deploy addon execute job [rke-user-includes-addons]: Failed to save addon ConfigMap
: [addons] Timeout waiting for kubernetes to be ready

This is my RKE config file (with masked some fields)
rancher-cluster.yaml.txt

Thanks,
Seub

@superseb
Copy link
Contributor

superseb commented Feb 2, 2021

This is probably because of the UpdateStateTimeout which is fixed to 30 (seconds).

@amuntean-godaddy
Copy link

Are there any plans to resolve this issue ?

@lugg1
Copy link

lugg1 commented May 29, 2024

@superseb: What happens if the UpdateStateTimeout will increased to 60 or more seconds?

@amuntean-godaddy: We run in the same issue...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants