Hi,

I'm encountering an issue during the installation of Maximo Manage. Inside the pod dev-mas-masdev-manage-maxinst, I see the following error:

pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

Could you please advise if there is any configuration needed to change or add an external IP for OpenShift so that the pod can correctly resolve and access image-registry.openshift-image-registry.svc:5000?

Thanks

That is an internal OpenShift registry URL. It should be resolvable by any pod running in OCP. On the other hand, maxinst has no business trying to access internal image registry. 

Can You share a bit wider output from the logs?

Hi,

I'm encountering an issue during the installation of Maximo Manage. Inside the pod dev-mas-masdev-manage-maxinst, I see the following error:

pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

Could you please advise if there is any configuration needed to change or add an external IP for OpenShift so that the pod can correctly resolve and access image-registry.openshift-image-registry.svc:5000?

Thanks

Hi Witold Wierzchowski,

The following error appears in the logs:
[root@mas-dev core]# oc logs dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h
Error from server (BadRequest): container "manage-maxinst-maxinst" in pod "dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h" is waiting to start: trying and failing to pull image.

The Maxinst pod is attempting to pull the image from the internal registry, but it is failing to do so, as shown in the attached image.

That is an internal OpenShift registry URL. It should be resolvable by any pod running in OCP. On the other hand, maxinst has no business trying to access internal image registry. 

Can You share a bit wider output from the logs?

Hi,

I'm encountering an issue during the installation of Maximo Manage. Inside the pod dev-mas-masdev-manage-maxinst, I see the following error:

pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

Could you please advise if there is any configuration needed to change or add an external IP for OpenShift so that the pod can correctly resolve and access image-registry.openshift-image-registry.svc:5000?

Thanks

Are Your Manage builds in order? In Openshift go to Builds > Builds and change project to mas-dev-mas-manage. Check for failed builds.
Also check if the internal image registry pods are running. These pods are in the openshift-image-registry project

Hi Witold Wierzchowski,

The following error appears in the logs:
[root@mas-dev core]# oc logs dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h
Error from server (BadRequest): container "manage-maxinst-maxinst" in pod "dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h" is waiting to start: trying and failing to pull image.

The Maxinst pod is attempting to pull the image from the internal registry, but it is failing to do so, as shown in the attached image.

That is an internal OpenShift registry URL. It should be resolvable by any pod running in OCP. On the other hand, maxinst has no business trying to access internal image registry. 

Can You share a bit wider output from the logs?

Hi,

I'm encountering an issue during the installation of Maximo Manage. Inside the pod dev-mas-masdev-manage-maxinst, I see the following error:

pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

Could you please advise if there is any configuration needed to change or add an external IP for OpenShift so that the pod can correctly resolve and access image-registry.openshift-image-registry.svc:5000?

Thanks

Hi, 

The image registry pod is running and also i checked the builds all are completed. 

Thanks,

Are Your Manage builds in order? In Openshift go to Builds > Builds and change project to mas-dev-mas-manage. Check for failed builds.
Also check if the internal image registry pods are running. These pods are in the openshift-image-registry project

Hi Witold Wierzchowski,

The following error appears in the logs:
[root@mas-dev core]# oc logs dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h
Error from server (BadRequest): container "manage-maxinst-maxinst" in pod "dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h" is waiting to start: trying and failing to pull image.

The Maxinst pod is attempting to pull the image from the internal registry, but it is failing to do so, as shown in the attached image.

That is an internal OpenShift registry URL. It should be resolvable by any pod running in OCP. On the other hand, maxinst has no business trying to access internal image registry. 

Can You share a bit wider output from the logs?

Hi,

I'm encountering an issue during the installation of Maximo Manage. Inside the pod dev-mas-masdev-manage-maxinst, I see the following error:

pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

Could you please advise if there is any configuration needed to change or add an external IP for OpenShift so that the pod can correctly resolve and access image-registry.openshift-image-registry.svc:5000?

Thanks

Hi, I've been working through an internal registry issue and have made some progress in resolving it. Now, I need some help understanding the next part of the process.

I'm trying to locate where the source files for MAS Manage are copied before the image is built. I want to verify and modify something before the build process completes, but I'm not sure which directory or container path holds these files.

Has anyone knows the correct location or documentation that outlines this step?

Thanks

Hi, 

The image registry pod is running and also i checked the builds all are completed. 

Thanks,

Are Your Manage builds in order? In Openshift go to Builds > Builds and change project to mas-dev-mas-manage. Check for failed builds.
Also check if the internal image registry pods are running. These pods are in the openshift-image-registry project

Hi Witold Wierzchowski,

The following error appears in the logs:
[root@mas-dev core]# oc logs dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h
Error from server (BadRequest): container "manage-maxinst-maxinst" in pod "dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h" is waiting to start: trying and failing to pull image.

The Maxinst pod is attempting to pull the image from the internal registry, but it is failing to do so, as shown in the attached image.

That is an internal OpenShift registry URL. It should be resolvable by any pod running in OCP. On the other hand, maxinst has no business trying to access internal image registry. 

Can You share a bit wider output from the logs?

Hi,

I'm encountering an issue during the installation of Maximo Manage. Inside the pod dev-mas-masdev-manage-maxinst, I see the following error:

pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

Could you please advise if there is any configuration needed to change or add an external IP for OpenShift so that the pod can correctly resolve and access image-registry.openshift-image-registry.svc:5000?

Thanks

Hi, I've been working through an internal registry issue and have made some progress in resolving it. Now, I need some help understanding the next part of the process.

I'm trying to locate where the source files for MAS Manage are copied before the image is built. I want to verify and modify something before the build process completes, but I'm not sure which directory or container path holds these files.

Has anyone knows the correct location or documentation that outlines this step?

Thanks

Hi, 

The image registry pod is running and also i checked the builds all are completed. 

Thanks,

Are Your Manage builds in order? In Openshift go to Builds > Builds and change project to mas-dev-mas-manage. Check for failed builds.
Also check if the internal image registry pods are running. These pods are in the openshift-image-registry project

Hi Witold Wierzchowski,

The following error appears in the logs:
[root@mas-dev core]# oc logs dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h
Error from server (BadRequest): container "manage-maxinst-maxinst" in pod "dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h" is waiting to start: trying and failing to pull image.

The Maxinst pod is attempting to pull the image from the internal registry, but it is failing to do so, as shown in the attached image.

That is an internal OpenShift registry URL. It should be resolvable by any pod running in OCP. On the other hand, maxinst has no business trying to access internal image registry. 

Can You share a bit wider output from the logs?

Hi,

I'm encountering an issue during the installation of Maximo Manage. Inside the pod dev-mas-masdev-manage-maxinst, I see the following error:

pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

Could you please advise if there is any configuration needed to change or add an external IP for OpenShift so that the pod can correctly resolve and access image-registry.openshift-image-registry.svc:5000?

Thanks

Hey,

Manage final images are build using images pulled from IBM servers (cp.icr.io to be specific). Depending on the version and the add-ons You have chosen there are different images being pulled. You can check the list in the BuildConfig called admin-build-config in the mas-xxx-manage project (xxx is Your MAS instance id).

Hi, I've been working through an internal registry issue and have made some progress in resolving it. Now, I need some help understanding the next part of the process.

I'm trying to locate where the source files for MAS Manage are copied before the image is built. I want to verify and modify something before the build process completes, but I'm not sure which directory or container path holds these files.

Has anyone knows the correct location or documentation that outlines this step?

Thanks

Hi, 

The image registry pod is running and also i checked the builds all are completed. 

Thanks,

Are Your Manage builds in order? In Openshift go to Builds > Builds and change project to mas-dev-mas-manage. Check for failed builds.
Also check if the internal image registry pods are running. These pods are in the openshift-image-registry project

Hi Witold Wierzchowski,

The following error appears in the logs:
[root@mas-dev core]# oc logs dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h
Error from server (BadRequest): container "manage-maxinst-maxinst" in pod "dev-mas-masdev-manage-maxinst-5dcf4c594d-bfc4h" is waiting to start: trying and failing to pull image.

The Maxinst pod is attempting to pull the image from the internal registry, but it is failing to do so, as shown in the attached image.

That is an internal OpenShift registry URL. It should be resolvable by any pod running in OCP. On the other hand, maxinst has no business trying to access internal image registry. 

Can You share a bit wider output from the logs?

Hi,

I'm encountering an issue during the installation of Maximo Manage. Inside the pod dev-mas-masdev-manage-maxinst, I see the following error:

pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc: no such host

Could you please advise if there is any configuration needed to change or add an external IP for OpenShift so that the pod can correctly resolve and access image-registry.openshift-image-registry.svc:5000?

Thanks