Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DEV-1039] Pull retag push fix #129

Merged
merged 1 commit into from
Sep 9, 2022
Merged

[DEV-1039] Pull retag push fix #129

merged 1 commit into from
Sep 9, 2022

Conversation

g0rgamesh
Copy link
Contributor

@g0rgamesh g0rgamesh commented Sep 9, 2022

  • changed pull location to new one in quay.io
  • changed tag naming to correct one

@g0rgamesh g0rgamesh changed the title Pull retag push fix [DEV-1039] Pull retag push fix Sep 9, 2022
@g0rgamesh g0rgamesh changed the base branch from stable/yoga to master September 9, 2022 09:59
Copy link
Member

@priteau priteau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix the typo in the commit message. Maybe add a small description.
Add that it closes #126

Copy link
Member

@priteau priteau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking of adding this new information to the commit rather than the PR.

@g0rgamesh g0rgamesh force-pushed the pull-retag-push-fix branch 2 times, most recently from 0af7c59 to 38a1f79 Compare September 9, 2022 12:08
@g0rgamesh g0rgamesh merged commit 71b4022 into master Sep 9, 2022
@g0rgamesh g0rgamesh deleted the pull-retag-push-fix branch September 9, 2022 12:19
@@ -80,24 +80,24 @@
- name: Pull container images (may take a long time)
become: true
vars:
remote_image: "{% if docker_pull_registry != '' %}{{ docker_pull_registry }}/{% endif %}{{ docker_pull_namespace }}/{{ item }}:{{ docker_pull_tag }}"
remote_image: "{% if docker_pull_registry != '' %}{{ docker_pull_registry }}/{% endif %}{{ docker_pull_namespace }}/{{ item }}:{{ docker_pull_tag }}-{{ kolla_base_distro }}-{{ ansible_facts.distribution_release }}"
Copy link
Member

@markgoddard markgoddard Sep 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think ansible_facts.distribution_release is always correct here. For example, on CentOS stream the image suffix is stream8.

Copy link
Contributor Author

@g0rgamesh g0rgamesh Sep 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would ansible_distribution_release be better?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's just a different way of accessing the same thing. Here's how kolla-ansible does it:

https://opendev.org/openstack/kolla-ansible/src/commit/a396284a83e7624a951190b36fbad79812f1937d/ansible/group_vars/all.yml#L1196

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants