Open VeerMuchandi opened 7 years ago
No one has experienced this problem. Can you describe the exact steps you are taking to get there? Your YAML is also badly formatted.
It looks like you may have failed to correctly select the right image to be used, or completed the steps in the wrong order.
All I did was when deploying the nationalparks-live app, I selected the nationalparks image and changed the name of the app to nationalparks-live as instructed in the lab. This changed the trigger to use nationalparks-live:live instead of nationalparks:live. I had to edit the DC to fix the trigger to get the app to deploy.
No one else has reported this issue and we have had well over a hundred people use this content at this point. I'm inclined to believe this is user error.
Can you provide very detailed/specific instructions / screenshots on how you can reproduce this issue?
FYI I just did this lab again:
triggers:
- type: ConfigChange
- imageChangeParams:
automatic: true
containerNames:
- nationalparks-live
from:
kind: ImageStreamTag
name: nationalparks:live
namespace: explore-00
lastTriggeredImage: 172.30.227.235:5000/explore-00/nationalparks@sha256:b2e1d95769b7eedac6461596bd584582b2c7c47944bc578939860bab9eebf6e5
type: ImageChange
In the step "Live Deployment", when you deploy an application pointing to the image with "live" tag, but if you rename the app to "nationalparks-live", the trigger in the deployment configuration is set to "national parks-live:live"
See below: triggers:
This is preventing the application from getting deployed. I had to manually change the from image name to national parks:live.