Running tempest on the 16.1 Deployment with collocated Ceph storage cluster fails with below issue: 2020-07-01 14:55:17.150 92139 INFO config_tempest.constants [-] Creating image 'cirros-0.4.0-x86_64-disk.img_alt' 2020-07-01 14:55:17.151 92139 INFO config_tempest.constants [-] Image 'https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img' already fetched to '/home/stack/tempest-dir/etc/cirros-0.4.0-x86_64-disk.img'. 2020-07-01 14:55:17.151 92139 INFO config_tempest.constants [-] Uploading image 'cirros-0.4.0-x86_64-disk.img_alt' from '/home/stack/tempest-dir/etc/cirros-0.4.0-x86_64-disk.img' 2020-07-01 14:55:17.362 92139 INFO tempest.lib.common.rest_client [req-1b9d2fc0-5888-45b2-b7cb-e020df5f331a ] Request (main): 201 POST http://10.0.0.140:9292/v2/images 0.210s 2020-07-01 14:57:17.414 92139 WARNING urllib3.connectionpool [-] Retrying (Retry(total=9, connect=None, read=None, redirect=5, status=None)) after connection broken by 'ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))': /v2/images/fc831b93-b9c6-48f5-9ece-6dc29c9a316b/file 2020-07-01 14:57:17.683 92139 INFO tempest.lib.common.rest_client [req-2b6c9fef-fee4-4775-9768-c70ca4ad3ddf ] Request (main): 409 PUT http://10.0.0.140:9292/v2/images/fc831b93-b9c6-48f5-9ece-6dc29c9a316b/file 120.321s 2020-07-01 14:57:17.684 92139 CRITICAL tempest [-] Unhandled error: tempest.lib.exceptions.Conflict: Conflict with state of target resource Details: b'409 Conflict\n\nImage status transition from saving to saving is not allowed\n\n ' 2020-07-01 14:57:17.684 92139 ERROR tempest Traceback (most recent call last): 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/bin/discover-tempest-config", line 10, in <module> 2020-07-01 14:57:17.684 92139 ERROR tempest sys.exit(main()) 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/lib/python3.6/site-packages/config_tempest/main.py", line 606, in main 2020-07-01 14:57:17.684 92139 ERROR tempest verbose=args.verbose 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/lib/python3.6/site-packages/config_tempest/main.py", line 545, in config_tempest 2020-07-01 14:57:17.684 92139 ERROR tempest image.create_tempest_images(conf) 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/lib/python3.6/site-packages/config_tempest/services/image.py", line 119, in create_tempest_images 2020-07-01 14:57:17.684 92139 ERROR tempest image_dest=img_path) 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/lib/python3.6/site-packages/config_tempest/services/image.py", line 161, in find_or_upload_image 2020-07-01 14:57:17.684 92139 ERROR tempest image = self._upload_image(image_name, image_dest) 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/lib/python3.6/site-packages/config_tempest/services/image.py", line 212, in _upload_image 2020-07-01 14:57:17.684 92139 ERROR tempest self.client.store_image_file(image['id'], data) 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/lib/python3.6/site-packages/tempest/lib/services/image/v2/images_client.py", line 151, in store_image_file 2020-07-01 14:57:17.684 92139 ERROR tempest body=data, chunked=True) 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py", line 687, in request 2020-07-01 14:57:17.684 92139 ERROR tempest self._error_checker(resp, resp_body) 2020-07-01 14:57:17.684 92139 ERROR tempest File "/usr/lib/python3.6/site-packages/tempest/lib/common/rest_client.py", line 808, in _error_checker 2020-07-01 14:57:17.684 92139 ERROR tempest raise exceptions.Conflict(resp_body, resp=resp) 2020-07-01 14:57:17.684 92139 ERROR tempest tempest.lib.exceptions.Conflict: Conflict with state of target resource 2020-07-01 14:57:17.684 92139 ERROR tempest Details: b'409 Conflict\n\nImage status transition from saving to saving is not allowed\n\n ' 2020-07-01 14:57:17.684 92139 ERROR tempest
Hello, Two questions: 1) Does it only happen when using colocated Ceph? 2) Did this job use to work and only started to fail recently, or is this a new job.
Hi, What is the solution for this, I am currently facing this issue, updating the mysql database is also not fixing this.
(In reply to swogat pradhan from comment #6) > Hi, What is the solution for this, I am currently facing this issue, > updating the mysql database is also not fixing this. This bug was closed as "NOTABUG" since there was not truly a bug after all. If you're a customer, I suggest you open a customer case, otherwise please report your issue on Launchpad and attach all relevant config files & logs.