Created attachment 1314526 [details] yml files and script to setup example environment Description of problem: Creating a deployment based off an ImageStreamTag results in a Deployment with an empty status. Creating the same deployment but using the image the ImageStreamTag is based off of results in a deployment with status as expected. Issue appeared after 3.6 upgrade and does not reproduce on minishift 1.4.1 running OpenShift Master: v3.6.0+c4dd4cf Kubernetes Master: v1.6.1+5115d708d7 Version-Release number of selected component (if applicable): OpenShift Master: v3.6.173.0.5 (online version 3.5.0.20) Kubernetes Master: v1.6.1+5115d708d7 How reproducible: Always Steps to Reproduce: I've included some yml files to demostrate the issue 1. Extract attached file 2. Run setup.sh script to create imagestream, imagestreamtags, and deployments. Wait until deployments are ready 3. Execute `oc get deployment -o yaml`. Output should resemble file oc-get-deployment.yml in attachment Actual results: Deployment created from ImageStreamTag has "status:{}" Expected results: Deployment created from ImageStreamTag has nonempty status, like normal deployment Additional info: Status being empty causes a NPE when deleting deployments in fabric8 kubernetes client
duplicate after all; see https://bugzilla.redhat.com/show_bug.cgi?id=1481801#c14 *** This bug has been marked as a duplicate of bug 1481801 ***