Query reg custom awx-ee image

[Vibin K Madampath]

Hello All,

I'm currently running awx version 19.2.0 with awx-operator 0.10.0 and awx-ee 0.3.0 but hitting issue Runtime error: Pod running when trying to execute a job.

I saw some bugs reported but couldn't find a concrete solution to it.

May be it's because of compatibility issues bwn different components. 

Now when I'm trying to upgrade the stack, custom awx-ee image from the internal registry is not getting picked up eventhough I mentioned it in the AWX CR yml file and it looks for the image from quay.io ( fails due to no outside connections allowed).

ee_images:

  - name: custom_awx-ee

    image: ansible/custom_awx-ee:0.5.0

Is there anything am doing wrong ?? 

Appreciate your help on these issues.

Regards,

Vibin

[Vibin K Madampath]

Anyone got any inputs ?

Appreciate your help.

[Abhinit Mallick]

Hi Vibin 

It is not clear from the initial what is the actual issue.

Please clearly mention 

1. Please first upgrade to awx Operator 0.13.0 with awx 19.3.0 and confirm if the issue exists 

2. If the issue exists then please first mention what is the problem with the default awx-ee

3. If you are using custom ee how have you created it 

    If you have created custom ee then you will need to upload it to awx and then change the job templates to use your custom ee

Regards

Abhinit 

[Kosala Atapattu]

Hi Vibin,

ee_images:

  - name: custom_awx-ee

    image: ansible/custom_awx-ee:0.5.0

Not sure where you get this code segment in, if you refer to a image as ansible/custom_awx-ee:0.5.0 it will be looked up in DockerHub. You might need to change the image path to lookup quay.io.

Cheers,

Ko

 

Is there anything am doing wrong ?? 

Appreciate your help on these issues.

Regards,

Vibin

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/CAE8NWtNB6N0NSpPzd7xQASi7ABs4YpwdF_DkFX-spNx2xW_5xA%40mail.gmail.com.

[Vibin K Madampath]

Hi Ko,

Thanks for your response. 

But I disagree on your point because I've similar statement for the awx image and it is being picked up successfully.

awx.yml:

image: ansible/awx_custom

image_version: 19.2.2

ee_images:

  - name: custom_awx-ee

    image: ansible/custom_awx-ee:0.5.0

Only problem is with ee_images.

Regards, 

Vibin

[Vibin K Madampath]

Hi Abhinit,

Thanks for your reply.

Yeah, am currently running on operator 10, awx 19.2.0 and awx-ee 0.3.0

I'm trying to upgrade to operator 13, awx 19.3.0 and awx-ee 0.6.0

All the images are in my local repository - artifactory. 

The operator is coming up properly without any issues. When I deploy awx, all the images except awx-ee is not picked up and the deployment fails with 3/4 pods running. 

It always looks for latest awx-ee image from quay.io

It is expected to pick the image I mentioned under ee_images section in the awx CR file but it never happens in the newer operator versions (Works in operator version 10.0.0)

Even I tried giving the complete repository path, even then it didn't pick. Not sure whether it's a bug or the way of mentioning ee_images changed in the newer versions (haven't found anything)

Regards,

Vibin

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/ef995b20-90da-477b-80f2-9e0c60e48a88n%40googlegroups.com.