api-registry pod can't be started

[cmoulliard]

The api-registry can't be started and this error is reported continuously within the log of OpenShift

Image(s): fabric8/api-registry:2.2.93

Mar 10 18:19:19 vagrant.f8 openshift[1024]: I0310 18:19:19.870444    1024 manager.go:2079] Back-off 2m40s restarting failed container=api-registry pod=api-registry-itncw_default(7d30f56e-e6eb-11e5-a35d-080027b5c2f4)
Mar 10 18:19:19 vagrant.f8 openshift[1024]: E0310 18:19:19.883245    1024 pod_workers.go:125] Error syncing pod 7d30f56e-e6eb-11e5-a35d-080027b5c2f4, skipping: failed to "StartContainer" for "api-registry" witth CrashLoopBackOff: "B

[KurtStam]

Hi @cmoulliard, could it be because it no longer there? #95. Are you missing certain functionality?

[cmoulliard]

Hi @KurtStam. I will make a new test this week. Excepted that it was not running, I didn't notice problems with apiman.

[KurtStam]

@cmoulliard ok - my point is that it is removed from the build in favor of using the api-catalog in apiman.

[KurtStam]

@cmoulliard Can I close this?