-
Notifications
You must be signed in to change notification settings - Fork 9
buildConfig for some apps fails while pushing image #42
Comments
There is more problems with BuildConfigs. o2n exports finished images (result of BuildConfig) with DeploymentConfigs. |
I see two options what to do here. 1) stop exporting images (pull/push to external registry) 2) Stop exporting BuildConfigs and really only on finished images. Or we can do both. Your thoughts @surajssd ? |
I just done couple more test with ruby-hello-world, When deploying exported app the following happens:
At first this behavior might be confusing, but it is basically OK :-) But I've still not be able to figure out why some applications BuildConfigs fails (like mlbaparks) with following error
and other BuildConfigs are ok - like ruby-hello-world |
This seems to be timing issue. It fails when BuildConfig is created before ImageStream. This is already reported in Origin openshift/origin#4518 |
It could be fixed by deploying artifacts in right order. But AtomicApp is not currently deploying artifacts in same order as they appear in Nulecule file. Related issue: projectatomic/atomicapp#669 |
One workaround for this would be using List with artifacts in right order, but this is not possible due to this: projectatomic/atomicapp#612 |
Until we can specify order in Nulecule, only workaround for this is to restart build manually. |
For mlbparks:
Importing BuildConfig triggers build that fails on this error:
The text was updated successfully, but these errors were encountered: