Hide Forgot
Description of problem: While updating overcloud the command 'ceph-upgrade' (ran after 'openstack overcloud update run --nodes CephStorage' and before 'openstack overcloud update converge') fails with this error: 2018-06-03 11:52:44Z [overcloud-Controller-ezdnestd3o3n-0-jwqqdvrzy5jz]: UPDATE_FAILED Resource UPDATE failed: resources.NodeTLSData: Resource CREATE failed: Error: resources.ControllerTLSDeployment: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1 Version-Release number of selected component (if applicable): For more information about the command and full error log see attached undercloud.tar archive How reproducible: Steps to Reproduce: 1. Install osp13 beta release with ceph 3-6 2. Update to passed_phase2 with ceph 3-8 3. Actual results: Update fail Expected results: Update pass Additional info:
Created attachment 1447353 [details] ceph update command
Created attachment 1447354 [details] ceph udate log
So according to Raviv, the issue is not reproduced anymore. (16:51 < rbartal> lbezdick, matbu so this time ceph-upgrade command passed, I don't know why. maybe because the passed_phase2 build is newer 16:52 < matbu> rbartal: yep i saw that update_complete 16:53 < matbu> rbartal_go_home: thanks for trying to reproduce it 16:54 < matbu> rbartal_go_home: so can you closed it ? or May i 16:54 < matbu> if you are going back to home 16:54 < rbartal_go_home> matbu, yes, please close it 16:56 < matbu> rbartal_go_home: ack ) So closing it as NOTABUG
This bug was re-opened as we found it reproduce on specific environments (composable) and does not reproduce, The failure is with grep command on openstack-neutron-l3-agent that returns 2 matches while the script expect 1 match only.
Patch not in build
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/RHEA-2018:2086