Hide Forgot
Description of problem: Due to space issues, after changing the path of pool default (i.e. pool-edit, pool-destroy, pool-start), workers are not created at all. Version-Release number of the following components: rpm -q openshift-ansible rpm -q ansible ansible --version How reproducible: Steps to Reproduce: 1. Change path in pool default 2. Run installer (master + workers in config.yaml) Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated No error msg appeared Expected results: Same behavior as with the default path "/var/lib/libvirt/images" Additional info: Please attach logs from ansible-playbook with the -vvv flag
I believe I already fixed this with: https://github.com/openshift/installer/pull/1628
Checked and work well now. $ bin/openshift-install version bin/openshift-install unreleased-master-1205-g59dd3e5b94349ec0b42690c13a688a6a4e5f8d81 built from commit 59dd3e5b94349ec0b42690c13a688a6a4e5f8d81 release image registry.svc.ci.openshift.org/origin/release:4.2 virsh # vol-list default Name Path ---------------------------------------------------------------------------------------------------------- wjiang-w72vx-base /var/lib/libvirt/images.new/wjiang-w72vx-base wjiang-w72vx-bootstrap /var/lib/libvirt/images.new/wjiang-w72vx-bootstrap wjiang-w72vx-bootstrap.ign /var/lib/libvirt/images.new/wjiang-w72vx-bootstrap.ign wjiang-w72vx-master-0 /var/lib/libvirt/images.new/wjiang-w72vx-master-0 wjiang-w72vx-master.ign /var/lib/libvirt/images.new/wjiang-w72vx-master.ign wjiang-w72vx-worker-0-hmmlm /var/lib/libvirt/images.new/wjiang-w72vx-worker-0-hmmlm wjiang-w72vx-worker-0-hmmlm.ignition /var/lib/libvirt/images.new/wjiang-w72vx-worker-0-hmmlm.ignition virsh # list Id Name State --------------------------------------------- 1 wjiang-w72vx-bootstrap running 2 wjiang-w72vx-master-0 running 3 wjiang-w72vx-worker-0-hmmlm running
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-2019:2922