search

att-comdev / openstack-helm

PROJECT HAS MOVED TO OPENSTACK
https://github.com/openstack/openstack-helm
69 stars 41 forks source link

bug: Unable to pull image for rabbitmq #306

Closed wilkers-steve closed 7 years ago

wilkers-steve commented 7 years ago

Is this a bug report or feature request? (choose one): bug

Kubernetes Version (output of kubectl version): 1.5.2

Helm Client and Tiller Versions (output of helm version): 2.2.3

Development or Deployment Environment?: Development

Release Tag or Master: Master

Expected Behavior: Running helm install --name=rabbitmq local/rabbitmq --namespace=rabbitmq should result in a successful release

What Actually Happened: Pod fails to start with an ImagePullBackOff. Appears to be due to an invalid rabbitmq image tag

How to Reproduce the Issue (as minimally as possible): Follow standard development flow up to installing rabbitmq

Any Additional Comments:

Log output: 29s 15s 2 {kubelet ip-172-31-8-127} Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "rabbitmq" with ErrImagePull: "image pull failed for registry.mcp.fuel-infra.org/mcp/rabbitmq:ocata-unstable, this may be because there are no credentials on this request. details: (Error: image mcp/rabbitmq:ocata-unstable not found)"

This should tie in to issue #246.

intlabs commented 7 years ago

Confirmed, it appears that the entire MCP registry has either moved or been removed.

intlabs commented 7 years ago

I have retagged and published this image at: docker.io/port/fuel-mcp-rabbitmq:ocata-unstable that we can use as a workaround until this is resolved.

wilkers-steve commented 7 years ago

Thanks @intlabs