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

Installation failing because Openstack image already exists #21

Open
fgiorgetti opened this issue Apr 19, 2021 · 0 comments
Open

Installation failing because Openstack image already exists #21

fgiorgetti opened this issue Apr 19, 2021 · 0 comments

Comments

@fgiorgetti
Copy link

Although logs say it is reusing the image, the installation fails.
If I remove the image from my openstack tenant and retry, it works.

2021-04-19 14:18:01 jenkins-slave root[3156] INFO Reusing found image in openstack osia-rhcos-47.83.202102090044-0
Traceback (most recent call last):
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz_/lib/python3.6/site-packages/osia/installer/clouds/openstack.py", line 210, in resolve_image
add_cluster(osp_connection, image, cluster_name)
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz_/lib/python3.6/site-packages/osia/installer/clouds/openstack.py", line 145, in add_cluster
osp_connection.image.update_image(image, osia_clusters=','.join(clusters))
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz_/lib/python3.6/site-packages/openstack/image/v2/proxy.py", line 516, in update_image
return self.update(image.Image, image, **attrs)
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz
/lib/python3.6/site-packages/openstack/proxy.py", line 47, in check
return method(self, expected, actual, *args, **kwargs)
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz
/lib/python3.6/site-packages/openstack/proxy.py", line 435, in update
return res.commit(self, base_path=base_path)
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz
/lib/python3.6/site-packages/openstack/resource.py", line 1543, in commit
retry_on_conflict=retry_on_conflict)
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz
/lib/python3.6/site-packages/openstack/resource.py", line 1569, in _commit
self.translate_response(response, has_body=has_body)
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz
/lib/python3.6/site-packages/openstack/resource.py", line 1158, in translate_response
exceptions.raise_from_response(response, error_message=error_message)
File "/home/cloud-user/.local/share/virtualenvs/ocp4-configuration-b4-2WUz
/lib/python3.6/site-packages/openstack/exceptions.py", line 235, in raise_from_response
http_status=http_status, request_id=request_id
openstack.exceptions.ConflictException: ConflictException: 409: Client Error for url: https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13292/v2/images/39513c9f-9035-49ef-8119-aa52b03b6054, Conflict

mijaros added a commit that referenced this issue Aug 11, 2021
While destroying clusters it might happen, that the DNS records are
already removed from route53. This should'nt prevent the osia from
continuing in cluster deletion. In order to fix this, it is necessary
to catch the exception thrown by boto3. It poses a bit of danger in case
of cluster installation, but the message and the error is properly logged,
so user should be informed that something bad happended with the DNS records.
@mijaros mijaros linked a pull request Aug 11, 2021 that will close this issue
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

No branches or pull requests

1 participant