In master and release-3.6 TASK [etcd_upgrade : lineinfile] *********************************************** Tuesday 31 October 2017 04:41:58 +0000 (0:00:30.905) 0:05:38.953 ******* fatal: [master-23f3c]: FAILED! => {"failed": true, "msg": "the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'etcd_quota_backend_bytes' is undefined\n\nThe error appears to have been in '/home/opsmedic/aos-cd/git/openshift-tools/openshift/installer/vendored/openshift-ansible-3.6.173.0.59/roles/etcd_upgrade/tasks/upgrade_rpm.yml': line 22, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- lineinfile:\n ^ here\n"}
I think this is happening because the variable is defined in etcd role but that role is not required of etcd_upgrade. Perhaps when performing a complete upgrade the etcd role gets invoked before etcd_upgrade but only when running control_plane is it undefined?
Proposed: https://github.com/openshift/openshift-ansible/pull/6003
@Scott @Russell AFAIK, etcd will not be upgraded by default during upgrade or upgrade_control_plane from v3.5 to v3.6. So this error can only happened when running upgrade_etcd.yml to upgrade etcd manually. Moreover, due to bz1495486, running upgrade_etcd can not upgrade a 3.1 or newer version etcd. So QE just check the pr merged, and run upgrade_etcd.yml against an etcd-3.0.15 to ensure the issue has been fixed. Version: openshift-ansible-3.6.173.0.75-1.git.0.0a44128.el7.noarch TASK [etcd_upgrade : lineinfile] ******************************************************************************************************************************************** changed: [x.x.x.x] => { "backup": "", "changed": true, "failed": false } MSG: line added
Yes that's fine, just need to ensure that this gets added.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3255
*** Bug 1546873 has been marked as a duplicate of this bug. ***
*** Bug 1546871 has been marked as a duplicate of this bug. ***
*** Bug 1546265 has been marked as a duplicate of this bug. ***