smarterclayton
commented
6 years ago Looks like there may be a system container bug with the pull CLI image flow.
Can you turn on -vv and run through that step again?
On Apr 5, 2018, at 2:23 AM, Vikas Choudhary (vikasc) < notifications@github.com> wrote:
Description
Trying to install single node 3.10 cluster with pre-release version v3.10.0-0.14.0. Eventually openshift-ansible fails with error related to node label parsing.
Invalid value: "node-role.kubernetes.io http://node-role.kubernetes.io~1master"
It fails because oc tool that openshift-ansible produces is version 3.6. Why it is not 3.10?
containerized=true
ansible_ssh_user=root openshift_deployment_type=openshift-enterprise openshift_image_tag=v3.10.0-0.14.0 openshift_release='3.10' openshift_playbook_rpm_repos=[{'id': 'aos-playbook-rpm', 'name': 'aos-playbook-rpm', 'baseurl': 'https://mirror.openshift.com/enterprise/all/3.10/v3.10.0-0.14.0_2018-03-27.1/x86_64/os/', 'enabled': 1, 'gpgcheck': 0}]
INSTALLER STATUS
Initialization : Complete (0:00:08) Health Check : Complete (0:00:01) etcd Install : Complete (0:01:53) Master Install : Complete (0:03:28) Master Additional Install : Complete (0:00:30) Node Install : In Progress (0:02:10) This phase can be restarted by running: playbooks/openshift-node/config.yml
Wednesday 04 April 2018 18:24:33 -0400 (0:00:20.880) 0:08:10.278 ***
etcd : Install etcd
68.88s openshift_master : Pre-pull master image
52.33s openshift_cli : Pull CLI Image
27.29s openshift_manage_node : Label nodes
20.88s restart master ------------------------------------------------------------------------------------------------------------------------------------------------------ 20.70s openshift_facts
13.94s openshift_manage_node : Wait for master API to become available before proceeding ----------------------------------------------------------------------------------- 10.85s openshift_manage_node : Set node schedulability
10.70s openshift_manage_node : Wait for Node Registration
10.70s openshift_node : Start and enable node
10.34s openshift_master : Start and enable master api
10.25s openshift_master : Start and enable master controller service
10.25s openshift_node : Install iSCSI storage plugin dependencies
9.75s openshift_manageiq : Configure role/user permissions
5.86s nickhammond.logrotate : nickhammond.logrotate | Install logrotate
5.19s openshift_node : Install GlusterFS storage plugin dependencies
5.05s openshift_node : Install dnsmasq
4.92s etcd : Install openssl
4.92s etcd : Install etcd
4.81s openshift_node : Install Ceph storage plugin dependencies
4.81s
Failure summary:
- Hosts: mynode Play: Additional node config Task: Label nodes Message: {u'cmd': u'/usr/local/bin/oc label node mynode node-role.kubernetes.io/master=true region=infra zone=default --overwrite -n default', u'returncode': 1, u'results': {}, u'stderr': u'The Node "mynode" is invalid: metadata.labels: Invalid value: "node-role.kubernetes.io~1master": name part must consist of alphanumeric characters, \'-\', \'\' or \'.\', and must start and end with an alphanumeric character (e.g. \'MyName\', or \'my.name\', or \'123-abc\', regex used for validation is \'([A-Za-z0-9][-A-Za-z0-9.]*)?[A-Za-z0-9]\')\n', u'stdout': u''}
Also when i tried to manually label the node, showing same error:
[root@dell-r620-01 openshift-ansible]# oc label node mynode node-role.kubernetes.io/master=true region=infra zone=default --overwrite -n default The Node "mynode" is invalid: metadata.labels: Invalid value: "node-role.kubernetes.io http://node-role.kubernetes.io~1master": name part must consist of alphanumeric characters, '-', '' or '.', and must start and end with an alphanumeric character (e.g. 'MyName', or 'my.name http://my.name', or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9.]*)?[A-Za-z0-9]')
Version
[root@dell-r620-01 openshift-ansible]# ansible --version ansible 2.4.3.0 config file = /home/vikas/openshift-ansible/ansible.cfg configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)]
[root@dell-r620-01 openshift-ansible]# git describe openshift-ansible-3.10.0-0.15.0
If i try to label node with oc tool 3.10 version (built manually), it works.
/cc @smarterclayton https://github.com/smarterclayton @sdodson https://github.com/sdodson @sjenning https://github.com/sjenning
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openshift/openshift-ansible/issues/7790, or mute the thread https://github.com/notifications/unsubscribe-auth/ABG_p2_ImBFzLTyIQPR0AvPau75KzFeHks5tlbhkgaJpZM4TH6jG .
vikaschoudhary16
openshift-bot
openshift-ci-robot
Description
Trying to install single node 3.10 cluster with pre-release version v3.10.0-0.14.0. Eventually openshift-ansible fails with error related to node label parsing.
It fails because oc tool that openshift-ansible produces is version 3.6. Why it is not 3.10?
Another confusing thing that i am not able to understand is the node image that openshift-ansible pulls to the host. Docker cmd shows image as "latest" but when i use "docker inspect", version it shows is v3.6.173.0.96, same as oc tool version.
same is the case with cli image.
Also when i tried to manually label the node, showing same error:
Version
UPDATE: Able to get pass this error by adding following in the inventory file:
openshift-ansible is not using
openshift_image_tag, in the docker pull for openshift3/ose image. Two questions:openshift_image_tagbe used in the docker pull?latestis used instead, whylatestpoints to 3.6 and not to 3.10?/cc @smarterclayton @sdodson @sjenning