[Yahoo-eng-team] [Bug 2061947] [NEW] stores-info --detail command fails if swift store is enabled
Public bug reported: If you enable swift store in multiple stores setup then glance stores- info --detail or glance stores-info command fails with 500 error "oslo_config.cfg.NoSuchOptError: no such option store_description in group [dummy]". Note: This error only occurs when you specify "swift_store_config_file = /etc/glance/glance-swift-store.conf and swift_store_multi_tenant = True" for swift store. Ideally it is recommended not to use "swift_store_config_file" when multi tenant is enabled for swift but it should not fail with 500 error and give appropriate 400 BadRequest error to the user. Sample configuration glance-api.conf: [DEFAULT] enabled_backends = dummy:swift [dummy] swift_store_multi_tenant = True default_swift_reference = ref1 swift_store_config_file = /etc/glance/glance-swift-store.conf swift_store_create_container_on_put = True store_description = "This is swift store" Also in second scenario if you set swift store as below in glance-api.conf then it gives 500 error "Apr 17 04:40:20 akekane-zed-dev glance-api[3389648]: ERROR glance.common.wsgi [None req-7dcd5c18-7b31-43e5-9b22-77e20505cab7 admin admin] Caught error: 'MultiTenantStore' object has no attribute 'container': AttributeError: 'MultiTenantStore' object has no attribute 'container'" fot glance stores-info --detail command [dummy] swift_store_multi_tenant = True default_swift_reference = ref1 swift_store_create_container_on_put = True store_description = "This is swift store" Ideally in scenario 1 glance stores-info --detail command should raise 400 Bad Request and for scenario 2 we need to identify what is ideal configuration for swift multi tenant and return the response accordingly. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/2061947 Title: stores-info --detail command fails if swift store is enabled Status in Glance: New Bug description: If you enable swift store in multiple stores setup then glance stores- info --detail or glance stores-info command fails with 500 error "oslo_config.cfg.NoSuchOptError: no such option store_description in group [dummy]". Note: This error only occurs when you specify "swift_store_config_file = /etc/glance/glance-swift-store.conf and swift_store_multi_tenant = True" for swift store. Ideally it is recommended not to use "swift_store_config_file" when multi tenant is enabled for swift but it should not fail with 500 error and give appropriate 400 BadRequest error to the user. Sample configuration glance-api.conf: [DEFAULT] enabled_backends = dummy:swift [dummy] swift_store_multi_tenant = True default_swift_reference = ref1 swift_store_config_file = /etc/glance/glance-swift-store.conf swift_store_create_container_on_put = True store_description = "This is swift store" Also in second scenario if you set swift store as below in glance-api.conf then it gives 500 error "Apr 17 04:40:20 akekane-zed-dev glance-api[3389648]: ERROR glance.common.wsgi [None req-7dcd5c18-7b31-43e5-9b22-77e20505cab7 admin admin] Caught error: 'MultiTenantStore' object has no attribute 'container': AttributeError: 'MultiTenantStore' object has no attribute 'container'" fot glance stores-info --detail command [dummy] swift_store_multi_tenant = True default_swift_reference = ref1 swift_store_create_container_on_put = True store_description = "This is swift store" Ideally in scenario 1 glance stores-info --detail command should raise 400 Bad Request and for scenario 2 we need to identify what is ideal configuration for swift multi tenant and return the response accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/2061947/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 2054732] Re: glance http store is broken with dnspytho 2.6.0
** Changed in: glance
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2054732
Title:
glance http store is broken with dnspytho 2.6.0
Status in Glance:
Fix Released
Bug description:
Our gate is broken with new version of dnspython 2.6.0.
You can see nova-ceph-multistore job started failing since today [1]
Last time it passed the dnspython 2.5.0 was used.
[1]
https://zuul.opendev.org/t/openstack/builds?job_name=nova-ceph-multistore=0
Stacktrace in g-api:
Feb 22 12:51:43.010574 np0036837391 glance-api[105921]: ERROR
glance.async_.flows._internal_plugins.web_download [-] Task
3ff71b99-5784-4fbd-aa33-c287cc7de816 failed with exception : urllib.error.URLError:
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: WARNING
glance.async_.taskflow_executor [-] Task
'api_image_import-WebDownload-3ff71b99-5784-4fbd-aa33-c287cc7de816'
(959ff8ac-9ba5-406b-b130-8d9a9846b97e) transitioned into state 'FAILURE' from
state 'RUNNING'
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: 4 predecessors (most
recent first):
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: Flow
'api_image_import'
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: |__Atom
'api_image_import-ImageLock-3ff71b99-5784-4fbd-aa33-c287cc7de816' {'intention':
'EXECUTE', 'state': 'SUCCESS', 'requires': {}, 'provides': None}
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: |__Atom
'api_image_import_retry' {'intention': 'EXECUTE', 'state': 'SUCCESS',
'requires': {}, 'provides': [(None, {})]}
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: |__Flow
'api_image_import': urllib.error.URLError:
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor Traceback (most recent call last):
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/eventlet/support/greendns.py",
line 463, in resolve
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor return _proxy.query(name, rdtype,
raise_on_no_answer=raises,
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/eventlet/support/greendns.py",
line 419, in query
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor return end()
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/eventlet/support/greendns.py",
line 398, in end
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor raise result[1]
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/eventlet/support/greendns.py",
line 379, in step
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor a = fun(*args, **kwargs)
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/dns/resolver.py", line 1364,
in query
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor return self.resolve(
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/dns/resolver.py", line 1321,
in resolve
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor timeout = self._compute_timeout(start,
lifetime, resolution.errors)
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/dns/resolver.py", line 1075,
in _compute_timeout
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor raise LifetimeTimeout(timeout=duration,
errors=errors)
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor dns.resolver.LifetimeTimeout: The resolution
lifetime expired after 5.102 seconds: Server Do53:127.0.0.1@53 answered udp()
got an unexpected keyword argument 'ignore_errors'; Server Do53:127.0.0.1@53
answered udp() got an unexpected keyword argument 'ignore_errors'; Server
Do53:127.0.0.1@53 answered udp() got an unexpected keyword argument
'ignore_errors'; Server Do53:127.0.0.1@53 answered udp() got an unexpected
keyword argument 'ignore_errors'; Server Do53:127.0.0.1@53 answered udp() got
an unexpected keyword argument 'ignore_errors'; Server
[Yahoo-eng-team] [Bug 2054732] [NEW] glance http store is broken with dnspytho 2.6.0
Public bug reported:
Our gate is broken with new version of dnspython 2.6.0.
You can see nova-ceph-multistore job started failing since today [1]
Last time it passed the dnspython 2.5.0 was used.
[1]
https://zuul.opendev.org/t/openstack/builds?job_name=nova-ceph-multistore=0
Stacktrace in g-api:
Feb 22 12:51:43.010574 np0036837391 glance-api[105921]: ERROR
glance.async_.flows._internal_plugins.web_download [-] Task
3ff71b99-5784-4fbd-aa33-c287cc7de816 failed with exception : urllib.error.URLError:
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: WARNING
glance.async_.taskflow_executor [-] Task
'api_image_import-WebDownload-3ff71b99-5784-4fbd-aa33-c287cc7de816'
(959ff8ac-9ba5-406b-b130-8d9a9846b97e) transitioned into state 'FAILURE' from
state 'RUNNING'
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: 4 predecessors (most
recent first):
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: Flow
'api_image_import'
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: |__Atom
'api_image_import-ImageLock-3ff71b99-5784-4fbd-aa33-c287cc7de816' {'intention':
'EXECUTE', 'state': 'SUCCESS', 'requires': {}, 'provides': None}
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: |__Atom
'api_image_import_retry' {'intention': 'EXECUTE', 'state': 'SUCCESS',
'requires': {}, 'provides': [(None, {})]}
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: |__Flow
'api_image_import': urllib.error.URLError:
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor Traceback (most recent call last):
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/eventlet/support/greendns.py",
line 463, in resolve
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor return _proxy.query(name, rdtype,
raise_on_no_answer=raises,
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/eventlet/support/greendns.py",
line 419, in query
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor return end()
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/eventlet/support/greendns.py",
line 398, in end
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor raise result[1]
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/eventlet/support/greendns.py",
line 379, in step
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor a = fun(*args, **kwargs)
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/dns/resolver.py", line 1364,
in query
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor return self.resolve(
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/dns/resolver.py", line 1321,
in resolve
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor timeout = self._compute_timeout(start,
lifetime, resolution.errors)
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor File
"/opt/stack/data/venv/lib/python3.10/site-packages/dns/resolver.py", line 1075,
in _compute_timeout
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor raise LifetimeTimeout(timeout=duration,
errors=errors)
Feb 22 12:51:43.017897 np0036837391 glance-api[105921]: ERROR
glance.async_.taskflow_executor dns.resolver.LifetimeTimeout: The resolution
lifetime expired after 5.102 seconds: Server Do53:127.0.0.1@53 answered udp()
got an unexpected keyword argument 'ignore_errors'; Server Do53:127.0.0.1@53
answered udp() got an unexpected keyword argument 'ignore_errors'; Server
Do53:127.0.0.1@53 answered udp() got an unexpected keyword argument
'ignore_errors'; Server Do53:127.0.0.1@53 answered udp() got an unexpected
keyword argument 'ignore_errors'; Server Do53:127.0.0.1@53 answered udp() got
an unexpected keyword argument 'ignore_errors'; Server Do53:127.0.0.1@53
answered udp() got an unexpected keyword argument 'ignore_errors'
** Affects: glance
Importance: Critical
Status: In Progress
** Changed in: glance
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
[Yahoo-eng-team] [Bug 2051914] [NEW] Copying existing image to AWS S3 fails for files larger than 5GB
Public bug reported: Copying of larger images using copy-image import method fails for AWS S3 store. The reason is while copying the image it uses 'single_part' upload for uploading large images. On normal image creation process it does uses 'multi_part' upload and thus works fine. After further analyzing the code in glance, image size is not passed to [1] which is required to decide the upload mechanism on S3 side. [1] https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/s3.py#L628 Possible solution: Since we have image size available at the time of copying the image, we should pass it all the way to s3 driver through onion layer of glance. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/2051914 Title: Copying existing image to AWS S3 fails for files larger than 5GB Status in Glance: New Bug description: Copying of larger images using copy-image import method fails for AWS S3 store. The reason is while copying the image it uses 'single_part' upload for uploading large images. On normal image creation process it does uses 'multi_part' upload and thus works fine. After further analyzing the code in glance, image size is not passed to [1] which is required to decide the upload mechanism on S3 side. [1] https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/s3.py#L628 Possible solution: Since we have image size available at the time of copying the image, we should pass it all the way to s3 driver through onion layer of glance. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/2051914/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 2051126] [NEW] stores-info fails if unrecognised backend specified
Public bug reported: If deployer specifies invalid backend for glance using 'enabled_backends' in glance-api.conf file then glance stores-info command fails with HTTP 500 error with below stacktrace; Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi [None req-71e90940-8b19-4711-b2fa-910c145c1960 admin admin] Caught error: no such option foo in group [DEFAULT]: oslo_config.cfg.NoSuchOptError: no such option foo in group [DEFAULT] Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi Traceback (most recent call last): Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_config/cfg.py", line 2219, in __getattr__ Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi return self._get(name) Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_config/cfg.py", line 2653, in _get Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi value, loc = self._do_get(name, group, namespace) Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_config/cfg.py", line 2671, in _do_get Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi info = self._get_opt_info(name, group) Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_config/cfg.py", line 2876, in _get_opt_info Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi raise NoSuchOptError(opt_name, group) Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi oslo_config.cfg.NoSuchOptError: no such option foo in group [DEFAULT] Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi During handling of the above exception, another exception occurred: Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi Traceback (most recent call last): Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1297, in __call__ Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi action_result = self.dispatch(self.controller, action, Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1340, in dispatch Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi return method(*args, **kwargs) Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/api/v2/discovery.py", line 68, in get_stores Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi description = getattr(CONF, backend).store_description Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_config/cfg.py", line 2223, in __getattr__ Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi raise NoSuchOptError(name) Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi oslo_config.cfg.NoSuchOptError: no such option foo in group [DEFAULT] Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi Jan 24 14:25:08 devstack-caracal glance-api[1906424]: INFO eventlet.wsgi.server [None req-71e90940-8b19-4711-b2fa-910c145c1960 admin admin] 10.0.109.128,10.0.109.128 - - [24/Jan/2024 14:25:08] "GET /v2/info/stores HTTP/1.1" 500 454 0.075514 How to reproduce: 1. Define enabled_backends as shown below in glance-api.conf [DEFAULT] enabled_backends = fast:file,foo:bar [glance_store] default_backend = fast [fast] filesystem_store_datadir = /opt/stack/data/glance/images/ [foo] foo = bar 2. Restart g-api service 3. Run glance stores-info command ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/2051126 Title: stores-info fails if unrecognised backend specified Status in Glance: New Bug description: If deployer specifies invalid backend for glance using 'enabled_backends' in glance-api.conf file then glance stores-info command fails with HTTP 500 error with below stacktrace; Jan 24 14:25:08 devstack-caracal glance-api[1906424]: ERROR glance.common.wsgi [None req-71e90940-8b19-4711-b2fa-910c145c1960 admin admin] Caught error: no
[Yahoo-eng-team] [Bug 2006490] Re: Limit CaptureRegion sizes in format_inspector for VMDK and VHDX
Fixed in master with, https://review.opendev.org/c/openstack/glance/+/871831 ** Also affects: glance/zed Importance: Undecided Status: Fix Committed ** Also affects: glance/xena Importance: Undecided Status: New ** Also affects: glance/yoga Importance: Undecided Status: New ** Changed in: glance/zed Status: Fix Committed => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/2006490 Title: Limit CaptureRegion sizes in format_inspector for VMDK and VHDX Status in Glance: In Progress Status in Glance xena series: New Status in Glance yoga series: New Status in Glance zed series: In Progress Bug description: VMDK: When parsing a VMDK file to calculate its size, the format_inspector determines the location of the Descriptor section by reading two uint64 from the headers of the file and uses them to create the descriptor CaptureRegion. It would be possible to craft a VMDK file that commands the format_inspector to create a very big CaptureRegion, thus exhausting resources on the glance-api process. VHDX: It is a bit more involved, but similar: when looking for the VIRTUAL_DISK_SIZE metadata, the format_inspector was creating an unbounded CaptureRegion. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/2006490/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 2006490] [NEW] Limit CaptureRegion sizes in format_inspector for VMDK and VHDX
Public bug reported: VMDK: When parsing a VMDK file to calculate its size, the format_inspector determines the location of the Descriptor section by reading two uint64 from the headers of the file and uses them to create the descriptor CaptureRegion. It would be possible to craft a VMDK file that commands the format_inspector to create a very big CaptureRegion, thus exhausting resources on the glance-api process. VHDX: It is a bit more involved, but similar: when looking for the VIRTUAL_DISK_SIZE metadata, the format_inspector was creating an unbounded CaptureRegion. ** Affects: glance Importance: Undecided Status: In Progress ** Affects: glance/xena Importance: Undecided Status: New ** Affects: glance/yoga Importance: Undecided Status: New ** Affects: glance/zed Importance: Undecided Status: In Progress ** Changed in: glance Status: New => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/2006490 Title: Limit CaptureRegion sizes in format_inspector for VMDK and VHDX Status in Glance: In Progress Status in Glance xena series: New Status in Glance yoga series: New Status in Glance zed series: In Progress Bug description: VMDK: When parsing a VMDK file to calculate its size, the format_inspector determines the location of the Descriptor section by reading two uint64 from the headers of the file and uses them to create the descriptor CaptureRegion. It would be possible to craft a VMDK file that commands the format_inspector to create a very big CaptureRegion, thus exhausting resources on the glance-api process. VHDX: It is a bit more involved, but similar: when looking for the VIRTUAL_DISK_SIZE metadata, the format_inspector was creating an unbounded CaptureRegion. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/2006490/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1978971] [NEW] Graceful shutdown not working for wsgi and uwsgi
Public bug reported: Earlier when we added config reloading functionality we made provision for the workers who were performing existing tasks should complete those before terminating them. The sequence was likely below; On receipt of a SIGHUP signal the master process will: * reload the configuration * send a SIGHUP to the original workers * start (a potentially different number of) new workers with the new configuration * its listening socket will *not* be closed On receipt of a SIGHUP signal each original worker process will: * close the listening socket so as not to accept new requests * complete any in-flight requests * complete async requests (V1 create with copy-from option and V2 task api) * exit Recently while working on one of the functionality I found that the workers are not waiting to complete any in-flight requests due to some errors. Following are some important logs; [1] Logs for upload/import request which gets terminated on reload/sighup [2] Reproducer [1] https://paste.opendev.org/show/bTjORjtLtbhUe93xQFDu/ [2] https://paste.opendev.org/show/bFqCD4U4P0Q8MyIrsO4J/ ** Affects: glance Importance: High Status: New ** Changed in: glance Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1978971 Title: Graceful shutdown not working for wsgi and uwsgi Status in Glance: New Bug description: Earlier when we added config reloading functionality we made provision for the workers who were performing existing tasks should complete those before terminating them. The sequence was likely below; On receipt of a SIGHUP signal the master process will: * reload the configuration * send a SIGHUP to the original workers * start (a potentially different number of) new workers with the new configuration * its listening socket will *not* be closed On receipt of a SIGHUP signal each original worker process will: * close the listening socket so as not to accept new requests * complete any in-flight requests * complete async requests (V1 create with copy-from option and V2 task api) * exit Recently while working on one of the functionality I found that the workers are not waiting to complete any in-flight requests due to some errors. Following are some important logs; [1] Logs for upload/import request which gets terminated on reload/sighup [2] Reproducer [1] https://paste.opendev.org/show/bTjORjtLtbhUe93xQFDu/ [2] https://paste.opendev.org/show/bFqCD4U4P0Q8MyIrsO4J/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1978971/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1973631] [NEW] List call for metadef namespaces returns 404 not found while fetching resource_types
Public bug reported: We encountered this issue in our glance-tempest-plugin 'test_list_namespace' test, where while running in parallel mode it tries to fetch resource_type for a namespace which is actually deleted and fails with 404 Not Found error. Actually while fetching the resource_types associated with namespace if namespace is not exist then it should return empty list rather than raising 404 not found from that point. ** Affects: glance Importance: Undecided Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1973631 Title: List call for metadef namespaces returns 404 not found while fetching resource_types Status in Glance: In Progress Bug description: We encountered this issue in our glance-tempest-plugin 'test_list_namespace' test, where while running in parallel mode it tries to fetch resource_type for a namespace which is actually deleted and fails with 404 Not Found error. Actually while fetching the resource_types associated with namespace if namespace is not exist then it should return empty list rather than raising 404 not found from that point. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1973631/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1971521] [NEW] Correction in response code for PUT /v2/cache/{image_id} API
Public bug reported:
The newly added cache API ``PUT /v2/cache/{image_id}`` returns http 200
response to user whereas as per the original proposal [1] it should have
been http 202.
[1] https://opendev.org/openstack/glance-
specs/blame/commit/2638ada23d92f714f54b71db00330e4a6c921beb/specs/xena/approved/glance/cache-
api.rst#L153
** Affects: glance
Importance: Undecided
Assignee: Abhishek Kekane (abhishek-kekane)
Status: New
** Changed in: glance
Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)
** Description changed:
The newly added cache API ``PUT /v2/cache/{image_id}`` returns http 200
response to user whereas as per the original proposal [1] it should have
been http 202.
+
+ [1] https://opendev.org/openstack/glance-
+
specs/blame/commit/2638ada23d92f714f54b71db00330e4a6c921beb/specs/xena/approved/glance/cache-
+ api.rst#L153
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1971521
Title:
Correction in response code for PUT /v2/cache/{image_id} API
Status in Glance:
New
Bug description:
The newly added cache API ``PUT /v2/cache/{image_id}`` returns http
200 response to user whereas as per the original proposal [1] it
should have been http 202.
[1] https://opendev.org/openstack/glance-
specs/blame/commit/2638ada23d92f714f54b71db00330e4a6c921beb/specs/xena/approved/glance/cache-
api.rst#L153
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1971521/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1963282] [NEW] Fix the section in release notes for fix-md-tag-create-multiple-c04756cf5155983d.yaml
Public bug reported: Glance yoga release notes generates one warning and as a result it will fail to list it on release page [1] like it is showing for Xena release. The warning in the test log is; "The Fixes section of releasenotes/notes/fix-md-tag-create- multiple-c04756cf5155983d.yaml is not a recognized section. It should be one of: features, issues, upgrade, deprecations, critical, security, fixes, other. This will be an error in a future release." [1] https://releases.openstack.org/teams/glance.html#team-yoga-glance ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Importance: Undecided => High ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1963282 Title: Fix the section in release notes for fix-md-tag-create- multiple-c04756cf5155983d.yaml Status in Glance: New Bug description: Glance yoga release notes generates one warning and as a result it will fail to list it on release page [1] like it is showing for Xena release. The warning in the test log is; "The Fixes section of releasenotes/notes/fix-md-tag-create- multiple-c04756cf5155983d.yaml is not a recognized section. It should be one of: features, issues, upgrade, deprecations, critical, security, fixes, other. This will be an error in a future release." [1] https://releases.openstack.org/teams/glance.html#team-yoga-glance To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1963282/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1939169] Re: glance md-tag-create-multiple overwrites existing tags
** Changed in: glance/xena
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1939169
Title:
glance md-tag-create-multiple overwrites existing tags
Status in Glance:
Fix Released
Status in Glance xena series:
Won't Fix
Bug description:
Our md-tag-create-multiple (/v2/metadefs/namespaces/{namespace_name}/tags)
[1] API overwrites existing tags for specified namespace rather than creating
new one in addition to the existing tags.
Where as if you try to create different tags using md-tag-create
(/v2/metadefs/namespaces/{namespace_name}/tags/{tag_name}) it is working as
expected, means adding new tag in addition to existing ones.
Steps to reproduce:
1. source using admin credentials
$ source devstack/openrc admin admin
2. Create new public namespace
$ glance md-namespace-create TagsBugNamespace --visibility public
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T17:43:03Z |
| namespace | TagsBugNamespace |
| owner | a14a058e2d1540c3a0dc7c397c55174e |
| protected | False|
| schema | /v2/schemas/metadefs/namespace |
| updated_at | 2021-08-06T17:43:03Z |
| visibility | public |
++--+
3. Create single tag using md-tag-create command
$ glance md-tag-create TagsBugNamespace --name tag1
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T17:57:37Z |
| name | tag1 |
| updated_at | 2021-08-06T17:57:37Z |
++--+
4. Create another tag
$ glance md-tag-create TagsBugNamespace --name tag2
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T17:57:37Z |
| name | tag2 |
| updated_at | 2021-08-06T17:57:37Z |
++--+
5. Verify that we have two tags in the list
$ glance md-tag-list TagsBugNamespace
+--+
| name |
+--+
| tag2 |
| tag1 |
+--+
6. Add more tags using md-tag-crate-multiple command
$ glance md-tag-create-multiple TagsBugNamespace --names
TestTag1141=TestTag2411 --delim =
+-+
| name|
+-+
| TestTag1141 |
| TestTag2411 |
+-+
7. Now run tags list command again
$ glance md-tag-list TagsBugNamespace
+-+
| name|
+-+
| TestTag2411 |
| TestTag1141 |
+-+
Expected result:
These new tags should have been added to existing tags.
Actual result:
Existing tags gets deleted and only newly added tags using
md-tag-crate-multiple command remains.
* This is further to show that adding new tag using md-tag-create command now
will add a new tag and does not overwrite existing ones.
$ glance md-tag-create TagsBugNamespace --name tag3
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T18:12:14Z |
| name | tag3 |
| updated_at | 2021-08-06T18:12:14Z |
++--+
* Verify that we have not overwritten existing tags now;
$ glance md-tag-list TagsBugNamespace
+-+
| name|
+-+
| tag3|
| TestTag2411 |
| TestTag1141 |
+-+
[1] https://docs.openstack.org/api-ref/image/v2/metadefs-
index.html?expanded=create-tag-definition-detail,create-tags-
detail,get-tag-definition-detail,delete-all-tag-definitions-
detail#create-tags
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1939169/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1959361] [NEW] Fix failing copy_image flow init in wallaby
Public bug reported: The new networkx requirement apparently causes us to fail the test_init_copy_flow_as_non_owner test because a None value can not be added to the flow graph. This just mocks out the glance_store call that is failing to get the staging store to avoid us choking there so we can proceed. We are just testing get_flow so we never use it anyway. This issue was fixed in Xena but now we realised that it is causing problem in Wallaby as well. ** Affects: glance Importance: Undecided Status: Fix Released ** Affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/wallaby Importance: Undecided Status: New ** Changed in: glance Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1959361 Title: Fix failing copy_image flow init in wallaby Status in Glance: Fix Released Status in Glance wallaby series: New Bug description: The new networkx requirement apparently causes us to fail the test_init_copy_flow_as_non_owner test because a None value can not be added to the flow graph. This just mocks out the glance_store call that is failing to get the staging store to avoid us choking there so we can proceed. We are just testing get_flow so we never use it anyway. This issue was fixed in Xena but now we realised that it is causing problem in Wallaby as well. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1959361/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1944445] [NEW] Bump oslo.policy minimum version to 3.8.1
Public bug reported: Most of the S-RBAC related testing is done with oslo.policy 3.8.1 so increasing minimum version to 3.8.1 for Xena. ** Affects: glance Importance: Undecided Status: In Progress ** Affects: glance/xena Importance: Undecided Status: New ** Affects: glance/yoga Importance: Undecided Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/195 Title: Bump oslo.policy minimum version to 3.8.1 Status in Glance: In Progress Status in Glance xena series: New Status in Glance yoga series: In Progress Bug description: Most of the S-RBAC related testing is done with oslo.policy 3.8.1 so increasing minimum version to 3.8.1 for Xena. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1943985] [NEW] Glance fails to build with oslo.log 4.4.0 for Debian platform
Public bug reported: Glance RC1 for Xena fails to build with oslo.log 4.4.0 for Debian platform so we need to bump the oslo.log version in requirements.txt Failures during discovery = --- import errors --- Failed to import test module: glance.tests.unit.api.middleware.test_cache_manage Traceback (most recent call last): File "/usr/lib/python3.9/unittest/loader.py", line 436, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.9/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/<>/glance/tests/unit/api/middleware/test_cache_manage.py", line 13, in from glance.api.middleware import cache_manage File "/<>/glance/api/middleware/cache_manage.py", line 23, in from glance.api.v2 import cached_images File "/<>/glance/api/v2/cached_images.py", line 23, in from glance.api import policy File "/<>/glance/api/policy.py", line 30, in from glance import policies File "/<>/glance/policies/__init__.py", line 17, in from glance.policies import metadef File "/<>/glance/policies/metadef.py", line 39, in deprecated_since=versionutils.deprecated.XENA AttributeError: type object 'deprecated' has no attribute 'XENA' versionutils module of oslo.log included Xena release from version 4.5.0 ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: In Progress ** Description changed: - Glance fails to build with oslo.log 4.4.0 for Debian platform so we need - to bump the oslo.log version in requirements.txt + Glance RC for Xena fails to build with oslo.log 4.4.0 for Debian + platform so we need to bump the oslo.log version in requirements.txt Failures during discovery = --- import errors --- Failed to import test module: glance.tests.unit.api.middleware.test_cache_manage Traceback (most recent call last): - File "/usr/lib/python3.9/unittest/loader.py", line 436, in _find_test_path - module = self._get_module_from_name(name) - File "/usr/lib/python3.9/unittest/loader.py", line 377, in _get_module_from_name - __import__(name) - File "/<>/glance/tests/unit/api/middleware/test_cache_manage.py", line 13, in - from glance.api.middleware import cache_manage - File "/<>/glance/api/middleware/cache_manage.py", line 23, in - from glance.api.v2 import cached_images - File "/<>/glance/api/v2/cached_images.py", line 23, in - from glance.api import policy - File "/<>/glance/api/policy.py", line 30, in - from glance import policies - File "/<>/glance/policies/__init__.py", line 17, in - from glance.policies import metadef - File "/<>/glance/policies/metadef.py", line 39, in - deprecated_since=versionutils.deprecated.XENA + File "/usr/lib/python3.9/unittest/loader.py", line 436, in _find_test_path + module = self._get_module_from_name(name) + File "/usr/lib/python3.9/unittest/loader.py", line 377, in _get_module_from_name + __import__(name) + File "/<>/glance/tests/unit/api/middleware/test_cache_manage.py", line 13, in + from glance.api.middleware import cache_manage + File "/<>/glance/api/middleware/cache_manage.py", line 23, in + from glance.api.v2 import cached_images + File "/<>/glance/api/v2/cached_images.py", line 23, in + from glance.api import policy + File "/<>/glance/api/policy.py", line 30, in + from glance import policies + File "/<>/glance/policies/__init__.py", line 17, in + from glance.policies import metadef + File "/<>/glance/policies/metadef.py", line 39, in + deprecated_since=versionutils.deprecated.XENA AttributeError: type object 'deprecated' has no attribute 'XENA' - versionutils module of oslo.log included Xena release from version 4.5.0 ** Description changed: - Glance RC for Xena fails to build with oslo.log 4.4.0 for Debian + Glance RC1 for Xena fails to build with oslo.log 4.4.0 for Debian platform so we need to bump the oslo.log version in requirements.txt Failures during discovery = --- import errors --- Failed to import test module: glance.tests.unit.api.middleware.test_cache_manage Traceback (most recent call last): File "/usr/lib/python3.9/unittest/loader.py", line 436, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.9/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/<>/glance/tests/unit/api/middleware/test_cache_manage.py", line 13, in from gla
[Yahoo-eng-team] [Bug 1943135] Re: Metadef Resource types are not getting flushing out from DB
I think this is not a bug and by design from the beginning. If metadef_resource_types are not associated with any namespaces then they will remain in metadef_resource_types table forever. If any resource type is associated with metadef_namespaces then new entry will be added in 'metadef_namespace_resource_types' and while de- associating it will delete the resource type from that table but keeps it in metadef_resource_types table so that if anyone wants to use that in future then that can be asoociated to with same or different namespace. But if without deassociating the resource type from the namespace if you delete the namespace then that record will be removed from both the tables. If we want to delete the resource type from the metadef_resource_types on deassociation then I think that will be API change and requires a spec for further discussion. ** Changed in: glance Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1943135 Title: Metadef Resource types are not getting flushing out from DB Status in Glance: Opinion Bug description: The resource types are not getting deleted form database even after deleting from CLI $ glance md-resource-type-associate my-test-for-rs-deletion --name test-resource-type-in-db ++--+ | Property | Value| ++--+ | created_at | 2021-09-09T12:46:18Z | | name | test-resource-type-in-db | | updated_at | 2021-09-09T12:46:18Z | ++--+ $ glance md-resource-type-deassociate my-test-for-rs-deletion test-resource-type-in-db $ mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 16967 Server version: 5.7.35-0ubuntu0.18.04.1 (Ubuntu) Copyright (c) 2000, 2021, Oracle and/or its affiliates. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> use glance; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> select * from metadef_resource_types WHERE name="test-resource-type-in-db"; +--+--+---+-+-+ | id | name | protected | created_at | updated_at | +--+--+---+-+-+ | 4| test-resource-type-in-db | 0 | 2021-09-09 12:46:18 | 2021-09-09 12:46:18 | +--+--+---+-+-+ The resource type needs to be deleted from the db. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1943135/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1939977] [NEW] 500 error on deleting image from store if get_image_location policy is disabled
Public bug reported: Note: This issue only occurs if multiple stores are configured in glance. Deleting image from particular store, if get_image_location policy is disabled or it does not match the policy criteria then you will get 500 internal server error. Steps to reproduce: 1. Verify you have multiple stores configured 2. Create image in all stores using below command $ glance image-create-via-import --disk-format qcow2 --container-format bare --name policy_test --file --all-stores True 3. Disable get_image_location in policy.yaml file and restart glance-api service 4. Delete image from any of the store using below command $ glance stores-delete --store Expected output: Unable to delete image '' from store ''. (HTTP 403 Forbidden: You are not authorized to complete get_image_location action.) Actual output: Unable to delete image '' from store ''. (HTTP 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation.) ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1939977 Title: 500 error on deleting image from store if get_image_location policy is disabled Status in Glance: New Bug description: Note: This issue only occurs if multiple stores are configured in glance. Deleting image from particular store, if get_image_location policy is disabled or it does not match the policy criteria then you will get 500 internal server error. Steps to reproduce: 1. Verify you have multiple stores configured 2. Create image in all stores using below command $ glance image-create-via-import --disk-format qcow2 --container-format bare --name policy_test --file --all-stores True 3. Disable get_image_location in policy.yaml file and restart glance-api service 4. Delete image from any of the store using below command $ glance stores-delete --store Expected output: Unable to delete image '' from store ''. (HTTP 403 Forbidden: You are not authorized to complete get_image_location action.) Actual output: Unable to delete image '' from store ''. (HTTP 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation.) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1939977/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1939922] [NEW] Internal server error if shared member tries to stage data to image
Public bug reported:
If non active image is shared with another project and any member from
that project tries to stage data for the same then we get Internal
server error from glance API.
Steps to reproduce:
1. Create image with shared visibility using below command
$ glance image-create --name stage-check --visibility shared
2. Share image with another project using below command
$ glance image-stage
3. Now source the credentials of project with we have shared image in stage 2
4. Stage image data using below command
$ glance image-stage --file
Expected Ouput: 403 HttpForbidden: You are not permitted for this operation
Actual Output:
HTTP 502 Bad Gateway: Bad Gateway: The proxy server received an invalid:
response from an upstream server.: Apache/2.4.41 (Ubuntu) Server at 10.0.78.195
Port 80
Glance API logs:
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data [None req-0c2515a8-cf31-4f8e-b365-c9f5375c386d
rbac-testing rbac-member] Failed to stage image data due to internal error:
glance.common.exception.Forbidden: You are not permitted to modify 'status' on
this image.
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data Traceback (most recent call last):
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data File
"/opt/stack/glance/glance/api/v2/image_data.py", line 372, in stage
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data image.status = 'uploading'
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data File
"/opt/stack/glance/glance/api/authorization.py", line 247, in forbidden
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data raise exception.Forbidden(message % {'attr': attr,
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data glance.common.exception.Forbidden: You are not
permitted to modify 'status' on this image.
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data [None req-0c2515a8-cf31-4f8e-b365-c9f5375c386d
rbac-testing rbac-member] Unable to restore image
30e26758-0e2d-4347-b0c0-66964f76403b: You are not permitted to modify 'status'
on this image.: glance.common.exception.Forbidden: You are not permitted to
modify 'status' on this image.
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data Traceback (most recent call last):
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data File
"/opt/stack/glance/glance/api/v2/image_data.py", line 372, in stage
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data image.status = 'uploading'
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data File
"/opt/stack/glance/glance/api/authorization.py", line 247, in forbidden
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data raise exception.Forbidden(message % {'attr': attr,
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data glance.common.exception.Forbidden: You are not
permitted to modify 'status' on this image.
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data During handling of the above exception, another
exception occurred:
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data Traceback (most recent call last):
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data File
"/opt/stack/glance/glance/api/v2/image_data.py", line 66, in _restore
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data image.status = 'queued'
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data File
"/opt/stack/glance/glance/api/authorization.py", line 247, in forbidden
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data raise exception.Forbidden(message % {'attr': attr,
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data glance.common.exception.Forbidden: You are not
permitted to modify 'status' on this image.
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.api.v2.image_data
Aug 13 20:49:33 akekane-xena-dev devstack@g-api.service[1526]: ERROR
glance.common.wsgi [None
[Yahoo-eng-team] [Bug 1939716] [NEW] Glance compatibility with SQLAlchemy 2.x
Public bug reported: Oslo.db has started putting efforts to support SQLAlchemy 2.x [1]. Our oslo-tips job, 'glance-tox-functional-py36-oslo-tips' and 'glance-tox- functional-py38-oslo-tips' started to fail as we also need to make similar changes to support SQLAlchemy 2.x. This bug will track efforts for the same. [1] https://review.opendev.org/q/topic:%22sqlalchemy-20%22+(status:open%20OR%20status:merged) ** Affects: glance Importance: High Status: New ** Changed in: glance Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1939716 Title: Glance compatibility with SQLAlchemy 2.x Status in Glance: New Bug description: Oslo.db has started putting efforts to support SQLAlchemy 2.x [1]. Our oslo-tips job, 'glance-tox-functional-py36-oslo-tips' and 'glance-tox- functional-py38-oslo-tips' started to fail as we also need to make similar changes to support SQLAlchemy 2.x. This bug will track efforts for the same. [1] https://review.opendev.org/q/topic:%22sqlalchemy-20%22+(status:open%20OR%20status:merged) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1939716/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1308484] Re: glance member-create doesn't complain when tenant_id doesn't exist
AFAIK this by design, feel free to bring this as a topic in upcoming Yoga PTG. https://etherpad.opendev.org/p/yoga-ptg-glance-planning ** Changed in: glance Status: Confirmed => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1308484 Title: glance member-create doesn't complain when tenant_id doesn't exist Status in Glance: Opinion Bug description: # glance image-create --name temporary_test --id 0bfbc34b-0ec8-4802-8f61-f45f0613fb54 # glance member-create --can-share 0bfbc34b-0ec8-4802-8f61-f45f0613fb54 'I do not exist!' # echo $? 0 # glance image-delete 0bfbc34b-0ec8-4802-8f61-f45f0613fb54 I expected it to return something greater than 0 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1308484/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1939169] [NEW] glance md-tag-create-multiple overwrites existing tags
Public bug reported:
Our md-tag-create-multiple (/v2/metadefs/namespaces/{namespace_name}/tags) [1]
API overwrites existing tags for specified namespace rather than creating new
one in addition to the existing tags.
Where as if you try to create different tags using md-tag-create
(/v2/metadefs/namespaces/{namespace_name}/tags/{tag_name}) it is working as
expected, means adding new tag in addition to existing ones.
Steps to reproduce:
1. source using admin credentials
$ source devstack/openrc admin admin
2. Create new public namespace
$ glance md-namespace-create TagsBugNamespace --visibility public
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T17:43:03Z |
| namespace | TagsBugNamespace |
| owner | a14a058e2d1540c3a0dc7c397c55174e |
| protected | False|
| schema | /v2/schemas/metadefs/namespace |
| updated_at | 2021-08-06T17:43:03Z |
| visibility | public |
++--+
3. Create single tag using md-tag-create command
$ glance md-tag-create TagsBugNamespace --name tag1
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T17:57:37Z |
| name | tag1 |
| updated_at | 2021-08-06T17:57:37Z |
++--+
4. Create another tag
$ glance md-tag-create TagsBugNamespace --name tag2
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T17:57:37Z |
| name | tag2 |
| updated_at | 2021-08-06T17:57:37Z |
++--+
5. Verify that we have two tags in the list
$ glance md-tag-list TagsBugNamespace
+--+
| name |
+--+
| tag2 |
| tag1 |
+--+
6. Add more tags using md-tag-crate-multiple command
$ glance md-tag-create-multiple TagsBugNamespace --names
TestTag1141=TestTag2411 --delim =
+-+
| name|
+-+
| TestTag1141 |
| TestTag2411 |
+-+
7. Now run tags list command again
$ glance md-tag-list TagsBugNamespace
+-+
| name|
+-+
| TestTag2411 |
| TestTag1141 |
+-+
Expected result:
These new tags should have been added to existing tags.
Actual result:
Existing tags gets deleted and only newly added tags using
md-tag-crate-multiple command remains.
* This is further to show that adding new tag using md-tag-create command now
will add a new tag and does not overwrite existing ones.
$ glance md-tag-create TagsBugNamespace --name tag3
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T18:12:14Z |
| name | tag3 |
| updated_at | 2021-08-06T18:12:14Z |
++--+
* Verify that we have not overwritten existing tags now;
$ glance md-tag-list TagsBugNamespace
+-+
| name|
+-+
| tag3|
| TestTag2411 |
| TestTag1141 |
+-+
[1] https://docs.openstack.org/api-ref/image/v2/metadefs-
index.html?expanded=create-tag-definition-detail,create-tags-detail,get-
tag-definition-detail,delete-all-tag-definitions-detail#create-tags
** Affects: glance
Importance: High
Status: New
** Affects: glance/xena
Importance: High
Status: New
** Changed in: glance
Importance: Undecided => High
** Description changed:
Our md-tag-create-multiple (/v2/metadefs/namespaces/{namespace_name}/tags)
[1] API overwrites existing tags for specified namespace rather than creating
new one in addition to the existing tags.
Where as if you try to create different tags using md-tag-create
(/v2/metadefs/namespaces/{namespace_name}/tags/{tag_name}) it is working as
expected, means adding new tag in addition to existing ones.
Steps to reproduce:
1. source using admin credentials
$ source devstack/openrc admin admin
2. Create new public namespace
- $ glance md-namespace-create TagsBugNamespace --visibility public
+ $ glance md-namespace-create TagsBugNamespace --visibility public
++--+
| Property | Value|
++--+
| created_at | 2021-08-06T17:43:03Z |
| namespace | TagsBugNamespace |
| owner | a14a058e2d1540c3a0dc7c397c55174e |
| protected | False|
| schema | /v2/schemas/metadefs/namespace |
| updated_at | 2021-08-06T17:43:03Z |
| visibility | public |
++--+
3. Create single tag using md-tag-create command
$
[Yahoo-eng-team] [Bug 1885825] Re: No implicit user creation with GRANT syntax in MySQL 8.0 Ubuntu Focal
** Also affects: glance Importance: Undecided Status: New ** Also affects: glance/ussuri Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1885825 Title: No implicit user creation with GRANT syntax in MySQL 8.0 Ubuntu Focal Status in coverage2sql: Fix Released Status in Glance: New Status in Glance ussuri series: New Status in OpenStack Identity (keystone): Fix Released Status in OpenStack Compute (nova): Fix Released Status in tacker: Fix Released Status in zaqar: Fix Released Bug description: Ubuntu Focal (20.04) has mysql 8.0 and with mysql 8.0 there is no implicit user creation with GRANT syntax. In Ubuntu Bionic (18.04) mysql 5.7 version used to create the user implicitly when using using the GRANT. But starting with mysql 8.0, we need to create the user explicitly before using the GRANT command. Nova unit and functional tests job using tools/test-setup.sh script start failing when running on Ubuntu Focal https://zuul.opendev.org/t/openstack/build/8b0f4fcc21854655a638c413b6fe1a91 + sudo -H mysql -u root -pinsecure_slave -h localhost -e ' DELETE FROM mysql.user WHERE User='\'''\''; FLUSH PRIVILEGES; GRANT ALL PRIVILEGES ON *.* TO '\''openstack_citest'\''@'\''%'\'' identified by '\''openstack_citest'\'' WITH GRANT OPTION;' mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 1064 (42000) at line 4: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'identified by 'openstack_citest' WITH GRANT OPTION' at line 2 we need to modify the tools/test-setup.sh to create user first. Below used to work with mysql 5.7 GRANT ALL PRIVILEGES ON *.* TO '$DB_USER'@'%' identified by '$DB_PW' WITH GRANT OPTION;" With mysql 8.0 we need to create user first CREATE USER '$DB_USER'@'%' IDENTIFIED BY '$DB_PW'; GRANT ALL PRIVILEGES ON *.* TO '$DB_USER'@'%' WITH GRANT OPTION;" To manage notifications about this bug go to: https://bugs.launchpad.net/coverage2sql/+bug/1885825/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1922928] Re: Image tasks API excludes in-progress tasks
** Changed in: glance Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1922928 Title: Image tasks API excludes in-progress tasks Status in Glance: Fix Released Bug description: The glance /images/$uuid/tasks API is excluding in-progress tasks, leading to test failures like this one: Traceback (most recent call last): File "/opt/stack/tempest/tempest/api/image/v2/test_images.py", line 111, in test_image_glance_direct_import self.assertEqual(1, len(tasks['tasks'])) File "/opt/stack/tempest/.tox/tempest/lib/python3.8/site-packages/testtools/testcase.py", line 415, in assertEqual self.assertThat(observed, matcher, message) File "/opt/stack/tempest/.tox/tempest/lib/python3.8/site-packages/testtools/testcase.py", line 502, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 1 != 0 This is caused by the fact that we assert that the task is not expired by comparing the expires_at column to the current time. However, if the task is not completed yet, the expires_at will be NULL and never pass that test. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1922928/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1930932] Re: Interoperable Image Import in glance - doc issue
I think this is deployment related issue. Your deployment tool need to provide support to parse image-import.conf file at the time of service start. For example if you set development environment using devstack then it parse your image-import.conf file. Marking this issue as invalid, feel free to comment back. ** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1930932 Title: Interoperable Image Import in glance - doc issue Status in Glance: Invalid Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [X] This doc is inaccurate in this way: This document references that the configuration options should be added in the file "/etc/glance/glance-image-import.conf" which is wrong, because glance code is using "glance-api.conf" to read these configurations This feature got added on this review https://review.opendev.org/c/openstack/charm-glance/+/792065 and this documentation issue lead to a confusion and it was found that configurations should be added into the "/etc/glance/glance-api.conf" file File "glance-image-import.conf" is referenced 13 times on this document, it should be corrected to reference "glance-api.conf" If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2019-07-22 18:46:16 SHA: b3de9da3b9c0f32cd0c5f1eda6bf1789b7425dc9 Source: https://opendev.org/openstack/glance/src/doc/source/admin/interoperable-image-import.rst URL: https://docs.openstack.org/glance/train/admin/interoperable-image-import.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1930932/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1932337] Re: Cinder store migration will fail if first GET'er is not the owner
I think this issue is not specific to cinder-glance driver but with other drivers as well. ** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/xena Importance: Undecided Status: New ** Changed in: glance/wallaby Status: New => Confirmed ** Changed in: glance/xena Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1932337 Title: Cinder store migration will fail if first GET'er is not the owner Status in Glance: Confirmed Status in Glance wallaby series: Confirmed Status in Glance xena series: Confirmed Bug description: During an upgrade to Xena, cinder-backed image locations are migrated to include the store name in the URL field. This is lazily done on the first GET of the image. The problem is that the first user to GET an image after the migration may not be an admin or the owner of the image, as would be the case for a public or shared image. If that happens, the user gets a 404 for a valid image because the DB layer refuses the modify operation. This is logged: 2021-06-17 08:50:06,559 WARNING [glance.db.sqlalchemy.api] Attempted to modify image user did not own. The lazy migration code needs to tolerate this and allow someone else to perform the migration without breaking non-owner GET operations until the migration is complete. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1932337/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1865284] Re: The image cannot be deleted(no instance uses it)
Marking it as won't fix, please feel free to reopen. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1865284 Title: The image cannot be deleted(no instance uses it) Status in Glance: Won't Fix Bug description: i try to delete a image, however, i can't delete it even though no instances use it. i means i have checked with both `openstack server list --all-projects` and `openstack server list --all-projects --deleted` root@mgt01:~# openstack image delete a070fe08-b722-4726-90ae-ef5cb24ecaa0 --debug ... curl -g -i -X DELETE -H 'b'Content-Type': b'application/octet-stream'' -H 'b'X-Auth-Token': b'gABeWm3DVCPriqDt-ygrySLeAtpuc2-X069T5RWEA3bnpQEOKI3JEfNgaFIVDPPa1dhQZeUBeyW7h5QOn_uJGGSg6vAbfaEHgpwc8ybs33xtN_xe1mQ-37ij9p-9aZm-dy_SsiaRmvavohOyX10Xvj6RycEkMRuCGsZtcs0MUUQ6OaW6Rqw'' -H 'User-Agent: python-glanceclient' -H 'Accept-Encoding: gzip, deflate' -H 'Accept: */*' -H 'Connection: keep-alive' http://glance.openstack.svc.chongqing-spring.myinspurcloud.com:80/v2/images/a070fe08-b722-4726-90ae-ef5cb24ecaa0 http://glance.openstack.svc.chongqing-spring.myinspurcloud.com:80 "DELETE /v2/images/a070fe08-b722-4726-90ae-ef5cb24ecaa0 HTTP/1.1" 409 299 DELETE call to image for http://glance.openstack.svc.chongqing-spring.myinspurcloud.com:80/v2/images/a070fe08-b722-4726-90ae-ef5cb24ecaa0 used request id req-7521347e-5c94-4ce8-95ab-3f5cd7fb8747 Request returned failure status 409. Failed to delete image with name or ID 'a070fe08-b722-4726-90ae-ef5cb24ecaa0': 409 Conflict: Image a070fe08-b722-4726-90ae-ef5cb24ecaa0 could not be deleted because it is in use: The image cannot be deleted because it is in use through the backend store outside of Glance. (HTTP 409) Failed to delete 1 of 1 images. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cliff/app.py", line 400, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python3/dist-packages/osc_lib/command/command.py", line 41, in run return super(Command, self).run(parsed_args) File "/usr/lib/python3/dist-packages/cliff/command.py", line 184, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python3/dist-packages/openstackclient/image/v2/image.py", line 419, in take_action raise exceptions.CommandError(msg) osc_lib.exceptions.CommandError: Failed to delete 1 of 1 images. clean_up DeleteImage: Failed to delete 1 of 1 images. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 135, in run ret_val = super(OpenStackShell, self).run(argv) File "/usr/lib/python3/dist-packages/cliff/app.py", line 279, in run result = self.run_subcommand(remainder) File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 175, in run_subcommand ret_value = super(OpenStackShell, self).run_subcommand(argv) File "/usr/lib/python3/dist-packages/cliff/app.py", line 400, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python3/dist-packages/osc_lib/command/command.py", line 41, in run return super(Command, self).run(parsed_args) File "/usr/lib/python3/dist-packages/cliff/command.py", line 184, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python3/dist-packages/openstackclient/image/v2/image.py", line 419, in take_action raise exceptions.CommandError(msg) osc_lib.exceptions.CommandError: Failed to delete 1 of 1 images. END return value: 1 root@mgt01:~# glance --version 2.9.1 This happens on only one image, i have not dig into the code, but i thought may be a bug related to glance. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1865284/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1671609] Re: Deleted glance images results in lost image name in horizon for non-admins
Marking it as won't fix, please feel free to reopen. ** Changed in: glance Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1671609 Title: Deleted glance images results in lost image name in horizon for non- admins Status in Glance: Won't Fix Bug description: When a glance image is deleted the 'Image Name' column in the Dashboard for non-admin users displays as '-' instead of the image name. Admin users can still see the image name in this column so the information is being retained in the DB and displayed appropriately. This is a problem for operators and users because I often refresh/recycle glance image names (ie 'Ubuntu 16.04 - latest' and the side effect of this use case is not very desirable. glance 2:12.0.0-0ubuntu2~cloud0 glance-api 2:12.0.0-0ubuntu2~cloud0 glance-common2:12.0.0-0ubuntu2~cloud0 glance-registry 2:12.0.0-0ubuntu2~cloud0 python-glance2:12.0.0-0ubuntu2~cloud0 python-glance-store 0.13.0-3~cloud0 python-glanceclient 1:2.0.0-2ubuntu0.16.04.1~cloud0 Please see my attached screenshot for clarification. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1671609/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1868455] Re: unit tests with py3.8: glance_store.exceptions.UnknownScheme: Unknown scheme '' found in URI
haven't heard anything about this failure in recent times, marking it as
won't fix, please feel free to reopen.
** Changed in: glance
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1868455
Title:
unit tests with py3.8: glance_store.exceptions.UnknownScheme: Unknown
scheme '' found in URI
Status in Glance:
Won't Fix
Bug description:
Rebuilding Glance 19.0.0 in Debian Sid gives the below result:
FAIL:
glance.tests.unit.v2.test_tasks_resource.TestTasksController.test_create_with_live_time
glance.tests.unit.v2.test_tasks_resource.TestTasksController.test_create_with_live_time
--
testtools.testresult.real._StringException: pythonlogging:'': {{{
2020-03-22 13:34:41,556 INFO [glance.db.simple.api] Calling task_create:
args=(None, {'id': 'c80a1a6c-bd1f-41c5-90ee-81afedb1d58d', 'status': 'pending',
'type': 'import', 'input': {}, 'result': None, 'owner':
'6838eb7b-6ded-434a-882c-b344c77fe8df', 'message': None, 'expires_at':
datetime.datetime(2021, 3, 22, 13, 34, 41, 556098), 'created_at':
datetime.datetime(2020, 3, 22, 13, 34, 41, 556080), 'updated_at':
datetime.datetime(2020, 3, 22, 13, 34, 41, 556080), 'deleted_at': None,
'deleted': False}), kwargs={}
2020-03-22 13:34:41,556 INFO [glance.db.simple.api] Returning task_create:
{'id': 'c80a1a6c-bd1f-41c5-90ee-81afedb1d58d', 'type': 'import', 'status':
'pending', 'owner': '6838eb7b-6ded-434a-882c-b344c77fe8df', 'expires_at':
datetime.datetime(2021, 3, 22, 13, 34, 41, 556098), 'created_at':
datetime.datetime(2020, 3, 22, 13, 34, 41, 556080), 'updated_at':
datetime.datetime(2020, 3, 22, 13, 34, 41, 556080), 'deleted_at': None,
'deleted': False, 'input': {}, 'result': None, 'message': None}
2020-03-22 13:34:41,556 INFO [glance.db.simple.api] Calling task_create:
args=(None, {'id': 'a85abd86-55b3-4d5b-b0b4-5d0a6e6042fc', 'status': 'pending',
'type': 'import', 'input': {}, 'result': None, 'owner':
'2c014f32-55eb-467d-8fcb-4bd706012f81', 'message': None, 'expires_at':
datetime.datetime(2021, 3, 22, 13, 34, 41, 556103), 'created_at':
datetime.datetime(2020, 3, 22, 13, 34, 46, 556080), 'updated_at':
datetime.datetime(2020, 3, 22, 13, 34, 46, 556080), 'deleted_at': None,
'deleted': False}), kwargs={}
2020-03-22 13:34:41,556 INFO [glance.db.simple.api] Returning task_create:
{'id': 'a85abd86-55b3-4d5b-b0b4-5d0a6e6042fc', 'type': 'import', 'status':
'pending', 'owner': '2c014f32-55eb-467d-8fcb-4bd706012f81', 'expires_at':
datetime.datetime(2021, 3, 22, 13, 34, 41, 556103), 'created_at':
datetime.datetime(2020, 3, 22, 13, 34, 46, 556080), 'updated_at':
datetime.datetime(2020, 3, 22, 13, 34, 46, 556080), 'deleted_at': None,
'deleted': False, 'input': {}, 'result': None, 'message': None}
2020-03-22 13:34:41,557 INFO [glance.db.simple.api] Calling task_create:
args=(None, {'id': '971ec09a-8067-4bc8-a91f-ae3557f1c4c7', 'status': 'pending',
'type': 'import', 'input': {}, 'result': None, 'owner':
'5a3e60e8-cfa9-4a9e-a90a-62b42cea92b8', 'message': None, 'expires_at':
datetime.datetime(2021, 3, 22, 13, 34, 41, 556107), 'created_at':
datetime.datetime(2020, 3, 22, 13, 34, 51, 556080), 'updated_at':
datetime.datetime(2020, 3, 22, 13, 34, 51, 556080), 'deleted_at': None,
'deleted': False}), kwargs={}
2020-03-22 13:34:41,557 INFO [glance.db.simple.api] Returning task_create:
{'id': '971ec09a-8067-4bc8-a91f-ae3557f1c4c7', 'type': 'import', 'status':
'pending', 'owner': '5a3e60e8-cfa9-4a9e-a90a-62b42cea92b8', 'expires_at':
datetime.datetime(2021, 3, 22, 13, 34, 41, 556107), 'created_at':
datetime.datetime(2020, 3, 22, 13, 34, 51, 556080), 'updated_at':
datetime.datetime(2020, 3, 22, 13, 34, 51, 556080), 'deleted_at': None,
'deleted': False, 'input': {}, 'result': None, 'message': None}
2020-03-22 13:34:41,557 INFO [glance.db.simple.api] Calling task_create:
args=(None, {'id': '6bbe7cc2-eae7-4c0f-b50d-a7160b0c6a86', 'status': 'pending',
'type': 'import', 'input': {}, 'result': None, 'owner':
'c6c87f25-8a94-47ed-8c83-053c25f42df4', 'message': None, 'expires_at':
datetime.datetime(2021, 3, 22, 13, 34, 41, 556110), 'created_at':
datetime.datetime(2020, 3, 22, 13, 34, 56, 556080), 'updated_at':
datetime.datetime(2020, 3, 22, 13, 34, 56, 556080), 'deleted_at': None,
'deleted': False}), kwargs={}
2020-03-22 13:34:41,557 INFO [glance.db.simple.api] Returning task_create:
{'id': '6bbe7cc2-eae7-4c0f-b50d-a7160b0c6a86', 'type': 'import', 'status':
'pending', 'owner': 'c6c87f25-8a94-47ed-8c83-053c25f42df4', 'expires_at':
datetime.datetime(2021, 3, 22, 13, 34, 41, 556110), 'created_at':
datetime.datetime(2020, 3, 22, 13, 34, 56, 556080), 'updated_at':
datetime.datetime(2020, 3, 22, 13, 34, 56, 556080), 'deleted_at': None,
'deleted': False, 'input': {}, 'result': None, 'message': None}
2020-03-22 13:34:41,563
[Yahoo-eng-team] [Bug 1536130] Re: error message of "1 is not a supported API version. Example values are 1 or 2." is not precise
No more inputs on this bug, marking this as won't fix. Please feel free to reopen. ** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1536130 Title: error message of "1 is not a supported API version. Example values are 1 or 2." is not precise Status in Glance: Won't Fix Bug description: when i add a new api cli command in glance, i get the error message: "1" is not a supported API version. Example values are "1" or "2". the reason is i import a wrong module in glanceclient/v1/client.py, so the return error message is not correct. it can be recurrent by modifing "from glanceclient.v1.images import ImageManager" to "from glanceclient.v1.imagesxxx import ImageManager" in glanceclient/v1/client.py, then you execute "glance image-list", you will found it. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1536130/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1407459] Re: glance-registry searches for [pipeline:glance-registry-]
Marking as Won't Fix as registry is now removed from glance code base. ** Changed in: glance Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1407459 Title: glance-registry searches for [pipeline:glance-registry-] Status in Glance: Won't Fix Bug description: Depending on what's in the flavor directive of /etc/glance/glance- registry.conf, glance-registry searches for a different section of /etc/glance/glance-registry-paste.ini. For example, if I put flavor = keystone+caching, then glance-registry searches for a section [pipeline:glance-registry-keystone+caching] in /etc/glance/glance- registry-paste.ini. If this is a feature, then the default configuration file should be updated to handle all values of the flavor directive. If it's a bug (eg: regression) and that glance-registry is searching for the wrong section, then this should be corrected. In the mean while, I'm patching the default configuration file in my Debian package to add the below lines to glance-registry-paste.ini: [pipeline:glance-registry-keystone] pipeline = osprofiler unauthenticated-context registryapp [pipeline:glance-registry-caching] pipeline = osprofiler unauthenticated-context registryapp [pipeline:glance-registry-keystone+caching] pipeline = osprofiler unauthenticated-context registryapp [pipeline:glance-registry-cachemanagement] pipeline = osprofiler unauthenticated-context registryapp [pipeline:glance-registry-keystone+cachemanagement] pipeline = osprofiler unauthenticated-context registryapp Without this, glance-registry may refuse to start by default, which is really annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1407459/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1470164] Re: Unexpected error in glance registry when param 'allow_anonymous_access' is True
Marking as Won't Fix as registry is now removed from glance code base. ** Changed in: glance Status: In Progress => Won't Fix ** Changed in: glance/juno Status: New => Won't Fix ** Changed in: glance/kilo Status: New => Won't Fix ** Changed in: glance/liberty Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1470164 Title: Unexpected error in glance registry when param 'allow_anonymous_access' is True Status in Glance: Won't Fix Status in Glance juno series: Won't Fix Status in Glance kilo series: Won't Fix Status in Glance liberty series: Won't Fix Bug description: Steps to reproduce: 1. Stop "glance-api" service. 2. In "glance-api.conf" set "allow_anonymous_access = True" 3. Start "glance-api" service. 4. Trying to get image-list with use v1 and without keystone "x-auth-token" GET /v1/images HTTP/1.1 Host: 172.18.85.25:2081 User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: ru-RU,ru;q=0.8,en-US;q=0.5,en;q=0.3 Accept-Encoding: gzip, deflate Connection: keep-alive Actual result: HTTP/1.1 500 Internal Server Error Content-Type: text/plain Content-Length: 0 Date: Tue, 30 Jun 2015 14:54:42 GMT Connection: close P.S: Affected all versions of glance (v1,v2,v3) if you use 'registry' backend and "use_user_token = true" in glance-api.conf (default value). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1470164/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1438952] Re: Glance Cache getting ignored
Marking as Won't Fix as registry is now removed from glance code base. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1438952 Title: Glance Cache getting ignored Status in Glance: Won't Fix Status in OpenStack Compute (nova): Confirmed Bug description: Step to reproduce: 1. Install glance registry on controller 2. Install galnce api con compute node & enable cachemanagement (flavor=keystone+cachemanagement) 3. Add an image to the registry and expose it as http:///imagepath (so that in db the location is http based) 4. From compute node, invoke glance-cache-manage queue-image ID_OF_IMAGE 5. Run glance-cache-prefetcher 6. Run nova boot --image --flavor 1 --availability-zone nova: MACHINENAME You'll see that image is downloaded again from network instead of using the local one in /var/lub/glance/image-cache To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1438952/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1483535] Re: Cannot create image: NotAuthenticated
Marking as Won't Fix as registry and v1 is now removed from glance code base. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1483535 Title: Cannot create image: NotAuthenticated Status in Glance: Won't Fix Bug description: Devstack Juno (2014.2.4) on Ubuntu 14.04. Local.conf: [[local|localrc]] LOGFILE=/opt/stack/logs/stack.sh.log LOGDIR=/opt/stack/logs HOST_IP=192.168.10.214 FLAT_INTERFACE=eth0 FIXED_RANGE=172.22.10.0/24 FIXED_NETWORK_SIZE=255 FLOATING_RANGE=192.168.10.0/24 MULTI_HOST=1 ADMIN_PASSWORD=PASSW MYSQL_PASSWORD=PASSW RABBIT_PASSWORD=PASSW SERVICE_PASSWORD=PASSW SERVICE_TOKEN=PASSW KEYSTONE_BRANCH=stable/juno NOVA_BRANCH=stable/juno NEUTRON_BRANCH=stable/juno SWIFT_BRANCH=stable/juno GLANCE_BRANCH=stable/juno CINDER_BRANCH=stable/juno HEAT_BRANCH=stable/juno TROVE_BRANCH=stable/juno HORIZON_BRANCH=stable/juno Exported vars: export OS_USERNAME=admin export OS_PASSWORD=PASSW # password set on first node: export OS_TENANT_NAME=admin export OS_AUTH_URL=http://192.168.10.214:35357/v2.0 Glance uses local storage (directory): /opt/stack/data/glance/images Conf: - glance-api: [DEFAULT] workers = 2 filesystem_store_datadir = /opt/stack/data/glance/images/ rabbit_hosts = 192.168.10.214 rpc_backend = glance.openstack.common.rpc.impl_kombu notification_driver = messaging use_syslog = False sql_connection = mysql://root:rooter@127.0.0.1/glance?charset=utf8 debug = True # Show more verbose log output (sets INFO log level output) #verbose = False # Show debugging output in logs (sets DEBUG log level output) #debug = False # Which backend scheme should Glance use by default is not specified # in a request to add a new image to Glance? Known schemes are determined # by the known_stores option below. # Default: 'file' default_store = file # Maximum image size (in bytes) that may be uploaded through the # Glance API server. Defaults to 1 TB. # WARNING: this value should only be increased after careful consideration # and must be set to a value under 8 EB (9223372036854775808). #image_size_cap = 1099511627776 # Address to bind the API server bind_host = 0.0.0.0 # Port the bind the API server to bind_port = 9292 # Log to this file. Make sure you do not set the same log file for both the API # and registry servers! # # If `log_file` is omitted and `use_syslog` is false, then log messages are # sent to stdout as a fallback. #log_file = /var/log/glance/api.log # Backlog requests when creating socket backlog = 4096 # TCP_KEEPIDLE value in seconds when creating socket. # Not supported on OS X. #tcp_keepidle = 600 # API to use for accessing data. Default value points to sqlalchemy # package, it is also possible to use: glance.db.registry.api # data_api = glance.db.sqlalchemy.api # The number of child process workers that will be # created to service API requests. The default will be # equal to the number of CPUs available. (integer value) #workers = 4 # Maximum line size of message headers to be accepted. # max_header_line may need to be increased when using large tokens # (typically those generated by the Keystone v3 API with big service # catalogs) # max_header_line = 16384 # Role used to identify an authenticated user as administrator #admin_role = admin # Allow unauthenticated users to access the API with read-only # privileges. This only applies when using ContextMiddleware. #allow_anonymous_access = False # Allow access to version 1 of glance api #enable_v1_api = True # Allow access to version 2 of glance api #enable_v2_api = True # Return the URL that references where the data is stored on # the backend storage system. For example, if using the # file system store a URL of 'file:///path/to/image' will # be returned to the user in the 'direct_url' meta-data field. # The default value is false. #show_image_direct_url = False # Send headers containing user and tenant information when making requests to # the v1 glance registry. This allows the registry to function as if a user is # authenticated without the need to authenticate a user itself using the # auth_token middleware. # The default value is false. #send_identity_headers = False # Supported values for the 'container_format' image attribute #container_formats=ami,ari,aki,bare,ovf,ova # Supported values for the 'disk_format' image attribute #disk_formats=ami,ari,aki,vhd,vmdk,raw,qcow2,vdi,iso # Directory to use for lock files. Default to a temp directory # (string value). This setting needs to be the same for both # glance-scrubber and glance-api. #lock_path= # Property Protections config file # This file contains the rules for property
[Yahoo-eng-team] [Bug 1502991] Re: Cache prefetcher can't work with trusted-auth registry
Marking as Won't Fix as registry is now removed from glance code base.
** Changed in: glance
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1502991
Title:
Cache prefetcher can't work with trusted-auth registry
Status in Glance:
Won't Fix
Bug description:
As described below, Cache prefetcher fails to work when the registry is
deployed in trusted-auth mode.
Cache prefetcher should send necessary identity headers to registry when
pulling image metadata.
$ curl -X PUT
http://127.0.0.1:9292/v1/queued_images/7c383ea4-f108-43c4-9d1e-02c8a6a1385c -H
'X-Auth-Token: ABCD' -i
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 4
X-Openstack-Request-Id: req-f3012c1b-a4ff-4ec2-a88b-3048bee0938d
Date: Mon, 05 Oct 2015 17:54:57 GMT
$ curl -X GET http://127.0.0.1:9292/v1/queued_images -H 'X-Auth-Token: ABCD'
-i
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 59
X-Openstack-Request-Id: req-a5cb12a1-6126-425c-9cff-d540c3a01f4e
Date: Mon, 05 Oct 2015 17:55:16 GMT
{"queued_images": ["7c383ea4-f108-43c4-9d1e-02c8a6a1385c"]}
$ /opt/stack/glance/glance/cmd/cache_prefetcher.py
2015-10-05 17:55:31.226 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.sheepdog.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.226 9296 DEBUG glance_store.backend [-] Attempting to
import store no_conf _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.227 9296 DEBUG glance_store.backend [-] Attempting to
import store http _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.227 9296 DEBUG glance_store.backend [-] Attempting to
import store file _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.227 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.http.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.227 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.rbd.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.227 9296 DEBUG glance_store.backend [-] Attempting to
import store rbd _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.228 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.gridfs.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.228 9296 DEBUG glance_store.backend [-] Attempting to
import store s3 _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.228 9296 DEBUG glance_store.backend [-] Attempting to
import store vmware _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.228 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.cinder.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.228 9296 DEBUG glance_store.backend [-] Attempting to
import store gridfs _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.228 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.filesystem.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.229 9296 DEBUG glance_store.backend [-] Attempting to
import store cinder _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.229 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.swift.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.229 9296 DEBUG glance_store.backend [-] Attempting to
import store swift _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.229 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.vmware_datastore.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.229 9296 DEBUG glance_store.backend [-] Attempting to
import store sheepdog _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.230 9296 DEBUG glance_store.backend [-] Attempting to
import store glance.store.s3.Store _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:149
2015-10-05 17:55:31.230 9296 DEBUG glance_store.backend [-] Registering
options for group glance_store register_opts
[Yahoo-eng-team] [Bug 1832818] Re: Glance registry service failed due to eventlet overflow error
Marking as Won't Fix as registry is now removed from glance code base. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1832818 Title: Glance registry service failed due to eventlet overflow error Status in Glance: Won't Fix Bug description: Glance registry service failed with logs: 2019-04-13 09:20:59.271 7184 CRITICAL glance [-] OverflowError: Python int too large to convert to C int 2019-04-13 09:20:59.271 7184 ERROR glance Traceback (most recent call last): 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/bin/glance-registry", line 10, in 2019-04-13 09:20:59.271 7184 ERROR glance sys.exit(main()) 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/glance/cmd/registry.py", line 77, in main 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/glance/common/wsgi.py", line 312, in start 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/glance/common/wsgi.py", line 327, in start_wsgi 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/glance/common/wsgi.py", line 447, in run_child 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/glance/common/wsgi.py", line 471, in run_server 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/eventlet/wsgi.py", line 842, in server 2019-04-13 09:20:59.271 7184 ERROR glance pool.waitall() 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/eventlet/greenpool.py", line 120, in waitall 2019-04-13 09:20:59.271 7184 ERROR glance self.no_coros_running.wait() 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/eventlet/event.py", line 121, in wait 2019-04-13 09:20:59.271 7184 ERROR glance return hubs.get_hub().switch() 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in switch 2019-04-13 09:20:59.271 7184 ERROR glance return self.greenlet.switch() 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 346, in run 2019-04-13 09:20:59.271 7184 ERROR glance self.wait(sleep_time) 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/eventlet/hubs/poll.py", line 85, in wait 2019-04-13 09:20:59.271 7184 ERROR glance presult = self.do_poll(seconds) 2019-04-13 09:20:59.271 7184 ERROR glance File "/usr/lib/python2.7/site-packages/eventlet/hubs/poll.py", line 74, in do_poll 2019-04-13 09:20:59.271 7184 ERROR glance return self.poll.poll(int(seconds * 1000.0)) 2019-04-13 09:20:59.271 7184 ERROR glance OverflowError: Python int too large to convert to C int 2019-04-13 09:20:59.271 7184 ERROR glance glance version: mitaka eventlet version: 0.17.4 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1832818/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1856333] Re: Install and configure (Ubuntu) in glance
Marking as Won't Fix as registry is now removed from glance code base. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1856333 Title: Install and configure (Ubuntu) in glance Status in Glance: Won't Fix Bug description: service glance-registry restart error Failed to restart glance-registry.service: Unit glance- registry.service not found. This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2018-08-22 10:01:34 SHA: fb173f680c7d4f39316c0e090a0c20854a5e6020 Source: https://git.openstack.org/cgit/openstack/glance/tree/doc/source/install/install-ubuntu.rst URL: https://docs.openstack.org/glance/stein/install/install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1856333/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1432701] Re: Glance API fail to list 'deleted' images
Marking as Won't Fix as registry and v1 is now removed from glance code
base.
** Changed in: glance
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1432701
Title:
Glance API fail to list 'deleted' images
Status in Glance:
Won't Fix
Bug description:
Even with user admin context, and following the API-ref for
image/detail api and attempt to query deleted images will get failure
for both ways.
1)
[root@node191 glance]# curl -i -X GET -H 'User-Agent: python-glanceclient' -H
'Content-Type: application/octet-stream' -H 'Accept-Encoding: gzip, deflate' -H
'Accept: */*' -H 'X-Auth-Token: 2e65fd85f8eb41e2a33ed5b401754798'
http://10.104.0.191:9292/v1/images/detail?status=deleted
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: 14
X-Openstack-Request-Id: req-req-2599f890-6986-435b-b23e-abafcd2b85ae
Date: Mon, 16 Mar 2015 15:21:46 GMT
{"images": []}
2) And
[root@node191 glance]# curl -i -X GET -H 'User-Agent: python-glanceclient' -H
'Content-Type: application/octet-stream' -H 'Accept-Encoding: gzip, deflate' -H
'Accept: */*' -H 'X-Auth-Token: 2e65fd85f8eb41e2a33ed5b401754798'
http://10.104.0.191:9292/v1/images/detail?deleted=True
Will also list all the Active images without any deleted images.
It does appears that glance will never allow the filters with 'deleted' key
passing from the check below.
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L387
And in registry code will never get filter with 'deleted', so 'deleted' will
always being false.
https://github.com/openstack/glance/blob/master/glance/registry/api/v1/images.py#L249
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1432701/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1424038] Re: Adding image member throws 500 when the member name is longer than 255 characters
Marking as Won't Fix as registry is now removed from glance code base. ** Changed in: glance Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1424038 Title: Adding image member throws 500 when the member name is longer than 255 characters Status in Glance: Won't Fix Status in OpenStack Security Advisory: Won't Fix Bug description: When adding a member to an image, if the member name is longer than 255 characters, Glance registry fails with a 500. Reproduction in devstack: glance member-create 749f53d4-896b-436c-b742-6e01d3d700e8 663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663asdsadasdsadsadasdsadasd1 HTTPInternalServerError (HTTP 500) Error in registry logs: DBError: (DataError) (1406, "Data too long for column 'member' at row 1") 'INSERT INTO image_members (created_at, updated_at, deleted_at, deleted, image_id, member, can_share, status) VALUES (%s, %s, %s, %s, %s, %s, %s, %s)' (datetime.datetime(2015, 2, 20, 19, 8, 15, 862789), datetime.datetime(2015, 2, 20, 19, 8, 15, 862800), None, 0, '749f53d4-896b-436c-b742-6e01d3d700e8', '663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663asdsadasdsadsadasdsadasd1', 0, 'pending') 2015-02-20 19:08:16.380 18844 INFO glance.wsgi.server [9719e12b-9926-47f4-a8a6-93430a792bec ca44bfc7c1e4421287bb6517be22e34d 4ccaf93d792a4a2880a60d32f570 - - -] 127.0.0.1 - - [20/Feb/2015 19:08:16] "PUT /images/749f53d4-896b- 436c-b742-6e01d3d700e8/members/663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663051afadfasdfadsf663asdsadasdsadsadasdsadasd1 HTTP/1.1" 500 139 0.538550 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1424038/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1157347] Re: Unclear error message if database has not been initialized
Marking as Won't Fix as registry is now removed from glance code base. ** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1157347 Title: Unclear error message if database has not been initialized Status in Glance: Won't Fix Status in glance package in openSUSE: New Bug description: Error condition: A "glance" database has been created, and the correct credentials are in /etc/glance/glance-*.conf files, but "glance_mange version_control 0" and "glance_manage db_sync" have not yet been run. When a user does a "glance index", then the glance-api.log will contain this trace, suggesting an error in glance-registry 2013-03-19 14:09:14 ERROR glance.registry.client [f8bb7547-2c91-4ae7-9d02-ded5fb07ebe0 8a44600ac8c6402fb781584022ceeb91 8283efb2e53d46e1a6bdbb2bdef9cb9a] Registry request GET /images/detail Exception 2013-03-19 14:09:14 29229 TRACE glance.registry.client Traceback (most recent call last): 2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/registry/client.py", line 89, in do_request 2013-03-19 14:09:14 29229 TRACE glance.registry.client action, **kwargs) 2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 63, in wrapped 2013-03-19 14:09:14 29229 TRACE glance.registry.client return func(self, *args, **kwargs) 2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 444, in do_request 2013-03-19 14:09:14 29229 TRACE glance.registry.client headers=headers) 2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 80, in wrapped 2013-03-19 14:09:14 29229 TRACE glance.registry.client return func(self, method, url, body, headers) 2013-03-19 14:09:14 29229 TRACE glance.registry.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 581, in _do_request 2013-03-19 14:09:14 29229 TRACE glance.registry.client raise exception.ServerError() 2013-03-19 14:09:14 29229 TRACE glance.registry.client ServerError: The request returned 500 Internal Server Error. However, /var/log/glance/registry.log will not contain any information about the nature of the error. It would help admins if the glance-registry did a check for this and outputted a meaningful error message to its log. This was tested against folsom on Ubuntu 12.04 (cloud archive). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1157347/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1494366] Re: AttributeError: 'ImmutableImageProxy' object has no attribute 'deactivate'
** Changed in: glance
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1494366
Title:
AttributeError: 'ImmutableImageProxy' object has no attribute
'deactivate'
Status in Glance:
Invalid
Bug description:
When you use the following way to get token,
"""
curl -i \
-H "Content-Type: application/json" \
-d '
{ "auth": {
"identity": {
"methods": ["password"],
"password": {
"user": {
"name": "admin",
"domain": { "id": "default" },
"password": "password"
}
}
}
}
}' \
http://localhost:5000/v3/auth/tokens ; echo
"""
And use the token to deactivate images, the glance will raise the
following exception.
2015-09-10 14:06:53.513 DEBUG eventlet.wsgi.server [-] (12570) accepted
('10.0.2.15', 55773) from (pid=12570) server
/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py:826
2015-09-10 14:06:53.516 DEBUG glance.api.middleware.version_negotiation [-]
Determining version of request: POST
/v2/images/48465a7e-5c84-42ce-b05e-d9c4c41fa5e7/actions/deactivate Accept: */*
from (pid=12570) process_request
/opt/stack/glance/glance/api/middleware/version_negotiation.py:47
2015-09-10 14:06:53.517 DEBUG glance.api.middleware.version_negotiation [-]
Using url versioning from (pid=12570) process_request
/opt/stack/glance/glance/api/middleware/version_negotiation.py:60
2015-09-10 14:06:53.517 DEBUG glance.api.middleware.version_negotiation [-]
Matched version: v2 from (pid=12570) process_request
/opt/stack/glance/glance/api/middleware/version_negotiation.py:72
2015-09-10 14:06:53.517 DEBUG glance.api.middleware.version_negotiation [-]
new path /v2/images/48465a7e-5c84-42ce-b05e-d9c4c41fa5e7/actions/deactivate
from (pid=12570) process_request
/opt/stack/glance/glance/api/middleware/version_negotiation.py:73
2015-09-10 14:06:53.544 ERROR glance.common.wsgi
[req-4e45a2f8-8af5-4148-b57e-99ea1292839b f96b81dbf2fe4e5eb0a90e984a26a732
None] Caught error: 'ImmutableImageProxy' object has no attribute 'deactivate'
2015-09-10 14:06:53.544 TRACE glance.common.wsgi Traceback (most recent call
last):
2015-09-10 14:06:53.544 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 879, in __call__
2015-09-10 14:06:53.544 TRACE glance.common.wsgi request, **action_args)
2015-09-10 14:06:53.544 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 907, in dispatch
2015-09-10 14:06:53.544 TRACE glance.common.wsgi return method(*args,
**kwargs)
2015-09-10 14:06:53.544 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/utils.py", line 504, in wrapped
2015-09-10 14:06:53.544 TRACE glance.common.wsgi return func(self, req,
*args, **kwargs)
2015-09-10 14:06:53.544 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/api/v2/image_actions.py", line 49, in deactivate
2015-09-10 14:06:53.544 TRACE glance.common.wsgi image.deactivate()
2015-09-10 14:06:53.544 TRACE glance.common.wsgi AttributeError:
'ImmutableImageProxy' object has no attribute 'deactivate'
2015-09-10 14:06:53.544 TRACE glance.common.wsgi
2015-09-10 14:06:53.546 INFO eventlet.wsgi.server
[req-4e45a2f8-8af5-4148-b57e-99ea1292839b f96b81dbf2fe4e5eb0a90e984a26a732
None] 10.0.2.15 - - [10/Sep/2015 14:06:53] "POST
/v2/images/48465a7e-5c84-42ce-b05e-d9c4c41fa5e7/actions/deactivate HTTP/1.1"
500 430 0.030960
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1494366/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1830186] Re: Install and configure (Ubuntu) in glance
Marking as Won't Fix as registry is now removed from glance code base. ** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1830186 Title: Install and configure (Ubuntu) in glance Status in Glance: Won't Fix Bug description: Hi, I am on Ubuntu 18.04, working on Openstack Stein Version I got this error while trying to restart glance-registry service (service glance-registry restart). Failed to restart glance-registry.service: Unit glance- registry.service not found. But glance-api service restarts without trouble. What is the issue here ? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1830186/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1446547] Re: glance services failed during the deployment on orange box
Marking it as won't fix, please feel free to reopen. ** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1446547 Title: glance services failed during the deployment on orange box Status in Glance: Won't Fix Bug description: While doing autopilot deployment on orange box glance api service failed which causes the not to upload the image into openstack. Restart of the glance api and registry service make it through. But need to root cause of the service failure and fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1446547/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1883942] Re: Install and configure (Ubuntu) in glance
Marking it as won't fix, feel free to reopen. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1883942 Title: Install and configure (Ubuntu) in glance Status in Glance: Won't Fix Bug description: Environment: Ubuntu 18.04 + Ussuri During the glance installation, the following error displayied ... Unpacking python3-cinderclient (1:7.0.0-0ubuntu1~cloud0) ... dpkg: error processing archive /tmp/apt-dpkg-install-o9aLUy/17-python3-cinderclient_1%3a7.0.0-0ubuntu1~cloud0_all.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/cinder.bash_completion', which is also in package python-cinderclient 1:3.5.0-0ubuntu1 ... after all, Preparing to unpack .../44-glance_2%3a20.0.0-0ubuntu0.20.04.1~cloud0_all.deb ... Unpacking glance (2:20.0.0-0ubuntu0.20.04.1~cloud0) ... Errors were encountered while processing: /tmp/apt-dpkg-install-o9aLUy/17-python3-cinderclient_1%3a7.0.0-0ubuntu1~cloud0_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Then, now I can't find /etc/glance/glance-api.conf to edit. Any suggestion? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1883942/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1887588] Re: Should add user's domian when using cinder as store backend
Marking it won't fix. Feel free to reopen. ** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1887588 Title: Should add user's domian when using cinder as store backend Status in Glance: Won't Fix Bug description: When using cinder as store backend, there are some configurations of user which can call cinder's API. cinder_store_auth_address cinder_store_user_name cinder_store_password cinder_store_project_name cinder_os_region_name cinder_catalog_info = volumev3:cinderv3:internalURL In the multi-domain, user maybe not belongs to 'Default' domain, got auth error. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1887588/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1890193] Re: nova-ceph-multistore fails with rbd.OSError: [errno 116] error removing image
Not heard anything in recent times about this issue, marking it won't fix at the moment. Please feel free to reopen. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1890193 Title: nova-ceph-multistore fails with rbd.OSError: [errno 116] error removing image Status in Glance: Won't Fix Bug description: tempest.api.image.v2.test_images.ImportImagesTest appears to be failing during tearDownClass: ft1.1: tearDownClass (tempest.api.image.v2.test_images.ImportImagesTest)testtools.testresult.real._StringException: Traceback (most recent call last): File "/opt/stack/tempest/tempest/test.py", line 242, in tearDownClass six.reraise(etype, value, trace) File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/opt/stack/tempest/tempest/test.py", line 214, in tearDownClass teardown() File "/opt/stack/tempest/tempest/test.py", line 585, in resource_cleanup raise testtools.MultipleExceptions(*cleanup_errors) testtools.runtest.MultipleExceptions: ((, Got server fault Details: The server has either erred or is incapable of performing the requested operation. , ), (, Request timed out Details: (ImportImagesTest:tearDownClass) Failed to delete image 6640a1ec-9ae4-4eae-874c-ccacb9600a9d within the required time (300 s)., )) https://22f684f005ef66b4c705-76c9445dc5d377f059713bef625876b4.ssl.cf1.rackcdn.com/744506/2/check/nova-ceph-multistore/46a4a0f/testr_results.html With the following trace logged in g-api: Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi [None req-d47ff0f9-ea09-49c6-9dc1-f9d381aa8fe3 tempest-ImportImagesTest-1392868169 tempest-ImportImagesTest-1392868169] Caught error: [errno 116] error removing image: rbd.OSError: [errno 116] error removing image Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi Traceback (most recent call last): Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1348, in __call__ Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi request, **action_args) Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1391, in dispatch Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi return method(*args, **kwargs) Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/utils.py", line 416, in wrapped Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi return func(self, req, *args, **kwargs) Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/api/v2/images.py", line 524, in delete Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi image.delete() Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/domain/proxy.py", line 194, in delete Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi self.base.delete() Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/domain/proxy.py", line 194, in delete Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi self.base.delete() Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/api/policy.py", line 177, in delete Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi return self.image.delete() Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/domain/proxy.py", line 194, in delete Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi self.base.delete() Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/location.py", line 442, in delete Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348 glance-api[48099]: ERROR glance.common.wsgi location) Aug 03 19:26:50.138467 ubuntu-bionic-ovh-gra1-0019075348
[Yahoo-eng-team] [Bug 1914665] Re: Cinder Multistore job hits Cinder Quota error
** Changed in: glance Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1914665 Title: Cinder Multistore job hits Cinder Quota error Status in Glance: Won't Fix Bug description: Noticed during a cinder multistore test run, we hit a quota not found error. It looks like we don't handle this well, which causes nova to see a 503: Proxy Error. I dunno if there's anything better can do than raise a 5xx, but we should probably explain in the error what happened when we know, as we clearly do here. From this: https://cbff25b854b00bc0ff99-8ce5690b0835baabd00baac02d43f418.ssl.cf5.rackcdn.com/770629/5/check /glance-multistore-cinder- import/7c71502/controller/logs/screen-g-api.txt this log text (see the end): Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi Traceback (most recent call last): Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1347, in __call__ Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi action_result = self.dispatch(self.controller, action, Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1391, in dispatch Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi return method(*args, **kwargs) Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/utils.py", line 416, in wrapped Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi return func(self, req, *args, **kwargs) Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/api/v2/image_data.py", line 299, in upload Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi self._restore(image_repo, image) Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi self.force_reraise() Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/usr/local/lib/python3.8/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi six.reraise(self.type_, self.value, self.tb) Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/usr/local/lib/python3.8/dist-packages/six.py", line 703, in reraise Feb 04 21:07:13.368998 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi raise value Feb 04 21:07:13.370209 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/api/v2/image_data.py", line 164, in upload Feb 04 21:07:13.370209 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi image.set_data(data, size, backend=backend) Feb 04 21:07:13.370209 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/domain/proxy.py", line 208, in set_data Feb 04 21:07:13.370209 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi self.base.set_data(data, size, backend=backend, set_active=set_active) Feb 04 21:07:13.370209 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/notifier.py", line 501, in set_data Feb 04 21:07:13.370209 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi _send_notification(notify_error, 'image.upload', msg) Feb 04 21:07:13.370209 ubuntu-focal-limestone-regionone-0022873642 devstack@g-api.service[93292]: ERROR glance.common.wsgi File
[Yahoo-eng-team] [Bug 1898489] Re: conrollres upgrade didnt failed even though galnce upgrade has faild
** Changed in: glance
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1898489
Title:
conrollres upgrade didnt failed even though galnce upgrade has faild
Status in Glance:
Won't Fix
Bug description:
During an upgrade process from Queens to Rocky we got an issue related to
glance
During the controllers upgrade step the creation of the additonal columns to
glance image table in the DB got failed with the following error
"+++ glance-manage db_sync",
"/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py:1352:
OsloDBDeprecationWarning: EngineFacade is deprecated; please use
oslo_db.sqlalchemy.enginefacade",
" expire_on_commit=expire_on_commit, _conf=conf)",
"INFO [alembic.runtime.migration] Context impl MySQLImpl.",
"INFO [alembic.runtime.migration] Will assume non-transactional
DDL.",
"INFO [alembic.runtime.migration] Running upgrade queens_expand01 ->
rocky_expand01, add os_hidden column to images table",
"CRITI [glance] Unhandled error",
"Traceback (most recent call last):",
" File \"/usr/bin/glance-manage\", line 10, in ",
"sys.exit(main())",
" File \"/usr/lib/python2.7/site-packages/glance/cmd/manage.py\",
line 563, in main",
"return CONF.command.action_fn()",
" File \"/usr/lib/python2.7/site-packages/glance/cmd/manage.py\",
line 395, in sync",
"self.command_object.sync(CONF.command.version)",
" File \"/usr/lib/python2.7/site-packages/glance/cmd/manage.py\",
line 165, in sync",
"self.expand(online_migration=False)",
" File \"/usr/lib/python2.7/site-packages/glance/cmd/manage.py\",
line 222, in expand",
"self._sync(version=expand_head)",
" File \"/usr/lib/python2.7/site-packages/glance/cmd/manage.py\",
line 180, in _sync",
"alembic_command.upgrade(a_config, version)",
" File \"/usr/lib/python2.7/site-packages/alembic/command.py\", line
254, in upgrade",
"script.run_env()",
" File \"/usr/lib/python2.7/site-packages/alembic/script/base.py\",
line 425, in run_env",
"util.load_python_file(self.dir, 'env.py')",
" File \"/usr/lib/python2.7/site-packages/alembic/util/pyfiles.py\",
line 81, in load_python_file",
"module = load_module_py(module_id, path)",
" File \"/usr/lib/python2.7/site-packages/alembic/util/compat.py\",
line 141, in load_module_py",
"mod = imp.load_source(module_id, path, fp)",
" File
\"/usr/lib/python2.7/site-packages/glance/db/sqlalchemy/alembic_migrations/env.py\",
line 88, in ",
"run_migrations_online()",
" File
\"/usr/lib/python2.7/site-packages/glance/db/sqlalchemy/alembic_migrations/env.py\",
line 83, in run_migrations_online",
"context.run_migrations()",
" File \"\", line 8, in run_migrations",
" File
\"/usr/lib/python2.7/site-packages/alembic/runtime/environment.py\", line 836,
in run_migrations",
"self.get_context().run_migrations(**kw)",
" File
\"/usr/lib/python2.7/site-packages/alembic/runtime/migration.py\", line 330, in
run_migrations",
"step.migration_fn(**kw)",
" File
\"/usr/lib/python2.7/site-packages/glance/db/sqlalchemy/alembic_migrations/versions/rocky_expand01_add_os_hidden.py\",
line 31, in upgrade",
"op.add_column('images', h_col)",
" File \"\", line 8, in add_column",
" File \"\", line 3, in add_column",
" File
\"/usr/lib/python2.7/site-packages/alembic/operations/ops.py\", line 1565, in
add_column",
"return operations.invoke(op)",
" File
\"/usr/lib/python2.7/site-packages/alembic/operations/base.py\", line 319, in
invoke",
"return fn(self, operation)",
" File
\"/usr/lib/python2.7/site-packages/alembic/operations/toimpl.py\", line 123, in
add_column",
"schema=schema",
" File \"/usr/lib/python2.7/site-packages/alembic/ddl/impl.py\",
line 172, in add_column",
"self._exec(base.AddColumn(table_name, column, schema=schema))",
" File \"/usr/lib/python2.7/site-packages/alembic/ddl/impl.py\",
line 118, in _exec",
"return conn.execute(construct, *multiparams, **params)",
" File
\"/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py\", line 948, in
execute",
"return meth(self, multiparams, params)",
" File \"/usr/lib64/python2.7/site-packages/sqlalchemy/sql/ddl.py\",
line 68, in _execute_on_connection",
"return connection._execute_ddl(self, multiparams, params)",
"
[Yahoo-eng-team] [Bug 1917501] Re: Translation issue
** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1917501 Title: Translation issue Status in Glance: Won't Fix Status in glance package in Ubuntu: Expired Bug description: I do some translations on my free time, and I can't understand this message: #234. "An image self url" Can you clarify the meaning, or change the original text? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1917501/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1860689] Re: Install and configure (Red Hat) in glance, [keystone_authtoken], "auth_url" is "auth_uri"
** Changed in: glance Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1860689 Title: Install and configure (Red Hat) in glance, [keystone_authtoken], "auth_url" is "auth_uri" Status in Glance: Fix Released Bug description: In section to edit /etc/glance/glance-api.conf,section [keystone_authtoken], "auth_url" is "auth_uri" This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2019-06-23 07:59:08 SHA: 8c2bc60820783f76c9421d615d3828a88008ca96 Source: https://opendev.org/openstack/glance/src/doc/source/install/install-rdo.rst URL: https://docs.openstack.org/glance/train/install/install-rdo.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1860689/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1875761] Re: Verify operation in glance
** Changed in: glance Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1875761 Title: Verify operation in glance Status in Glance: Fix Released Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: At "4. Confirm upload of the image and validate attributes:", the command shown is "glance image-list", but the output shown below it is from "openstack image list". - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2020-01-28 06:54:43 SHA: 0a0a39aa83cd64128e42be50983af52914595f2b Source: https://opendev.org/openstack/glance/src/doc/source/install/verify.rst URL: https://docs.openstack.org/glance/train/install/verify.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1875761/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1863209] Re: [openstacksdk] image name is not set if filename is not passed to create_image method
This issue is fixed in openstacksdk so marking it as invalid for Glance.
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1863209
Title:
[openstacksdk] image name is not set if filename is not passed to
create_image method
Status in Glance:
Invalid
Bug description:
I want to create an image without uploading image data using
openstacksdk create_image method.
sdkconnection.image.create_image(name, allow_duplicates=True,
**fields)
fields = {"min_disk": min_disk, "min_ram": min_ram,
"disk_format": "qcow2",
"container_format": "bare",
"sha256": ,
"visibility": "private"}
Image is created successfully but it doesn't have any name to it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1863209/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1890073] Re: queen glance image tags were deleted when it's status became active
** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1890073 Title: queen glance image tags were deleted when it's status became active Status in Glance: Won't Fix Bug description: After successfully calling the create private image interface, add a tag to the image. When the image is created, the tag is deleted on glance v2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1890073/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1908008] Re: Glance with cinder backend
Marking won't fix as no updates from the reporter since 2020 December, feel free to re-open it. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1908008 Title: Glance with cinder backend Status in Glance: Won't Fix Bug description: Centos 8.2, Ussuri I´m trying to configure cinder as a glance backend. Glance configuration: stores = cinder default_store = cinder cinder_store_auth_address = http://xx.0.35.200:5000/v3 cinder_store_user_name = cinder cinder_store_password = xx cinder_catalog_info = volumev2::cinder:http://xx.0.35.200:8776/v3/%(tenant_id)s cinder_store_project_name = service Cinder configuration: allowed_direct_url_schemes = cinder image_upload_use_internal_tenant = True But I´m receiving this message: 2020-12-13 21:42:31.481 134945 ERROR glance.api.v2.image_data [req-083c3f07-15dd-458c-bcce-95b8313a7260 - - - - -] Failed to upload image data due to internal error: cinderclient.exceptions.BadRequest: Invalid input for field/attribute image_owner. Value: None. None is not of type 'string' (HTTP 400) (Request-ID: req-e0e72f00-27bd-4ed6-b8c2-018623be7a69) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi [req-083c3f07-15dd-458c-bcce-95b8313a7260 - - - - -] Caught error: Invalid input for field/attribute image_owner. Value: None. None is not of type 'string' (HTTP 400) (Request-ID: req-e0e72f00-27bd-4ed6-b8c2-018623be7a69): cinderclient.exceptions.BadRequest: Invalid input for field/attribute image_owner. Value: None. None is not of type 'string' (HTTP 400) (Request-ID: req-e0e72f00-27bd-4ed6-b8c2-018623be7a69) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi Traceback (most recent call last): 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/glance/common/wsgi.py", line 1349, in __call__ 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi request, **action_args) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/glance/common/wsgi.py", line 1392, in dispatch 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi return method(*args, **kwargs) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/glance/common/utils.py", line 416, in wrapped 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi return func(self, req, *args, **kwargs) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/glance/api/v2/image_data.py", line 299, in upload 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi self._restore(image_repo, image) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi self.force_reraise() 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi six.reraise(self.type_, self.value, self.tb) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi raise value 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/glance/api/v2/image_data.py", line 164, in upload 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi image.set_data(data, size, backend=backend) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/glance/domain/proxy.py", line 198, in set_data 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi self.base.set_data(data, size, backend=backend, set_active=set_active) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/glance/notifier.py", line 501, in set_data 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi _send_notification(notify_error, 'image.upload', msg) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi self.force_reraise() 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi six.reraise(self.type_, self.value, self.tb) 2020-12-13 21:42:31.508 134945 ERROR glance.common.wsgi File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise 2020-12-13 21:42:31.508 134945 ERROR
[Yahoo-eng-team] [Bug 1912001] Re: glance allows reserved properties during create()
** Changed in: glance Status: New => Fix Released ** Changed in: glance Assignee: (unassigned) => Dan Smith (danms) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1912001 Title: glance allows reserved properties during create() Status in Glance: Fix Released Bug description: Certain image properties are reserved for internal glance usage, such as os_glance_import_task. Changing these properties is disallowed during PATCH. However, glance does not enforce that they are not present in an image POST. It should. This command: openstack --debug image create --container-format bare --disk-format qcow2 \ --property os_glance_import_task=foobar test succeeds in creating an image with os_glance_import_task set. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1912001/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1913625] Re: Glance will leak staging data
** Changed in: glance Status: Confirmed => Fix Released ** Changed in: glance Assignee: (unassigned) => Dan Smith (danms) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1913625 Title: Glance will leak staging data Status in Glance: Fix Released Bug description: In various situations, glance will leak (potentially very large) temporary files in the staging store. One example is doing a web-download import, where glance initially downloads the image to its staging store. If the worker doing that activity crashes, loses power, etc, the user may delete the image and try again on another worker. When the crashed worker resumes, the staging data will remain but nothing will ever clean it up. Another example would be a misconfigured glance that uses local staging directories, but glance-direct is used, where the user stages data, and then deletes the image from another worker. Even in a situation where shared staging is properly configured, a failure to access the staging location during the delete call will result in the image being deleted, but the staging file not being purged. IMHO, glance workers should clean their staging directories at startup, purging any data that is attributable to a previous image having been deleted. Another option is to add a store location for each staged image, and make sure the scrubber can clean those things from the staging directory periodically (this requires also running the scrubber on each node, which may not be common practice currently). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1913625/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1914826] Re: web-download with invalid url does not report error
** Changed in: glance
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1914826
Title:
web-download with invalid url does not report error
Status in Glance:
Fix Released
Bug description:
In my testing, if I provide a URL to web-download that yields an error
from urlopen(), I never see the store listed in the
os_glance_failed_import list, and the store remains in
os_glance_importing_to_stores. The image status does not change, which
means there's no way for the API client to know that the import
failed.
I found this when debugging a gate issue where occasionally the
tempest web-download test fails. It ends up waiting many minutes for
the import to complete, even though it failed long before that. In
that case, the cirros link we use for testing web-download raised a
timeout.
From my log, here what we log as returning to the user just before we
start the import:
Feb 05 20:18:02 guaranine devstack@g-api.service[1008592]: DEBUG
oslo_policy.policy [-] enforce: rule="modify_image"
creds={"domain_id": null, "is_admin_project": true,
"project_domain_id": "default", "project_id":
"59a5997403484e97803cac28b7aa7366", "roles": ["reader", "member"],
"service_project_domain_id": null, "service_project_id": null,
"service_roles": [], "service_user_domain_id": null,
"service_user_id": null, "system_scope": null, "user_domain_id":
"default", "user_id": "10e5d60c60e54ab3889bcd57e367fe01"}
target={"checksum": null, "container_format": "bare", "created_at":
"2021-02-05T20:18:03.00", "disk_format": "raw",
"extra_properties": {}, "image_id": "70917fce-
bfc6-4d57-aa54-58235d09cf24", "locations": [], "min_disk": 0,
"min_ram": 0, "name": "test", "os_glance_failed_import": "",
"os_glance_import_task": "e2cb5441-8c92-45c6-9363-f4b7915401e1",
"os_glance_importing_to_stores": "cheap", "os_hash_algo": null,
"os_hash_value": null, "os_hidden": false, "owner":
"59a5997403484e97803cac28b7aa7366", "protected": false, "size": null,
"status": "importing", "tags": [], "updated_at":
"2021-02-05T20:18:03.00", "virtual_size": null, "visibility":
"shared"} {{(pid=1008592) enforce /usr/local/lib/python3.8/dist-
packages/oslo_policy/policy.py:994}}
Note that os_glance_importing_to_stores="cheap" and
os_glance_failed_import="". Shortly after this, the web-download task
fails:
Feb 05 20:18:03 guaranine devstack@g-api.service[1008592]: ERROR
glance.async_.flows._internal_plugins.web_download [-] Task
e2cb5441-8c92-45c6-9363-f4b7915401e1 failed with exception : urllib.error.URLError:
Here's where the task is fully reverted:
Feb 05 20:18:03 guaranine devstack@g-api.service[1008592]: WARNING
glance.async_.taskflow_executor [-] Task 'api_image_import-WebDownlo
ad-e2cb5441-8c92-45c6-9363-f4b7915401e1'
(bc722b5c-ddd4-404b-9c09-8625ed9c5941) transitioned into state 'REVERTED' from
state 'REVERTIN
G' with result 'None'
And after that, here's what we're still returning to the user:
Feb 05 20:18:03 guaranine devstack@g-api.service[1008592]: DEBUG
oslo_policy.policy [-] enforce: rule="get_image" creds={"domain_id": n
ull, "is_admin_project": true, "project_domain_id": "default", "project_id":
"59a5997403484e97803cac28b7aa7366", "roles": ["reader", "m
ember"], "service_project_domain_id": null, "service_project_id": null,
"service_roles": [], "service_user_domain_id": null, "service_u
ser_id": null, "system_scope": null, "user_domain_id": "default", "user_id":
"10e5d60c60e54ab3889bcd57e367fe01"} target={"checksum": nu
ll, "container_format": "bare", "created_at": "2021-02-05T20:18:03.00",
"disk_format": "raw", "extra_properties": {}, "image_id": "
70917fce-bfc6-4d57-aa54-58235d09cf24", "locations": [], "min_disk": 0,
"min_ram": 0, "name": "test", "os_glance_failed_import": "", "os
_glance_import_task": "e2cb5441-8c92-45c6-9363-f4b7915401e1",
"os_glance_importing_to_stores": "cheap", "os_hash_algo": null, "os_hash_
value": null, "os_hidden": false, "owner":
"59a5997403484e97803cac28b7aa7366", "protected": false, "size": null, "status":
"queued", "t
ags": [], "updated_at": "2021-02-05T20:18:03.00", "virtual_size": null,
"visibility": "shared"} {{(pid=1008592) enforce /usr/local/
lib/python3.8/dist-packages/oslo_policy/policy.py:994}}
Note that os_glance_importing_to_stores="cheap" and
os_glance_failed_import="". In this case, "cheap" should have moved
from "importing" to "failed".
I wrote a tempest negative test for this situation using a totally
bogus URL, which is here:
https://review.opendev.org/c/openstack/tempest/+/774303
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1914826/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
[Yahoo-eng-team] [Bug 1916011] Re: test_migrate_image_after_upgrade failing because of glance cinder store change
** Changed in: glance Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1916011 Title: test_migrate_image_after_upgrade failing because of glance cinder store change Status in Glance: Fix Released Bug description: The test_migrate_image_after_upgrade is failing[1] with change[2] in glance store [1] https://f709d50a480576319de8-9ac17d813a47c2e69fd653e5129cc971.ssl.cf2.rackcdn.com/periodic/opendev.org/openstack/glance/master/glance-tox-functional-py36-glance_store-tips/f97f4be/testr_results.html [2] https://review.opendev.org/c/openstack/glance_store/+/774703 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1916011/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1108979] Re: v1 headers are not decoded
Glance does not support V1 and its has been removed since Ussuri. ** Changed in: glance Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1108979 Title: v1 headers are not decoded Status in Glance: Won't Fix Bug description: In the v1.1 API, metadata headers are assumed to be ASCII-only (which is the case in python-glanceclient currently - see bug 1108969). However, in theory they could be encoded in a number of ways. If bug 1008969 is to be fixed, glance needs to support decoding the headers using the MIME header encoding rules from RFC 2047 (http://www.ietf.org/rfc/rfc2047.txt ). For reference the format of the header field contents is defined in section 4.2 of RFC 2616: field-content = http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2 ...which must be further interpreted using section 2.2: The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message parser. Words of *TEXT MAY contain characters from character sets other than ISO-8859-1 only when encoded according to the rules of RFC 2047. TEXT = http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1108979/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1450041] Re: Glance v1 api returns 500 on NotAuthenticated in registry
Glance does not support V1 and its has been removed since Ussuri. ** Changed in: glance Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1450041 Title: Glance v1 api returns 500 on NotAuthenticated in registry Status in Glance: Won't Fix Bug description: If some operation with an image (v1 create/show/delete) fails due to keystone token expiration during a glance-registry operation, glance- api returns 500 InternalServerError as NotAuthenticated exception is not expected in any of the api methods. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1450041/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1471215] Re: Need to add url encode before give response to image show for v1
Glance does not support V1 and its has been removed since Ussuri. ** Changed in: glance Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1471215 Title: Need to add url encode before give response to image show for v1 Status in Glance: Won't Fix Bug description: If we use http proxy ip like a glance endpoint and add metadata for image in bug: https://bugs.launchpad.net/horizon/+bug/1449260 then http response have wrong HTTP type. reproduced on branch: stable/juno Steps to reproduce: Precondition steps: httpproxy glance endpoint: http://192.168.0.2:9292 host ip with runned glance-api: 192.168.0.6 Step 1. Create glance image, e.g.: glance image-create --name test --id --disk-format qcow2 --container-format bare --file response: http://paste.openstack.org/show/338516/ Step 2. Show glance image using v1 glance api and using curl: glance --debug --os-image-api-version 1 image-show response: http://paste.openstack.org/show/338515/ curl -v -i -X HEAD -H 'X-Auth-Token: ' http://192.168.0.2:9292/v1/images/ response: http://paste.openstack.org/show/338528/ Step 3. Add metadata like in bug: https://bugs.launchpad.net/horizon/+bug/1449260 using horizon or python v2 glance client. e.g.: cat glance_add_meta.py: http://paste.openstack.org/show/338529/) python glance_add_meta.py Step 4. Repead step 2. Expected result: GET 200 responce Actual result Responses: 502 Bad Gateway: curl -v -i -X HEAD -H 'X-Auth-Token: ' http://192.168.0.2:9292/v1/images/ response: http://paste.openstack.org/show/338531/ glance --debug --os-image-api-version 1 image-show response: http://paste.openstack.org/show/338533/ -- If we use for CURl request host ip(bypass httpproxy glance endpoint) we have 200 OK. curl -v -i -X HEAD -H 'X-Auth-Token: ' http://192.168.0.6:9292/v1/images/ response: http://paste.openstack.org/show/338535/ If we use for CLI request os-image-url like a host ip (bypass httpproxy glance endpoint) we have 200 OK. http://paste.openstack.org/show/338561/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1471215/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1556023] Re: Direct v1 registry access can bypass Glance's policies
Glance does not support V1 and its has been removed since Ussuri.
** Changed in: glance
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1556023
Title:
Direct v1 registry access can bypass Glance's policies
Status in Glance:
Won't Fix
Status in OpenStack Security Advisory:
Won't Fix
Bug description:
If a non-admin user can access the registry directly, then they can
bypass Glance's policies.
Here, for example, is a registry request which bypasses both the
policy to mark an image as public, and to set the image location
directly:
PUT /images/37d89430-8bf2-433a-843e-909c752866df HTTP/1.1.
Host: 127.0.0.1:9191.
Content-Length: 606.
Accept-Encoding: gzip, deflate.
Accept: application/json.
x-auth-token: dc9e09e4954d4b42983784b3c4642bd9.
Connection: keep-alive.
User-Agent: restfuzz-0.1.0.
Content-Type: application/json.
.
{"image": {"status": "active", "deleted": false, "name":
"testpublic", "container_format": "bare", "min_ram": 2147483647,
"disk_format": "qcow2", "id": "37d89430-8bf2-433a-843e-909c752866df",
"owner": "48c21395db63405d94aee1f965615d1c", "min_disk": 2147483647,
"is_public": true, "properties": {"image_type": "snapshot",
"instance_uuid": "7df74ad1-1caf-44ac-8f4b-4313f5fda5ed", "user_id":
"76b4ded518594216832e06c261523074' or 1=1--", "base_image_ref":
"1c8c3ba8-3a2f-4d06-b1ba-ac1791b599d8"}, "size": 6599958588555,
"virtual_size": 6599958588551, "min_disk": 2147483647,
"location":"http://google.com"}}
Note that deployments should firewall the registry off; typical users should
only have access to the Glance API endpoint.
However, users such as a Swift administrator who does not have Glance admin
powers but is able to access the 'private' network can bypass Glance's policies.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1556023/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1905672] [NEW] Non existing property protection file raises 500 Internal server error
i
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: INFO
eventlet.wsgi.server [None req-43d209a4-3143-4855-b843-2137a9cbb22b admin
admin] 10.0.79.216,10.0.79.216 - - [26/Nov/2020 06:49:54] "POST /v2/images
HTTP/1.1" 500 454 0.053478
Nov 26 06:50:21 akekane-wallaby-dev glance-api[15444]: DEBUG
glance.image_cache.prefetcher [-] Nothing to prefetch. {{(pid=15444) run
/opt/stack/glance/glance/image_cache/prefetcher.py:76}}
** Affects: glance
Importance: Low
Assignee: Abhishek Kekane (abhishek-kekane)
Status: New
** Changed in: glance
Importance: Undecided => Low
** Changed in: glance
Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1905672
Title:
Non existing property protection file raises 500 Internal server error
Status in Glance:
New
Bug description:
Non existing property protection file raises 500 Internal server error
If admin/operator specifies non existing property protection file in
glance-api.conf then create/update image call raises 500 Internal
server error.
Steps to reproduce:
1. Enable property protection in glance-api.conf and provide non existing
file
[Default]
property_protection_file = non_existing_file.yaml
property_protection_rule_format = policies
2. Restart glance-api service
3. Create image by specifiying additional property
glance image-create-via-import --disk-format qcow2 --container-format bare
--name conversion_test --import-method web-download --uri
https://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img --property
xyz=xyz
Expected Result:
API should return 400 Bad request
Actual result:
Returns 500 Internal server error
Glance API Logs:
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.property_utils [None req-43d209a4-3143-4855-b843-2137a9cbb22b
admin admin] Couldn't find property protection file /etc/glance/property.yaml:
'NoneType' object is not iterable.
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi [None req-43d209a4-3143-4855-b843-2137a9cbb22b admin admin]
Caught error: Invalid configuration in property protection file.:
glance.common.exception.InvalidPropertyProtectionConfiguration: Invalid
configuration in property protection file.
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi Traceback (most recent call last):
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi File "/opt/stack/glance/glance/common/property_utils.py",
line 119, in _load_rules
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi CONFIG.read(conf_file)
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi File "/usr/lib/python3.6/configparser.py", line 694, in
read
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi for filename in filenames:
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi TypeError: 'NoneType' object is not iterable
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi During handling of the above exception, another exception
occurred:
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi Traceback (most recent call last):
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1348,
in __call__
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi request, **action_args)
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1391,
in dispatch
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi return method(*args, **kwargs)
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi File "/opt/stack/glance/glance/common/utils.py", line 416,
in wrapped
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi return func(self, req, *args, **kwargs)
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi File "/opt/stack/glance/glance/api/v2/images.py", line 74,
in create
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi image_factory =
self.gateway.get_image_factory(req.context)
Nov 26 06:49:54 akekane-wallaby-dev glance-api[15444]: ERROR
glance.common.wsgi File "
[Yahoo-eng-team] [Bug 1891190] Re: test_reload() functional test causes hang and jobs TIMED_OUT
** Changed in: glance Status: New => Fix Released ** Changed in: glance Assignee: (unassigned) => Dan Smith (danms) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1891190 Title: test_reload() functional test causes hang and jobs TIMED_OUT Status in Glance: Fix Released Bug description: The glance.tests.functional.test_reload.TestReload.test_reload() test has been causing spurious deadlocks in functional test jobs, resulting in TIMED_OUT job statuses due to the global timeout expiring. This can be reproduced locally with lots of exposure, but Zuul runs things enough to hit it fairly often. I have tracked this down to the test_reload() test, which if I reproduce this locally, I find it is in an infinite waitpid() on the API master process that the FunctionalTest base class has started for it. The test tracks child PIDs of the master as it initiates several SIGHUP operations. Upon exit, the FunctionalTest.cleanup() routine runs and ends up waitpid()ing on the master process forever. A process list shows all the other stestr workers in Z state waiting for the final worker to complete. The final worker being stuck on waitpid() has the master process and both worker processes still running. Upon killing the master, stestr frees up, reports status from the test and exits normally. Stack trace of the hung test process after signaling the master it is waiting for manually is: Traceback (most recent call last): File "/usr/lib64/python3.7/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.7/runpy.py", line 85, in _run_code exec(code, run_globals) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/stestr/subunit_runner/run.py", line 93, in main() File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/stestr/subunit_runner/run.py", line 89, in main testRunner=partial(runner, stdout=sys.stdout)) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/stestr/subunit_runner/program.py", line 185, in __init__ self.runTests() File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/stestr/subunit_runner/program.py", line 226, in runTests self.result = testRunner.run(self.test) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/stestr/subunit_runner/run.py", line 52, in run test(result) File "/usr/lib64/python3.7/unittest/suite.py", line 84, in __call__ return self.run(*args, **kwds) File "/usr/lib64/python3.7/unittest/suite.py", line 122, in run test(result) File "/usr/lib64/python3.7/unittest/suite.py", line 84, in __call__ return self.run(*args, **kwds) File "/usr/lib64/python3.7/unittest/suite.py", line 122, in run test(result) File "/usr/lib64/python3.7/unittest/suite.py", line 84, in __call__ return self.run(*args, **kwds) File "/usr/lib64/python3.7/unittest/suite.py", line 122, in run test(result) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/unittest2/case.py", line 673, in __call__ return self.run(*args, **kwds) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/testtools/testcase.py", line 675, in run return run_test.run(result) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/testtools/runtest.py", line 80, in run return self._run_one(actual_result) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/testtools/runtest.py", line 94, in _run_one return self._run_prepared_result(ExtendedToOriginalDecorator(result)) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/testtools/runtest.py", line 119, in _run_prepared_result raise e File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/testtools/runtest.py", line 191, in _run_user return fn(*args, **kwargs) File "/home/dan/glance/glance/tests/functional/__init__.py", line 881, in cleanup s.stop() File "/home/dan/glance/glance/tests/functional/__init__.py", line 293, in stop rc = test_utils.wait_for_fork(self.process_pid, raise_error=False) File "/home/dan/glance/glance/tests/utils.py", line 294, in wait_for_fork (pid, rc) = os.waitpid(pid, 0) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/eventlet/green/os.py", line 96, in waitpid greenthread.sleep(0.01) File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/eventlet/greenthread.py", line 36, in sleep hub.switch() File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/eventlet/hubs/hub.py", line 298, in switch return self.greenlet.switch() File "/home/dan/glance/.tox/functional/lib/python3.7/site-packages/eventlet/hubs/hub.py",
[Yahoo-eng-team] [Bug 1891352] Re: Failed import of one store will remain in progress forever if all_stores_must_succeed=True
** Also affects: glance/ussuri Importance: Undecided Status: New ** Changed in: glance Assignee: (unassigned) => Dan Smith (danms) ** Changed in: glance/ussuri Assignee: (unassigned) => Dan Smith (danms) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1891352 Title: Failed import of one store will remain in progress forever if all_stores_must_succeed=True Status in Glance: Fix Released Status in Glance ussuri series: New Bug description: If import is called with all_stores_must_succeed=True and a store fails during set_image_data(), the store will remain in os_glance_importing_stores forever, never going into the os_glance_failed_import list. This means a polling client will never notice that the import failed. Further, if multiple stores are included in the import, and the failure happens in the later stores, the revert process will remove the earlier stores (after they had already been reported as available in stores). This means a polling client doing an import on an image already in store1 to store2,store3,store4 will see the following progression: stores=store1;os_glance_importing_to_stores=store2,store3,store4 stores=store1,store2;os_glance_importing_to_stores=store3,store4 stores=store1,store2,store3;os_glance_importing_to_stores=store4 stores=store1,store2;os_glance_importing_to_stores=store4 stores=store1;os_glance_importing_to_stores=store4 The last line, forever, and never see anything in os_glance_failed_import To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1891352/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1890994] Re: can not Specify backend when creating image from volume
** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1890994 Title: can not Specify backend when creating image from volume Status in Glance: Invalid Bug description: I want to use the multi-store for glance in my environment，so I use cinder as backend. The configuration file is as follows： [DEFAULT] enabled_backends = g2:cinder, g5:cinder [g2] cinder_api_insecure = true cinder_os_region_name = region-sandev cinder_store_auth_address = http://keystone-api.openstack.svc.region-sandev.myinspurcloud.com:5000/v3 cinder_store_password = qjUAkJ6QGNJMzU7 cinder_store_project_name = cloud-poss cinder_store_user_name = image-admin cinder_volume_type = volume_for_glance [g5] cinder_api_insecure = true cinder_os_region_name = region-sandev cinder_store_auth_address = http://keystone-api.openstack.svc.region-sandev.myinspurcloud.com:5000/v3 cinder_store_password = qjUAkJ6QGNJMzU7 cinder_store_project_name = cloud-poss cinder_store_user_name = image-admin cinder_volume_type = g5-sas-1 Then I found that openstackclient can't use "--backend" ,so I used glanceclient ,it works. However I need create image from volume, glanceclient doesn't support the parameter "--volume" . openstackclient can use "--volume" but not "--backend" .To make matters worse,I found parameter "--backend" only supports creating image from file. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1890994/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1888349] [NEW] glance-cache-manage utility is broken
Public bug reported: When I try to run any of glance-cache-manage command it fails with below error; glance-cache-manage --host 172.16.2.23 list-cached Traceback (most recent call last): File "/usr/bin/glance-cache-manage", line 6, in from glance.cmd.cache_manage import main File "/usr/lib/python3.6/site-packages/glance/cmd/cache_manage.py", line 46, in import glance.image_cache.client File "/usr/lib/python3.6/site-packages/glance/image_cache/__init__.py", line 30, in from glance.common import utils File "/usr/lib/python3.6/site-packages/glance/common/utils.py", line 50, in from glance.common import wsgi File "/usr/lib/python3.6/site-packages/glance/common/wsgi.py", line 61, in from glance.image_cache import prefetcher File "/usr/lib/python3.6/site-packages/glance/image_cache/prefetcher.py", line 28, in from glance.image_cache import base File "/usr/lib/python3.6/site-packages/glance/image_cache/base.py", line 15, in from glance.image_cache import ImageCache ImportError: cannot import name 'ImageCache' . glance-cache-manage --help Traceback (most recent call last): File "/usr/bin/glance-cache-manage", line 6, in from glance.cmd.cache_manage import main File "/usr/lib/python3.6/site-packages/glance/cmd/cache_manage.py", line 46, in import glance.image_cache.client File "/usr/lib/python3.6/site-packages/glance/image_cache/__init__.py", line 30, in from glance.common import utils File "/usr/lib/python3.6/site-packages/glance/common/utils.py", line 50, in from glance.common import wsgi File "/usr/lib/python3.6/site-packages/glance/common/wsgi.py", line 61, in from glance.image_cache import prefetcher File "/usr/lib/python3.6/site-packages/glance/image_cache/prefetcher.py", line 28, in from glance.image_cache import base File "/usr/lib/python3.6/site-packages/glance/image_cache/base.py", line 15, in from glance.image_cache import ImageCache ImportError: cannot import name 'ImageCache' ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Affects: glance/train Importance: High Status: New ** Affects: glance/ussuri Importance: High Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => High ** Also affects: glance/train Importance: Undecided Status: New ** Also affects: glance/ussuri Importance: Undecided Status: New ** Changed in: glance/ussuri Importance: Undecided => High ** Changed in: glance/train Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1888349 Title: glance-cache-manage utility is broken Status in Glance: New Status in Glance train series: New Status in Glance ussuri series: New Bug description: When I try to run any of glance-cache-manage command it fails with below error; glance-cache-manage --host 172.16.2.23 list-cached Traceback (most recent call last): File "/usr/bin/glance-cache-manage", line 6, in from glance.cmd.cache_manage import main File "/usr/lib/python3.6/site-packages/glance/cmd/cache_manage.py", line 46, in import glance.image_cache.client File "/usr/lib/python3.6/site-packages/glance/image_cache/__init__.py", line 30, in from glance.common import utils File "/usr/lib/python3.6/site-packages/glance/common/utils.py", line 50, in from glance.common import wsgi File "/usr/lib/python3.6/site-packages/glance/common/wsgi.py", line 61, in from glance.image_cache import prefetcher File "/usr/lib/python3.6/site-packages/glance/image_cache/prefetcher.py", line 28, in from glance.image_cache import base File "/usr/lib/python3.6/site-packages/glance/image_cache/base.py", line 15, in from glance.image_cache import ImageCache ImportError: cannot import name 'ImageCache' . glance-cache-manage --help Traceback (most recent call last): File "/usr/bin/glance-cache-manage", line 6, in from glance.cmd.cache_manage import main File "/usr/lib/python3.6/site-packages/glance/cmd/cache_manage.py", line 46, in import glance.image_cache.client File "/usr/lib/python3.6/site-packages/glance/image_cache/__init__.py", line 30, in from glance.common import utils File "/usr/lib/python3.6/site-packages/glance/common/utils.py", line 50, in from glance.common import wsgi File "/usr/lib/python3.6/site-packages/glance/common/
[Yahoo-eng-team] [Bug 1886374] [NEW] Improve lazy loading mechanism for multiple stores
Public bug reported: Glance has a facility lazy loading for legacy images which will be called on get/list api calls to add store information in image's location metadata based on location URL of image. Even if admin decides to change the store names in glance-api.conf same will also be updated in location metadata for all images related to that particular store. Current implementation of legacy image performs this operation on each get/list call as location metadata is not getting updated in database or it doesn't handle to perform store name check in glance-api.conf Proposed fix for improvements: 1. Save updated location metadata information in database permanently 2. Add logic to perform lazy loading only if store information is not present in location metadata or store present in location metadata is not defined in glance's enbaled_backends configuration option. ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Affects: glance/train Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Affects: glance/ussuri Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => High ** Also affects: glance/train Importance: Undecided Status: New ** Also affects: glance/victoria Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Also affects: glance/ussuri Importance: Undecided Status: New ** No longer affects: glance/victoria ** Changed in: glance/ussuri Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance/train Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1886374 Title: Improve lazy loading mechanism for multiple stores Status in Glance: New Status in Glance train series: New Status in Glance ussuri series: New Bug description: Glance has a facility lazy loading for legacy images which will be called on get/list api calls to add store information in image's location metadata based on location URL of image. Even if admin decides to change the store names in glance-api.conf same will also be updated in location metadata for all images related to that particular store. Current implementation of legacy image performs this operation on each get/list call as location metadata is not getting updated in database or it doesn't handle to perform store name check in glance- api.conf Proposed fix for improvements: 1. Save updated location metadata information in database permanently 2. Add logic to perform lazy loading only if store information is not present in location metadata or store present in location metadata is not defined in glance's enbaled_backends configuration option. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1886374/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1881958] [NEW] read-only http store should not be used if --all-stores specified for import/copy image workflow
Public bug reported: In Ussuri release we have added new functionality to import image in multiple stores or copy existing image in multiple stores. To ease user experience we have given a option --all-stores in glanceclient which avoids user to specify all the configured stores explicitly for these new operations. Now, if operator has configured read-only 'http' store and while creating or copying image if user has specified --all-stores true then depending on `allow-failure`; if it is True then image is imported/copied to other stores than http or if it is false then image can not be imported/copied to other stores as well. Aslo, new image property `os_glance_failed_imports` shows `http` as failed store. Expected flow: If operator configures 'http' store as then it should not be included in import/copying operation if --all-stores specified by user. ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1881958 Title: read-only http store should not be used if --all-stores specified for import/copy image workflow Status in Glance: New Bug description: In Ussuri release we have added new functionality to import image in multiple stores or copy existing image in multiple stores. To ease user experience we have given a option --all-stores in glanceclient which avoids user to specify all the configured stores explicitly for these new operations. Now, if operator has configured read-only 'http' store and while creating or copying image if user has specified --all-stores true then depending on `allow-failure`; if it is True then image is imported/copied to other stores than http or if it is false then image can not be imported/copied to other stores as well. Aslo, new image property `os_glance_failed_imports` shows `http` as failed store. Expected flow: If operator configures 'http' store as then it should not be included in import/copying operation if --all-stores specified by user. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1881958/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1873735] [NEW] Functional test 'test_image_member_lifecycle_for_multiple_stores' fails intermittently for py37
Public bug reported: Functional test test_image_member_lifecycle_for_multiple_stores failing intermittently for python 37 in upstream zuul checks. Same test is passing with python 3.6 environment and also passes in local environment for python 3.7 No fruitful information from logs either. Reference logs http://paste.openstack.org/show/792390/ ** Affects: glance Importance: High Status: New ** Changed in: glance Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1873735 Title: Functional test 'test_image_member_lifecycle_for_multiple_stores' fails intermittently for py37 Status in Glance: New Bug description: Functional test test_image_member_lifecycle_for_multiple_stores failing intermittently for python 37 in upstream zuul checks. Same test is passing with python 3.6 environment and also passes in local environment for python 3.7 No fruitful information from logs either. Reference logs http://paste.openstack.org/show/792390/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1873735/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1871588] [NEW] copy-image, multiple image imports dosen't work as expected if all_stores_must_succeed passed as string
Public bug reported:
If user passes 'all_stores_must_succeed' as 'false' in copy-image, multiple
image imports request body then it does not work as expected.
Expected is to skip the failure store and continue copying/importing image to
other stores but instead it stops execution of task and revert it and deletes
the image data copied/imported to previous stores.
How to reproduce:
1. Ensure multipe stores are enabled in your environment and multiple stores
are configured
2. Run below commands to import image in multiple stores
glance --debug image-create-via-import --container-format ami --disk-format
ami --name import_scenario --file gentoo_root.img --all-stores True
--allow-failure True
(internal curl command to API - curl -g -i -X POST
http://192.168.100.13:9292/v2/images/04f891c8-1a20-4c3d-a270-59b1123584cb/import
-H "Content-Type: application/json" -H "User-Agent: python-glanceclient" -H
"X-Auth-Token:
{SHA256}b83a45c9d14131f4d461af948a9c2bf961a035762c3af6e9cc7432bb5e33b2bb" -d
'{"method": {"name": "glance-direct"}, "stores": ["ceph", "cheap", "slow",
"reliable", "common"], "all_stores_must_succeed": "false"}')
Assume failure occures while importing image to "slow" store
Expected result:
Image should be uploaded to all other stores except "slow" store
Actual result:
Image remains in 'importing' state and data imported to previous stores get
deleted while reverting the import tasks.
** Affects: glance
Importance: Critical
Assignee: Abhishek Kekane (abhishek-kekane)
Status: New
** Changed in: glance
Importance: Undecided => Critical
** Changed in: glance
Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1871588
Title:
copy-image, multiple image imports dosen't work as expected if
all_stores_must_succeed passed as string
Status in Glance:
New
Bug description:
If user passes 'all_stores_must_succeed' as 'false' in copy-image, multiple
image imports request body then it does not work as expected.
Expected is to skip the failure store and continue copying/importing image to
other stores but instead it stops execution of task and revert it and deletes
the image data copied/imported to previous stores.
How to reproduce:
1. Ensure multipe stores are enabled in your environment and multiple stores
are configured
2. Run below commands to import image in multiple stores
glance --debug image-create-via-import --container-format ami
--disk-format ami --name import_scenario --file gentoo_root.img --all-stores
True --allow-failure True
(internal curl command to API - curl -g -i -X POST
http://192.168.100.13:9292/v2/images/04f891c8-1a20-4c3d-a270-59b1123584cb/import
-H "Content-Type: application/json" -H "User-Agent: python-glanceclient" -H
"X-Auth-Token:
{SHA256}b83a45c9d14131f4d461af948a9c2bf961a035762c3af6e9cc7432bb5e33b2bb" -d
'{"method": {"name": "glance-direct"}, "stores": ["ceph", "cheap", "slow",
"reliable", "common"], "all_stores_must_succeed": "false"}')
Assume failure occures while importing image to "slow" store
Expected result:
Image should be uploaded to all other stores except "slow" store
Actual result:
Image remains in 'importing' state and data imported to previous stores
get deleted while reverting the import tasks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1871588/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1861723] Re: Glance is listening on TCP socket before store initialization
** Changed in: glance Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1861723 Title: Glance is listening on TCP socket before store initialization Status in Glance: Fix Released Bug description: When multiple backends is being used with rbd backend, Glance tries to get fsid of the cluster using rados library. If even one of the rbd backends is unavailable, glance-api wsgi fails to start properly, but continue listening on the tcp socket and not responding at any request until the timeout. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1861723/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1813147] Re: p35 jobs are failing with subunit.parser ... FAILED
** Changed in: glance
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1813147
Title:
p35 jobs are failing with subunit.parser ... FAILED
Status in Glance:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Various py35 jobs[1] are failing recently with:
2019-01-22 00:10:44.708744 | ubuntu-xenial | {0} subunit.parser [0.000360s]
... FAILED
2019-01-22 00:10:44.708947 | ubuntu-xenial |
2019-01-22 00:10:44.709000 | ubuntu-xenial | Captured Parser Error:
2019-01-22 00:10:44.709057 | ubuntu-xenial | ~~
2019-01-22 00:10:44.709122 | ubuntu-xenial | b'Short read - got 167
bytes, wanted 4263 bytes'
It seems that when a job fails, the log of the test case that
triggered the failure is truncated. Also it feels that it is caused by
extensive logging.
There was a past cinder bug[2] that was marked fixed after couple of
logging reduction.
There was 11 failures in the last 24 hours[3]
[1]
http://logs.openstack.org/58/632158/1/check/cross-nova-py35/afe0282/job-output.txt#_2019-01-22_00_10_44_708744
[2] https://bugs.launchpad.net/cinder/+bug/1728640
[3]
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22subunit.parser%5C%22%20AND%20message:%5C%22FAILED%5C%22%20AND%20voting:1=864000s
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1813147/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1867205] [NEW] Reload functionality is broken in Ussuri
Public bug reported: Reload config files doesn't work upon sending sighup signal to glance- api service parent process, resulting in terminating the parent and keeping child processes orphan. ** Affects: glance Importance: High Status: New ** Changed in: glance Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1867205 Title: Reload functionality is broken in Ussuri Status in Glance: New Bug description: Reload config files doesn't work upon sending sighup signal to glance- api service parent process, resulting in terminating the parent and keeping child processes orphan. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1867205/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1863879] [NEW] Multiple import fails if all-stores 'True' is passed
Public bug reported:
Newly added multiple import fails if user passes "all_stores" as "true" in the
request.
The reason is if all_stores is specified then we are getting stores using
CONF.enabled_backends and unfortunately we are injecting reserved stores
'os_glance_staging_store' and 'os_glance_tasks_store' runtime. As a result
import job tries to import the image in the 'os_glance_staging_store' store as
well where it fails as that image is already staged in this staging store.
Steps to reproduce:
1. Create image using
glance --debug image-create-via-import --disk-format qcow2
--container-format bare --name multi-copy-test-13
2. Stage the data for import using
glance image-stage --file
3. import image in multiple stores by setting all_stores as true
curl -g -i -X POST http://192.168.0.27:9292/v2/images//import
"User-Agent: python-glanceclient" -H "Content-Type: application/json" -H
"X-Auth-Token: " -d '{"method": {"name": "glance-direct"}, "all_stores":
"true"}'
Expected result:
Image should be imported in all stores configured using enabled_backends config
option
Actual result:
Image fails to import and data remains in staging area
Possible solution:
After population stores using CONF.enabled_backends, remove reserved stores
from those stores.
** Affects: glance
Importance: High
Assignee: Abhishek Kekane (abhishek-kekane)
Status: New
** Changed in: glance
Importance: Undecided => High
** Changed in: glance
Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1863879
Title:
Multiple import fails if all-stores 'True' is passed
Status in Glance:
New
Bug description:
Newly added multiple import fails if user passes "all_stores" as "true" in
the request.
The reason is if all_stores is specified then we are getting stores using
CONF.enabled_backends and unfortunately we are injecting reserved stores
'os_glance_staging_store' and 'os_glance_tasks_store' runtime. As a result
import job tries to import the image in the 'os_glance_staging_store' store as
well where it fails as that image is already staged in this staging store.
Steps to reproduce:
1. Create image using
glance --debug image-create-via-import --disk-format qcow2
--container-format bare --name multi-copy-test-13
2. Stage the data for import using
glance image-stage --file
3. import image in multiple stores by setting all_stores as true
curl -g -i -X POST http://192.168.0.27:9292/v2/images//import
"User-Agent: python-glanceclient" -H "Content-Type: application/json" -H
"X-Auth-Token: " -d '{"method": {"name": "glance-direct"}, "all_stores":
"true"}'
Expected result:
Image should be imported in all stores configured using enabled_backends
config option
Actual result:
Image fails to import and data remains in staging area
Possible solution:
After population stores using CONF.enabled_backends, remove reserved stores
from those stores.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1863879/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1855417] [NEW] Image data stays in staging store if image is deleted while its in importing state
Public bug reported: Image data stays in staging area (filesystem backend) if image is deleted while it is in 'importing' state. Steps to reproduce: 1. Create image using new import workflow: glance image-create-via-import --disk-format qcow2 --container-format bare --name testing-import-delete --file Expected result: 1. Image should be deleted 2. Image data from staging area should be deleted Actual result: 1. Image is deleted but; 2. Image data from staging area is not deleted ** Affects: glance Importance: Critical Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => Critical -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1855417 Title: Image data stays in staging store if image is deleted while its in importing state Status in Glance: New Bug description: Image data stays in staging area (filesystem backend) if image is deleted while it is in 'importing' state. Steps to reproduce: 1. Create image using new import workflow: glance image-create-via-import --disk-format qcow2 --container-format bare --name testing-import-delete --file Expected result: 1. Image should be deleted 2. Image data from staging area should be deleted Actual result: 1. Image is deleted but; 2. Image data from staging area is not deleted To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1855417/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1844108] [NEW] glance-api fails to start with duplicate option: filesystem_store_datadir error
Public bug reported: Since commit 4265e61bc84ce9bd085a95d8734647f4875af740 [0] is merged, glance-api service fails to start with ERROR: duplicate option: filesystem_store_datadir. The reason for failure is glance_store [1] already registering the options for reserved stores. The above commit was aimed to add reserved stores options in sample config file, but it is also registering the same while doing so. Because of this failure the functional job is also timing out and failing on patch [2]. In order to resolve this issue we should remove the part of registering the reserved store options logic from glance/common/config.py file, so that it can be only used when generating the sample config file. [0]https://github.com/openstack/glance/commit/4265e61bc84ce9bd085a95d8734647f4875af740 [1] https://github.com/openstack/glance_store/blob/master/glance_store/multi_backend.py#L107 [2] https://review.opendev.org/#/c/611253 ** Affects: glance Importance: Critical Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => Critical -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1844108 Title: glance-api fails to start with duplicate option: filesystem_store_datadir error Status in Glance: New Bug description: Since commit 4265e61bc84ce9bd085a95d8734647f4875af740 [0] is merged, glance-api service fails to start with ERROR: duplicate option: filesystem_store_datadir. The reason for failure is glance_store [1] already registering the options for reserved stores. The above commit was aimed to add reserved stores options in sample config file, but it is also registering the same while doing so. Because of this failure the functional job is also timing out and failing on patch [2]. In order to resolve this issue we should remove the part of registering the reserved store options logic from glance/common/config.py file, so that it can be only used when generating the sample config file. [0]https://github.com/openstack/glance/commit/4265e61bc84ce9bd085a95d8734647f4875af740 [1] https://github.com/openstack/glance_store/blob/master/glance_store/multi_backend.py#L107 [2] https://review.opendev.org/#/c/611253 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1844108/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1840898] [NEW] INSTR can not supported for postgresql
Public bug reported: Recently added migration script doesn't support INSTR function. INSTR function does support sqlite3 and mysql. [1] https://review.opendev.org/#/c/665606/5 ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1840898 Title: INSTR can not supported for postgresql Status in Glance: New Bug description: Recently added migration script doesn't support INSTR function. INSTR function does support sqlite3 and mysql. [1] https://review.opendev.org/#/c/665606/5 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1840898/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1840885] [NEW] MultiStore: Lazy update fails if image is not owned by owner
Public bug reported: Recently merged patch [1] adds a capacity to image to update the store location in the location metadata. Lazy update of metadata fails on image-list call if one of the image listed is not owned by the user and throws NotFound error. Environment details: 1. Devstack: latest version 2. glance_store v1.0.0 Steps to reproduce: 1. Enable multiple stores in glance-api.conf (Add below params under respective sections) [Default] enabled_backends = fast:file,cheap:file [glance_store] default_backend = fast [fast] filesystem_store_datadir = /opt/stack/data/glance/fast/ [cheap] filesystem_store_datadir = /opt/stack/data/glance/cheap/ 2. restart glance-api service 3. source using ~/devstack localrc demo demo 4. Run glance image-list command Expected result: All images should be shown Actual Result: HTTP 400 Bad Request: No image found with ID ** Affects: glance Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: cinder Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: cinder Status: New => Invalid ** Project changed: cinder => glance ** Changed in: glance Status: Invalid => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1840885 Title: MultiStore: Lazy update fails if image is not owned by owner Status in Glance: New Bug description: Recently merged patch [1] adds a capacity to image to update the store location in the location metadata. Lazy update of metadata fails on image-list call if one of the image listed is not owned by the user and throws NotFound error. Environment details: 1. Devstack: latest version 2. glance_store v1.0.0 Steps to reproduce: 1. Enable multiple stores in glance-api.conf (Add below params under respective sections) [Default] enabled_backends = fast:file,cheap:file [glance_store] default_backend = fast [fast] filesystem_store_datadir = /opt/stack/data/glance/fast/ [cheap] filesystem_store_datadir = /opt/stack/data/glance/cheap/ 2. restart glance-api service 3. source using ~/devstack localrc demo demo 4. Run glance image-list command Expected result: All images should be shown Actual Result: HTTP 400 Bad Request: No image found with ID To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1840885/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1836140] [NEW] 500 response while try to delete image is in uploading state
Public bug reported:
When image import fails during image is in uploaded from staging area
image remains in uploading state and data remains in staging area. In
this scenario if file store is not enabled then while deleting the image
glance-api returns 500 status code with error 'file' scheme is Unknwon.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/glance_store/backend.py", line 409,
in delete_from_backend
loc = location.get_location_from_uri(uri, conf=CONF)
File "/usr/lib/python2.7/site-packages/glance_store/location.py", line 75,
in get_location_from_uri
raise exceptions.UnknownScheme(scheme=pieces.scheme)
UnknownScheme: Unknown scheme 'file' found in URI
Note:
Solution is similar as proposed in this patch:
https://review.opendev.org/#/c/618468/7
** Affects: glance
Importance: High
Assignee: Abhishek Kekane (abhishek-kekane)
Status: New
** Changed in: glance
Importance: Undecided => High
** Changed in: glance
Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1836140
Title:
500 response while try to delete image is in uploading state
Status in Glance:
New
Bug description:
When image import fails during image is in uploaded from staging area
image remains in uploading state and data remains in staging area. In
this scenario if file store is not enabled then while deleting the
image glance-api returns 500 status code with error 'file' scheme is
Unknwon.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/glance_store/backend.py", line 409,
in delete_from_backend
loc = location.get_location_from_uri(uri, conf=CONF)
File "/usr/lib/python2.7/site-packages/glance_store/location.py", line 75,
in get_location_from_uri
raise exceptions.UnknownScheme(scheme=pieces.scheme)
UnknownScheme: Unknown scheme 'file' found in URI
Note:
Solution is similar as proposed in this patch:
https://review.opendev.org/#/c/618468/7
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1836140/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1832490] [NEW] Avoid keyerror which might cause failure of functional tests
Public bug reported: During rocky glance has added ability to mention 'backend' information in the location as a metadata attribute. As of now while setting a class for multi_store [1] we are accessing 'backend' from location as it will always be present. This can lead us to KeyError if backend is not present/provided to image. To avoid this use dict.get() function which will return None if 'backend' key is not present in the location metadata. Reference: Glance Store tips job [2] is failing with this issue at the moment. [1] https://github.com/openstack/glance/blob/master/glance/location.py#L70 [2] http://logs.openstack.org/periodic/opendev.org/openstack/glance/master/glance-tox-functional-glance_store-tips/27b550c/testr_results.html.gz ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1832490 Title: Avoid keyerror which might cause failure of functional tests Status in Glance: New Bug description: During rocky glance has added ability to mention 'backend' information in the location as a metadata attribute. As of now while setting a class for multi_store [1] we are accessing 'backend' from location as it will always be present. This can lead us to KeyError if backend is not present/provided to image. To avoid this use dict.get() function which will return None if 'backend' key is not present in the location metadata. Reference: Glance Store tips job [2] is failing with this issue at the moment. [1] https://github.com/openstack/glance/blob/master/glance/location.py#L70 [2] http://logs.openstack.org/periodic/opendev.org/openstack/glance/master/glance-tox-functional-glance_store-tips/27b550c/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1832490/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1831963] [NEW] unit tests fails with new glance_store version 0.29.0
Public bug reported: Around 11 unit tests are failing [1] after recent patch [2] to set _url_prefix to store instance is merged. The reason for failure is unit tests tries to create rbd store [3] which is now tries to connect to Rados. As we all know that the zuul jobs does not support ceph/rbd it does not install dependent modules of rbd/ceph, which causes the failure. File "/home/zuul/src/opendev.org/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/glance_store/_drivers/rbd.py", line 270, in get_connection client = rados.Rados(conffile=conffile, rados_id=rados_id) AttributeError: 'NoneType' object has no attribute 'Rados' To avoid these kind of failures, need to drop rbd store from loading as it is not supported in gate. [1] http://logs.openstack.org/40/663740/1/check/cross-glance-py27/50a9a9c/testr_results.html.gz [2] https://review.opendev.org/660340 [3] https://github.com/openstack/glance/blob/master/glance/tests/unit/base.py#L75 ** Affects: glance Importance: Critical Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => Critical -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1831963 Title: unit tests fails with new glance_store version 0.29.0 Status in Glance: New Bug description: Around 11 unit tests are failing [1] after recent patch [2] to set _url_prefix to store instance is merged. The reason for failure is unit tests tries to create rbd store [3] which is now tries to connect to Rados. As we all know that the zuul jobs does not support ceph/rbd it does not install dependent modules of rbd/ceph, which causes the failure. File "/home/zuul/src/opendev.org/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/glance_store/_drivers/rbd.py", line 270, in get_connection client = rados.Rados(conffile=conffile, rados_id=rados_id) AttributeError: 'NoneType' object has no attribute 'Rados' To avoid these kind of failures, need to drop rbd store from loading as it is not supported in gate. [1] http://logs.openstack.org/40/663740/1/check/cross-glance-py27/50a9a9c/testr_results.html.gz [2] https://review.opendev.org/660340 [3] https://github.com/openstack/glance/blob/master/glance/tests/unit/base.py#L75 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1831963/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1828966] Re: tox doesn't catch invalid interpreter
For nova and glance it doesn't run the tests, but for cinder it executes the tests as well. A virtual environment directory py23 is created under .tox directory. ** Also affects: nova Importance: Undecided Status: New ** Also affects: cinder Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1828966 Title: tox doesn't catch invalid interpreter Status in Cinder: New Status in Glance: New Status in OpenStack Compute (nova): New Bug description: When you pass invalid interpreter to tox command it installs dependencies, requirements in virtual environment and exits without running any tests. Actually it should throw error, Interpreter Not Found. tox -e py23 py23 create: /opt/stack/glance/.tox/py23 py23 installdeps: -r/opt/stack/glance/test-requirements.txt py23 develop-inst: /opt/stack/glance py23 installed: alabaster==0.7.12,alembic==1.0.10,amqp==2.4.2,appdirs==1.4.3,asn1crypto==0.24.0,automaton==1.16.0,Babel==2.6.0,cachetools==3.1.0,castellan==1.2.2,certifi==2019.3.9,cffi==1.12.3,chardet==3.0.4,cliff==2.14.1,cmd2==0.8.9,coverage==4.5.3,cryptography==2.6.1,cursive==0.2.2,ddt==1.2.1,debtcollector==1.21.0,decorator==4.4.0,defusedxml==0.6.0,dnspython==1.15.0,doc8==0.8.0,docutils==0.14,dogpile.cache==0.7.1,eventlet==0.24.1,extras==1.0.0,fasteners==0.14.1,fixtures==3.0.0,flake8==2.5.5,future==0.17.1,futurist==1.8.1,-e git+https://git.openstack.org/openstack/glance.git@18e71c8e759aa4031da6258bff519ae206145fe6#egg=glance,glance-store==0.28.0,greenlet==0.4.15,hacking==0.12.0,httplib2==0.12.3,idna==2.8,imagesize==1.1.0,iso8601==0.1.12,Jinja2==2.10.1,jmespath==0.9.4,jsonpatch==1.23,jsonpointer==2.0,jsonschema==2.6.0,keystoneauth1==3.14.0,keystonemiddleware==6.0.0,kombu==4.5.0,linecache2==1.0.0,Mako==1.0.9,MarkupSafe==1.1.1,mccabe==0.2.1,mock==3.0.4,monotonic==1.5,mox3==0.27.0,msgpack==0.6.1,munch==2.3.2,netaddr==0.7.19,netifaces==0.10.9,networkx==2.3,openstacksdk==0.27.0,os-client-config==1.32.0,os-service-types==1.7.0,os-win==4.2.0,oslo.cache==1.34.0,oslo.concurrency==3.29.1,oslo.config==6.9.0,oslo.context==2.22.1,oslo.db==4.46.0,oslo.i18n==3.23.1,oslo.log==3.43.0,oslo.messaging==9.6.0,oslo.middleware==3.38.0,oslo.policy==2.2.0,oslo.serialization==2.29.0,oslo.service==1.38.0,oslo.upgradecheck==0.2.1,oslo.utils==3.41.0,oslotest==3.7.1,osprofiler==2.7.0,packaging==19.0,Paste==3.0.8,PasteDeploy==2.0.1,pbr==5.2.0,pep8==1.5.7,prettytable==0.7.2,psutil==5.6.2,psycopg2==2.8.2,pycadf==2.9.0,pycparser==2.19,pydot==1.4.1,pyflakes==0.8.1,Pygments==2.4.0,pyinotify==0.9.6,PyMySQL==0.9.3,pyOpenSSL==19.0.0,pyparsing==2.4.0,pyperclip==1.7.0,pysendfile==2.0.1,python-barbicanclient==4.8.1,python-dateutil==2.8.0,python-editor==1.0.4,python-keystoneclient==3.19.0,python-mimeparse==1.6.0,python-subunit==1.3.0,python-swiftclient==3.7.0,pytz==2019.1,PyYAML==5.1,repoze.lru==0.7,requests==2.21.0,requestsexceptions==1.4.0,restructuredtext-lint==1.3.0,retrying==1.3.3,rfc3986==1.3.1,Routes==2.4.1,simplegeneric==0.8.1,six==1.12.0,snowballstemmer==1.2.1,Sphinx==2.0.1,sphinxcontrib-applehelp==1.0.1,sphinxcontrib-devhelp==1.0.1,sphinxcontrib-htmlhelp==1.0.2,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.2,sphinxcontrib-serializinghtml==1.1.3,SQLAlchemy==1.2.18,sqlalchemy-migrate==0.12.0,sqlparse==0.3.0,statsd==3.3.0,stestr==2.3.1,stevedore==1.30.1,taskflow==3.4.0,Tempita==0.5.2,tenacity==5.0.4,testrepository==0.0.20,testresources==2.0.1,testscenarios==0.5.0,testtools==2.3.0,traceback2==1.4.0,unittest2==1.1.0,urllib3==1.24.3,vine==1.3.0,voluptuous==0.11.5,wcwidth==0.1.7,WebOb==1.8.5,wrapt==1.11.1,WSME==0.9.3,xattr==0.9.6,yappi==1.0 py23 run-test-pre: PYTHONHASHSEED='1359514857' py23 runtests: commands[0] | find . -type f -name '*.pyc' -delete summary _ py23: commands succeeded congratulations :) To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1828966/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1828966] [NEW] tox doesn't catch invalid interpreter
Public bug reported: When you pass invalid interpreter to tox command it installs dependencies, requirements in virtual environment and exits without running any tests. Actually it should throw error, Interpreter Not Found. tox -e py23 py23 create: /opt/stack/glance/.tox/py23 py23 installdeps: -r/opt/stack/glance/test-requirements.txt py23 develop-inst: /opt/stack/glance py23 installed: alabaster==0.7.12,alembic==1.0.10,amqp==2.4.2,appdirs==1.4.3,asn1crypto==0.24.0,automaton==1.16.0,Babel==2.6.0,cachetools==3.1.0,castellan==1.2.2,certifi==2019.3.9,cffi==1.12.3,chardet==3.0.4,cliff==2.14.1,cmd2==0.8.9,coverage==4.5.3,cryptography==2.6.1,cursive==0.2.2,ddt==1.2.1,debtcollector==1.21.0,decorator==4.4.0,defusedxml==0.6.0,dnspython==1.15.0,doc8==0.8.0,docutils==0.14,dogpile.cache==0.7.1,eventlet==0.24.1,extras==1.0.0,fasteners==0.14.1,fixtures==3.0.0,flake8==2.5.5,future==0.17.1,futurist==1.8.1,-e git+https://git.openstack.org/openstack/glance.git@18e71c8e759aa4031da6258bff519ae206145fe6#egg=glance,glance-store==0.28.0,greenlet==0.4.15,hacking==0.12.0,httplib2==0.12.3,idna==2.8,imagesize==1.1.0,iso8601==0.1.12,Jinja2==2.10.1,jmespath==0.9.4,jsonpatch==1.23,jsonpointer==2.0,jsonschema==2.6.0,keystoneauth1==3.14.0,keystonemiddleware==6.0.0,kombu==4.5.0,linecache2==1.0.0,Mako==1.0.9,MarkupSafe==1.1.1,mccabe==0.2.1,mock==3.0.4,monotonic==1.5,mox3==0.27.0,msgpack==0.6.1,munch==2.3.2,netaddr==0.7.19,netifaces==0.10.9,networkx==2.3,openstacksdk==0.27.0,os-client-config==1.32.0,os-service-types==1.7.0,os-win==4.2.0,oslo.cache==1.34.0,oslo.concurrency==3.29.1,oslo.config==6.9.0,oslo.context==2.22.1,oslo.db==4.46.0,oslo.i18n==3.23.1,oslo.log==3.43.0,oslo.messaging==9.6.0,oslo.middleware==3.38.0,oslo.policy==2.2.0,oslo.serialization==2.29.0,oslo.service==1.38.0,oslo.upgradecheck==0.2.1,oslo.utils==3.41.0,oslotest==3.7.1,osprofiler==2.7.0,packaging==19.0,Paste==3.0.8,PasteDeploy==2.0.1,pbr==5.2.0,pep8==1.5.7,prettytable==0.7.2,psutil==5.6.2,psycopg2==2.8.2,pycadf==2.9.0,pycparser==2.19,pydot==1.4.1,pyflakes==0.8.1,Pygments==2.4.0,pyinotify==0.9.6,PyMySQL==0.9.3,pyOpenSSL==19.0.0,pyparsing==2.4.0,pyperclip==1.7.0,pysendfile==2.0.1,python-barbicanclient==4.8.1,python-dateutil==2.8.0,python-editor==1.0.4,python-keystoneclient==3.19.0,python-mimeparse==1.6.0,python-subunit==1.3.0,python-swiftclient==3.7.0,pytz==2019.1,PyYAML==5.1,repoze.lru==0.7,requests==2.21.0,requestsexceptions==1.4.0,restructuredtext-lint==1.3.0,retrying==1.3.3,rfc3986==1.3.1,Routes==2.4.1,simplegeneric==0.8.1,six==1.12.0,snowballstemmer==1.2.1,Sphinx==2.0.1,sphinxcontrib-applehelp==1.0.1,sphinxcontrib-devhelp==1.0.1,sphinxcontrib-htmlhelp==1.0.2,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.2,sphinxcontrib-serializinghtml==1.1.3,SQLAlchemy==1.2.18,sqlalchemy-migrate==0.12.0,sqlparse==0.3.0,statsd==3.3.0,stestr==2.3.1,stevedore==1.30.1,taskflow==3.4.0,Tempita==0.5.2,tenacity==5.0.4,testrepository==0.0.20,testresources==2.0.1,testscenarios==0.5.0,testtools==2.3.0,traceback2==1.4.0,unittest2==1.1.0,urllib3==1.24.3,vine==1.3.0,voluptuous==0.11.5,wcwidth==0.1.7,WebOb==1.8.5,wrapt==1.11.1,WSME==0.9.3,xattr==0.9.6,yappi==1.0 py23 run-test-pre: PYTHONHASHSEED='1359514857' py23 runtests: commands[0] | find . -type f -name '*.pyc' -delete summary _ py23: commands succeeded congratulations :) ** Affects: glance Importance: Low Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Importance: Undecided => Low ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1828966 Title: tox doesn't catch invalid interpreter Status in Glance: New Bug description: When you pass invalid interpreter to tox command it installs dependencies, requirements in virtual environment and exits without running any tests. Actually it should throw error, Interpreter Not Found. tox -e py23 py23 create: /opt/stack/glance/.tox/py23 py23 installdeps: -r/opt/stack/glance/test-requirements.txt py23 develop-inst: /opt/stack/glance py23 installed: alabaster==0.7.12,alembic==1.0.10,amqp==2.4.2,appdirs==1.4.3,asn1crypto==0.24.0,automaton==1.16.0,Babel==2.6.0,cachetools==3.1.0,castellan==1.2.2,certifi==2019.3.9,cffi==1.12.3,chardet==3.0.4,cliff==2.14.1,cmd2==0.8.9,coverage==4.5.3,cryptography==2.6.1,cursive==0.2.2,ddt==1.2.1,debtcollector==1.21.0,decorator==4.4.0,defusedxml==0.6.0,dnspython==1.15.0,doc8==0.8.0,docutils==0.14,dogpile.cache==0.7.1,eventlet==0.24.1,extras==1.0.0,fasteners==0.14.1,fixtures==3.0.0,flake8==2.5.5,future==0.17.1,futurist==1.8.1,-e git+https://git.openstack.org/openstack/glance.git@18e71c8e759aa4031da6258bff519ae206145fe6#egg=glance,glance-store==0.28.0,greenlet==0.4.15,hacking==0.12.0,httplib2==
[Yahoo-eng-team] [Bug 1828333] [NEW] changing path of filesystem_store_datadir does not reflect
Public bug reported: If you change the 'filesystem_store_datadir' under glance_store section in glance-api.conf file and restart the glance-api service then it still points towards earlier/default path. DevStack Version: train Change: 0cb721b790baa8f2929f716dc8945f4bfd25f08f Merge "Fix is_neutron_legacy_enabled function" 2019-05-04 22:38:45 + How to reproduce: 1. Modify glance-api.conf file [glance_store] #filesystem_store_datadir = /opt/stack/data/glance/images/ (old path) filesystem_store_datadir = /opt/stack/data/glance/images_1/ #(new path) 2. Restart glance-api service $ sudo systemctl restart devstack@g-api.service Expected result: After restart images_1 directory should be created in /opt/stack/data/glance directory Actual result: images_1 directory is not created. ** Affects: glance Importance: High Status: New ** Changed in: glance Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1828333 Title: changing path of filesystem_store_datadir does not reflect Status in Glance: New Bug description: If you change the 'filesystem_store_datadir' under glance_store section in glance-api.conf file and restart the glance-api service then it still points towards earlier/default path. DevStack Version: train Change: 0cb721b790baa8f2929f716dc8945f4bfd25f08f Merge "Fix is_neutron_legacy_enabled function" 2019-05-04 22:38:45 + How to reproduce: 1. Modify glance-api.conf file [glance_store] #filesystem_store_datadir = /opt/stack/data/glance/images/ (old path) filesystem_store_datadir = /opt/stack/data/glance/images_1/ #(new path) 2. Restart glance-api service $ sudo systemctl restart devstack@g-api.service Expected result: After restart images_1 directory should be created in /opt/stack/data/glance directory Actual result: images_1 directory is not created. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1828333/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1823124] [NEW] Update cache-manage documentation
Public bug reported: During Stein cycle glance has added support to use cache-manage utility of glance using V2 API. Glance has added support for keystone v3 authentication as well. Need to update below new options for doamin information which will be useful in case of v3 authentication: --os-domain-id --os-user-domain-id --os-project-domain-id Also need to add a NOTE on how glance-cache-manage will be used if HA is configured. ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: cinder Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: cinder Status: New => Invalid ** Project changed: cinder => glance ** Changed in: glance Importance: Undecided => High ** Changed in: glance Status: Invalid => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1823124 Title: Update cache-manage documentation Status in Glance: New Bug description: During Stein cycle glance has added support to use cache-manage utility of glance using V2 API. Glance has added support for keystone v3 authentication as well. Need to update below new options for doamin information which will be useful in case of v3 authentication: --os-domain-id --os-user-domain-id --os-project-domain-id Also need to add a NOTE on how glance-cache-manage will be used if HA is configured. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1823124/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1808456] Re: ceph backend reporting meaningless error when no space left
** Also affects: glance-store
Importance: Undecided
Status: New
** Changed in: glance
Status: New => Invalid
** Changed in: glance-store
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1808456
Title:
ceph backend reporting meaningless error when no space left
Status in Glance:
Invalid
Status in glance_store:
New
Bug description:
When uploading image, but there's no space left in ceph(rbd) backend,
client(such as glanceclient) will receive a meaningless error:
500 Internal Server Error: The server has either erred or is incapable of
performing the requested operation. (HTTP 500)
steps to reproduce:
-
1.Prepare ceph backend for glance, make the free space small enough, e.g.
10MB.
To be simple, you also can modify ceph's code(function resize), to let it
raise errno.ENOSPC. I did this way.
2.uploading image: glance image-create --name img2-ceph --visibility public
--disk-format raw --container-format bare --progress --backend rbd --file
/opt/stack/data/glance/images/d4ca8259-168b-42f5-a719-40038362ae8c
logs
-
stack@ubuntu16vmliang:~$ glance image-create --name img2-ceph --visibility
public --disk-format raw --container-format bare --progress --backend rbd
--file /opt/stack/data/glance/images/d4ca8259-168b-42f5-a719-40038362ae8c
>
/usr/local/lib/python2.7/dist-packages/glanceclient/v2/shell.py(555)do_image_upload()
-> backend = None
(Pdb) c
[=>] 100%
+--+--+
| Property | Value|
+--+--+
| checksum | None |
| container_format | bare |
| created_at | 2018-12-14T02:08:36Z |
| disk_format | raw |
| id | 8c2e48f0-aafc-4744-95b6-fe0b6fbfe975 |
| min_disk | 0|
| min_ram | 0|
| name | img2-ceph|
| os_hash_algo | None |
| os_hash_value| None |
| os_hidden| False|
| owner| 3242a198f7044fcd9b756866ec296391 |
| protected| False|
| size | None |
| status | queued |
| tags | [] |
| updated_at | 2018-12-14T02:08:36Z |
| virtual_size | Not available|
| visibility | public |
+--+--+
500 Internal Server Error: The server has either erred or is incapable of
performing the requested operation. (HTTP 500)
expected
-
The correct message should be something related "Storage Full", rbd.py should
raise glance_store.StorageFull, and this exception will be caught by
notifier.py.
Some code snippet in notifier.py:
except glance_store.StorageFull as e:
msg = (_("Image storage media is full: %s") %
encodeutils.exception_to_unicode(e))
_send_notification(notify_error, 'image.upload', msg)
raise webob.exc.HTTPRequestEntityTooLarge(explanation=msg)
After doing this, the expected behavior will be:
stack@ubuntu16vmliang:~$ glance image-create --name img2-ceph --visibility
public --disk-format raw --container-format bare --progress --backend rbd
--file /opt/stack/data/glance/images/d4ca8259-168b-42f5-a719-40038362ae8c
>
/usr/local/lib/python2.7/dist-packages/glanceclient/v2/shell.py(555)do_image_upload()
-> backend = None
(Pdb) c
[=>] 100%
+--+--+
| Property | Value|
+--+--+
| checksum | None |
| container_format | bare |
| created_at | 2018-12-14T01:41:36Z |
| disk_format | raw |
| id | 8aefa92d-bd9c-4726-95ae-d8f698d7bc82 |
| min_disk | 0|
| min_ram | 0|
| name | img2-ceph|
| os_hash_algo | None
[Yahoo-eng-team] [Bug 1812550] Re: Image creation fails with "u'string' Failed validating u'type' in schema[u'additionalProperties']: {u'type': u'string'} On instance[u'os_hidden']: False"
Hi Dilip,
I doubt this issue is in openstack client and not in glance. I am sure
that openstack client is not upto date with the latest features/support
added in glance client.
In Rocky we have added a support to hide the image, at the time of
creation it will be false. Openstack client is not up-to-date with this
support and that's why it is failing.
Using glance image-create command I am able to create this image without
any issue.
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1812550
Title:
Image creation fails with "u'string' Failed validating u'type' in
schema[u'additionalProperties']: {u'type': u'string'} On
instance[u'os_hidden']: False"
Status in Glance:
Invalid
Bug description:
Hi all,
I am running on OpenStack Rocky(17.0.0). Image creation fails with the
following error
root@ctrl1:~# openstack image create \
> --disk-format=qcow2 \
> --container-format=bare \
> --file=Fedora-Atomic-27-20180212.2.x86_64.qcow2\
> --property os_distro='fedora-atomic' \
> fedora-atomic-latest
rating version 2 is not in supported versions: 1
False is not of type u'string'
Failed validating u'type' in schema[u'additionalProperties']:
{u'type': u'string'}
On instance[u'os_hidden']:
False
How can we solve this type conversion error ?
This seems to affect nova also
https://bugs.launchpad.net/nova/+bug/1806239
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1812550/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1805765] [NEW] Glance image conversion fails
Public bug reported:
It is not possible to convert glance images as it fails with error,
NoSuchOptError: no such option conversion_plugin_options in group
[DEFAULT].
Steps to reproduce:
Ensure 'image_conversion' plugin is enabled in glance-image-import.conf as
shown below:
[image_import_opts]
image_import_plugins = ['image_conversion']
[image_conversion]
output_format = raw
Run below command to create image:
$ glance image-create-via-import --disk-format qcow2 --container-format bare
--name cirros --import-method web-download --uri
http://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img
Expected result:
Image should be converted to raw format on the fly.
Actual result:
Conversion fails
Glance API logs:
2018-11-28 16:26:46.502 24 INFO eventlet.wsgi.server [-] 172.17.1.201 - -
[28/Nov/2018 16:26:46] "GET /healthcheck HTTP/1.0" 200 137 0.003688
2018-11-28 16:26:46.870 25 WARNING glance.async.taskflow_executor [-] Task
'api_image_import-Convert_Image-f8822a30-4980-451d-bbed-d73fd48736a8'
(ba9729e1-9069-40fd-a3fd-496072765936) transitioned into state 'FAILURE' from
state 'RUNNING'
5 predecessors (most recent first):
Flow 'api_image_import'
|__Atom
'api_image_import-ConfigureStaging-f8822a30-4980-451d-bbed-d73fd48736a8'
{'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {}, 'provides':
'file:///var/lib/glance/staging/7b317981-81a6-4839-8bc3-a138ddb4472d'}
|__Flow 'api_image_import'
|__Atom 'api_image_import_retry' {'intention': 'EXECUTE', 'state':
'SUCCESS', 'requires': {}, 'provides': [(None, {})]}
|__Flow 'api_image_import': NoSuchOptError: no such option
conversion_plugin_options in group [DEFAULT]
2018-11-28 16:26:46.870 25 ERROR glance.async.taskflow_executor Traceback (most
recent call last):
2018-11-28 16:26:46.870 25 ERROR glance.async.taskflow_executor File
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py",
line 53, in _execute_task
2018-11-28 16:26:46.870 25 ERROR glance.async.taskflow_executor result =
task.execute(**arguments)
2018-11-28 16:26:46.870 25 ERROR glance.async.taskflow_executor File
"/usr/lib/python2.7/site-packages/glance/async/flows/plugins/image_conversion.py",
line 78, in execute
2018-11-28 16:26:46.870 25 ERROR glance.async.taskflow_executor
target_format = CONF.conversion_plugin_options.output_format
2018-11-28 16:26:46.870 25 ERROR glance.async.taskflow_executor File
"/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2644, in __getattr__
2018-11-28 16:26:46.870 25 ERROR glance.async.taskflow_executor raise
NoSuchOptError(name)
2018-11-28 16:26:46.870 25 ERROR glance.async.taskflow_executor NoSuchOptError:
no such option conversion_plugin_options in group [DEFAULT]
** Affects: glance
Importance: High
Status: Confirmed
** Tags: rocky-backport-potential
** Changed in: glance
Status: New => Confirmed
** Changed in: glance
Importance: Undecided => High
** Tags added: rocky-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1805765
Title:
Glance image conversion fails
Status in Glance:
Confirmed
Bug description:
It is not possible to convert glance images as it fails with error,
NoSuchOptError: no such option conversion_plugin_options in group
[DEFAULT].
Steps to reproduce:
Ensure 'image_conversion' plugin is enabled in glance-image-import.conf as
shown below:
[image_import_opts]
image_import_plugins = ['image_conversion']
[image_conversion]
output_format = raw
Run below command to create image:
$ glance image-create-via-import --disk-format qcow2 --container-format bare
--name cirros --import-method web-download --uri
http://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img
Expected result:
Image should be converted to raw format on the fly.
Actual result:
Conversion fails
Glance API logs:
2018-11-28 16:26:46.502 24 INFO eventlet.wsgi.server [-] 172.17.1.201 - -
[28/Nov/2018 16:26:46] "GET /healthcheck HTTP/1.0" 200 137 0.003688
2018-11-28 16:26:46.870 25 WARNING glance.async.taskflow_executor [-] Task
'api_image_import-Convert_Image-f8822a30-4980-451d-bbed-d73fd48736a8'
(ba9729e1-9069-40fd-a3fd-496072765936) transitioned into state 'FAILURE' from
state 'RUNNING'
5 predecessors (most recent first):
Flow 'api_image_import'
|__Atom
'api_image_import-ConfigureStaging-f8822a30-4980-451d-bbed-d73fd48736a8'
{'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {}, 'provides':
'file:///var/lib/glance/staging/7b317981-81a6-4839-8bc3-a138ddb4472d'}
|__Flow 'api_image_import'
|__Atom 'api_image_import_retry' {'intention': 'EXECUTE', 'state':
'SUCCESS', 'requires': {}, 'provides': [(None, {})]}
|__Flow 'api_image_import': NoSuchOptError: no such option
conversion_plugin_options in group [DEFAULT]
[Yahoo-eng-team] [Bug 1783278] Re: https url for image import
** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1783278 Title: https url for image import Status in Glance: Invalid Bug description: task API in Glance is failing while using https URL for import location because of this: https://github.com/openstack/glance/blob/master/glance/common/scripts/utils.py#L141 while creating url connection, there is no way remote certificates can be used or ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1783278/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1795786] [NEW] glance-cache-manage need to be removed from documentation?
Public bug reported: When I try to run glance-cache-manage command it returns following error. glance-cache-manage --help Traceback (most recent call last): File "/usr/local/bin/glance-cache-manage", line 6, in from glance.cmd.cache_manage import main ImportError: No module named 'glance.cmd.cache_manage' This command is removed from the code base during v1 removal [1] but still present in documentation. [1] https://review.openstack.org/#/c/532503/10/glance/cmd/cache_manage.py ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1795786 Title: glance-cache-manage need to be removed from documentation? Status in Glance: New Bug description: When I try to run glance-cache-manage command it returns following error. glance-cache-manage --help Traceback (most recent call last): File "/usr/local/bin/glance-cache-manage", line 6, in from glance.cmd.cache_manage import main ImportError: No module named 'glance.cmd.cache_manage' This command is removed from the code base during v1 removal [1] but still present in documentation. [1] https://review.openstack.org/#/c/532503/10/glance/cmd/cache_manage.py To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1795786/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1794225] [NEW] Multiple backend support for scrubber and cache-prefetcher is missing
Public bug reported: In Rocky multiple backend support is added as an experimental API feature. As of now multiple backend works with glance-api but it is missing in glance-scrubber and glance-cache-prefetcher. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1794225 Title: Multiple backend support for scrubber and cache-prefetcher is missing Status in Glance: New Bug description: In Rocky multiple backend support is added as an experimental API feature. As of now multiple backend works with glance-api but it is missing in glance-scrubber and glance-cache-prefetcher. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1794225/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1793057] [NEW] Multiple backend related config options are not listed in sample conf file
Public bug reported: In Rocky we have added support for multiple backend as a EXPERIMENTAL feature. However configuration options related to multiple backend are not generated in sample config file due to some issue. We have added below 3 new config options for multiple backend. 1. enabled_backneds (added in glance) 2. default_backend (added in glance_store) 3. store_description (added in glance_store) To fix this we need to propose two different patches one in glance and another one is glance_store. Once glance_store patch is merged and new library version released and available in glance then all the above 3 config options will be added to newly generated sample config file. ** Affects: glance Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Affects: glance-store Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Also affects: glance-store Importance: Undecided Status: New ** Changed in: glance-store Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance Importance: Undecided => High ** Changed in: glance-store Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1793057 Title: Multiple backend related config options are not listed in sample conf file Status in Glance: New Status in glance_store: New Bug description: In Rocky we have added support for multiple backend as a EXPERIMENTAL feature. However configuration options related to multiple backend are not generated in sample config file due to some issue. We have added below 3 new config options for multiple backend. 1. enabled_backneds (added in glance) 2. default_backend (added in glance_store) 3. store_description (added in glance_store) To fix this we need to propose two different patches one in glance and another one is glance_store. Once glance_store patch is merged and new library version released and available in glance then all the above 3 config options will be added to newly generated sample config file. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1793057/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1789351] Re: Glance deployment with python3 + "keystone" paste_deploy flavor Fails
Fixed in keystonemiddleware. ** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1789351 Title: Glance deployment with python3 + "keystone" paste_deploy flavor Fails Status in Glance: Invalid Status in keystonemiddleware: In Progress Status in oslo.config: New Bug description: This happens with oslo.config >= 6.3.0([1]) + python3 + "keystone" paste_deploy + current glance(before https://review.openstack.org/#/c/532503/10/glance/common/store_utils.py@30 it works) Testing in devstack: https://review.openstack.org/#/c/596380/ The glance api service fails to start with below Error, reproducing here: https://review.openstack.org/#/c/596380/:- ERROR: dictionary changed size during iteration , see logs below Failure logs from job:- http://logs.openstack.org/80/596380/2/check /tempest-full- py3/514fa29/controller/logs/screen-g-api.txt.gz#_Aug_27_07_26_10_698243 The Runtime Error is returned at keystonemiddleware:- https://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token/__init__.py#L551 Adding code snippet here:- if self._conf.oslo_conf_obj != cfg.CONF: <-- Fails here oslo_cache.configure(self._conf.oslo_conf_obj) So with pdb found that an additional key(fatal_deprecations) was added to cfg.CONF at ^^, so Error is returned in python3. With python2 same key is added but no Error. There are multiple ways to avoid it, like use the paste_deploy configuration that works(ex: keystone+cachemanagement), use oslo.config <= 6.2.0, Use python2 or update glance(https://review.openstack.org/#/c/532503/10/glance/common/store_utils.py@30 as use_user_token is deprecated since long) with keystone+cachemanagement, all the config items were added before reaching the Failure point in keystonemiddleware and self._conf.oslo_conf_obj != cfg.CONF didn't raised an error and returned Boolean. Don't know why. But it seems a real issue to me as it may happen in python3 at different places. So it would be good if Teams from affected projects(oslo.config, keystonemiddleware, glance) can look at it and fix(not avoid) at the best place. To me it looks like keystonemiddleware is not handling(comparing the dict) it properly for python3, as the conf is dynamically updated(how ? and when ?). - so can oslo.config Team check if glance and keystonmiddleware are handling/using oslo.config properly. - i checked keystone+cachemanagement is default in devstack from last 6 years, is "keystone" flavor supported? if yes it should be fixed. Also it would be good to cleanup the deprecated options those are deprecated since Mitaka. - If it's wrongly used in keystonemiddleware/glance, it would be good to fix there. Initially detected while testing with Fedora[2], but later digged on why it's working in CI with Ubuntu and started [3]. [1] https://review.openstack.org/#/c/560094/ [2] https://review.rdoproject.org/r/#/c/14921/ [3] https://review.openstack.org/#/c/596380/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1789351/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1778645] [NEW] 500 response for incorrect node_staging_uri in glance-api.conf
Public bug reported: node_staging_uri configuration option needs a value which always starts with file:///. If by mistake operator sets value of node_staging_uri without file:/// then import api fails with 500 internal server error. Steps to reproduce: 1. set below value to node_staging_uri in glance.api.conf node_staging_uri = /opt/stack/data/glance/staging 2. Restart glance-api service 3. Import image using below command $ glance image-create-via-import --disk-format qcow2 --container-format bare --name test --import-method 'glance-direct' --file Expected output: Image should be imported successfully and should be in active state. Actual output: 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) Image remains in queued state. glance-api logs: Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data [None req-696e90ed-1592-4287-a84c-eeaa395852a8 admin admin] Failed to stage image data due to internal error: StoreAddDisabled: Configuration for store failed. Adding images to this store is disabled. Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data Traceback (most recent call last): Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data File "/opt/stack/glance/glance/api/v2/image_data.py", line 321, in stage Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data utils.CooperativeReader(data), CONF.image_size_cap), 0) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data File "/usr/local/lib/python2.7/dist-packages/glance_store/capabilities.py", line 223, in op_checker Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data raise op_exec_map[op](**kwargs) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data StoreAddDisabled: Configuration for store failed. Adding images to this store is disabled. Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi [None req-696e90ed-1592-4287-a84c-eeaa395852a8 admin admin] Caught error: Configuration for store failed. Adding images to this store is disabled.: StoreAddDisabled: Configuration for store failed. Adding images to this store is disabled. Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi Traceback (most recent call last): Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1274, in __call__ Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi request, **action_args) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/wsgi.py", line 1317, in dispatch Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi return method(*args, **kwargs) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/common/utils.py", line 417, in wrapped Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi return func(self, req, *args, **kwargs) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/api/v2/image_data.py", line 370, in stage Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi self._restore(image_repo, image) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi self.force_reraise() Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi six.reraise(self.type_, self.value, self.tb) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi File "/opt/stack/glance/glance/api/v2/image_data.py", line 321, in stage Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi utils.CooperativeReader(data), CONF.image_size_cap), 0) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi File "/usr/local/lib/python2.7/dist-packages/glance_store/capabilities.py", line 223, in op_checker Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi raise op_exec_map[op](**kwargs) Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi StoreAddDisabled: Configuration for store failed. Adding images to this store is disabled. Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi Jun 26 06:28:11 ubuntu-old glance-api[24600]: INFO eventlet.wsgi.server [None req-696e90ed-1592-4287-a84c-eeaa395852a8
[Yahoo-eng-team] [Bug 1775782] [NEW] glance-image-import.conf not parsed when running under wsgi
Public bug reported: When development environment is set to run under wsgi mode (by setting WSGI_MODE=mod_wsgi in local.conf) glance-image-import.conf file is not parsed. It is working properly if glance is running under uwsgi. Steps to reproduce: NOTE: Here I am trying to use plugin "inject_image_metadata" to inject metadata properties to the image. 1. Add glance-image-import.conf as mentioned at /etc/glance [image_import_opts] image_import_plugins = ["inject_image_metadata"] [inject_metadata_properties] inject = "property1":"value" ignore_user_roles = demo 2. Restart glance api service using "devstack@g-api.service" 3. Source using admin credentials (as we are ignoring demo role in glance-image-import.conf) $ source devstack/openrc admin admin 3. Create image using import api $ glance image-create-via-import --container-format bare --disk-format qcow2 --name ceph_image_default --file temp.qcow2 Expected Output: Properties mentioned in glance-image-import.conf should be injected to the image Actual Output: Properties are not injected as plugin is not loaded. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1775782 Title: glance-image-import.conf not parsed when running under wsgi Status in Glance: New Bug description: When development environment is set to run under wsgi mode (by setting WSGI_MODE=mod_wsgi in local.conf) glance-image-import.conf file is not parsed. It is working properly if glance is running under uwsgi. Steps to reproduce: NOTE: Here I am trying to use plugin "inject_image_metadata" to inject metadata properties to the image. 1. Add glance-image-import.conf as mentioned at /etc/glance [image_import_opts] image_import_plugins = ["inject_image_metadata"] [inject_metadata_properties] inject = "property1":"value" ignore_user_roles = demo 2. Restart glance api service using "devstack@g-api.service" 3. Source using admin credentials (as we are ignoring demo role in glance-image-import.conf) $ source devstack/openrc admin admin 3. Create image using import api $ glance image-create-via-import --container-format bare --disk-format qcow2 --name ceph_image_default --file temp.qcow2 Expected Output: Properties mentioned in glance-image-import.conf should be injected to the image Actual Output: Properties are not injected as plugin is not loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1775782/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1770325] [NEW] Remove glance-direct from enabled_import_methods config option
Public bug reported: Glance added the support for interoperable image imports. Image uploads are done using a two-step approach: first uploading it to the Glance API using a local staging area, and then triggering an upload from the staging area to the storage backend. In the case of an HA setup (ie with 3 controller nodes) this requires a shared consistent filesystem across the controller nodes. Otherwise it might happen that the image is uploaded to one node, and triggering the import is executed on a different node - where the image does not exist. Therefore we need to remove 'glance-direct' from the default, thus operators need to enable it explicitly if they have a shared filesystem across the controller nodes (for example using NFS). ** Affects: glance Importance: Undecided Assignee: Abhishek Kekane (abhishek-kekane) Status: New ** Changed in: glance Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1770325 Title: Remove glance-direct from enabled_import_methods config option Status in Glance: New Bug description: Glance added the support for interoperable image imports. Image uploads are done using a two-step approach: first uploading it to the Glance API using a local staging area, and then triggering an upload from the staging area to the storage backend. In the case of an HA setup (ie with 3 controller nodes) this requires a shared consistent filesystem across the controller nodes. Otherwise it might happen that the image is uploaded to one node, and triggering the import is executed on a different node - where the image does not exist. Therefore we need to remove 'glance-direct' from the default, thus operators need to enable it explicitly if they have a shared filesystem across the controller nodes (for example using NFS). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1770325/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1331913] Re: tempest.api.volume.test_volumes_actions.VolumesActionsTestXML.test_volume_upload fails
Looks like not related to glance and never occurred again as well. ** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1331913 Title: tempest.api.volume.test_volumes_actions.VolumesActionsTestXML.test_volume_upload fails Status in Glance: Invalid Status in tempest: Invalid Bug description: See: http://logs.openstack.org/07/81707/7/check/check-tempest-dsvm- full/8b1ee80/console.html 2014-06-19 03:37:29.394 | tempest.api.volume.test_volumes_actions.VolumesActionsTestXML.test_volume_upload[gate,image] 2014-06-19 03:37:29.394 | 2014-06-19 03:37:29.395 | 2014-06-19 03:37:29.395 | Captured traceback: 2014-06-19 03:37:29.395 | ~~~ 2014-06-19 03:37:29.395 | Traceback (most recent call last): 2014-06-19 03:37:29.395 | File "tempest/test.py", line 126, in wrapper 2014-06-19 03:37:29.395 | return f(self, *func_args, **func_kwargs) 2014-06-19 03:37:29.395 | File "tempest/api/volume/test_volumes_actions.py", line 107, in test_volume_upload 2014-06-19 03:37:29.395 | self.image_client.wait_for_image_status(image_id, 'active') 2014-06-19 03:37:29.395 | File "tempest/services/image/v1/json/image_client.py", line 289, in wait_for_image_status 2014-06-19 03:37:29.395 | status=status) 2014-06-19 03:37:29.395 | ImageKilledException: Image ecd98deb-ca3d-4207-b6c9-49ae6434e765 'killed' while waiting for 'active' To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1331913/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1338567] Re: delete the image using v2 api when we upload a image using v1 api, glance don't delete the image data after finishing the uploading.
V1 is deprecated and will be removed in Rocky also as per comments it looks like it is not reproducible any more. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1338567 Title: delete the image using v2 api when we upload a image using v1 api, glance don't delete the image data after finishing the uploading. Status in Glance: Won't Fix Bug description: First, I use glance cli to upload a image glance image-create --name myimage --disk-format=raw --container-format=bare --file /path/to/file.img At the same time, I use the v2 api to delete the image curl -i -X DELETE -H 'X-Auth-Token: $TOKNE_ID' -H 'Content-Type: application/json' http://localhost:9292/v2/images/$IMAGE_ID. After the uploading is finished, the response shows that the image status is active and the image is deleted. The image data that has been uploaded has not been removed from glance store backend. The right response should be "Image could not be found after upload. The image may have been deleted during the upload." as we see when we upload image using v1 api and delete using v1 api or we upload image using v2 api and delete using v2 api. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1338567/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1327775] Re: tempest.api.compute.images.test_images_oneserver.ImagesOneServerTestXML.test_create_delete_image timed out
Looks like not related to glance. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1327775 Title: tempest.api.compute.images.test_images_oneserver.ImagesOneServerTestXML.test_create_delete_image timed out Status in Glance: Won't Fix Status in OpenStack Object Storage (swift): Invalid Bug description: http://logs.openstack.org/44/98044/1/gate/gate-tempest-dsvm- neutron/525dcba/ 2014-06-08 00:45:51.509 | Captured traceback-1: 2014-06-08 00:45:51.509 | ~ 2014-06-08 00:45:51.509 | Traceback (most recent call last): 2014-06-08 00:45:51.509 | File "tempest/api/compute/images/test_images_oneserver.py", line 31, in tearDown 2014-06-08 00:45:51.510 | self.server_check_teardown() 2014-06-08 00:45:51.510 | File "tempest/api/compute/base.py", line 161, in server_check_teardown 2014-06-08 00:45:51.510 | 'ACTIVE') 2014-06-08 00:45:51.510 | File "tempest/services/compute/xml/servers_client.py", line 388, in wait_for_server_status 2014-06-08 00:45:51.510 | raise_on_error=raise_on_error) 2014-06-08 00:45:51.510 | File "tempest/common/waiters.py", line 93, in wait_for_server_status 2014-06-08 00:45:51.510 | raise exceptions.TimeoutException(message) 2014-06-08 00:45:51.510 | TimeoutException: Request timed out 2014-06-08 00:45:51.510 | Details: (ImagesOneServerTestXML:tearDown) Server 72897dd4-cd42-4e0b-af15-3eec5b677d0b failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: ACTIVE. Current task state: image_snapshot. 2014-06-08 00:45:51.510 | 2014-06-08 00:45:51.510 | 2014-06-08 00:45:51.511 | Captured traceback: 2014-06-08 00:45:51.511 | ~~~ 2014-06-08 00:45:51.511 | Traceback (most recent call last): 2014-06-08 00:45:51.511 | File "tempest/api/compute/images/test_images_oneserver.py", line 77, in test_create_delete_image 2014-06-08 00:45:51.511 | self.client.wait_for_image_status(image_id, 'ACTIVE') 2014-06-08 00:45:51.511 | File "tempest/services/compute/xml/images_client.py", line 140, in wait_for_image_status 2014-06-08 00:45:51.511 | waiters.wait_for_image_status(self, image_id, status) 2014-06-08 00:45:51.511 | File "tempest/common/waiters.py", line 129, in wait_for_image_status 2014-06-08 00:45:51.511 | raise exceptions.TimeoutException(message) 2014-06-08 00:45:51.511 | TimeoutException: Request timed out 2014-06-08 00:45:51.511 | Details: (ImagesOneServerTestXML:test_create_delete_image) Image fbe2b95d-7126-444d-be5a-e4104ec7d799 failed to reach ACTIVE status within the required time (196 s). Current status: SAVING. logstash query: http://logstash.openstack.org/#eyJzZWFyY2giOiJmaWxlbmFtZTpcImNvbnNvbGUuaHRtbFwiIEFORCBtZXNzYWdlOlwiRGV0YWlsczogKEltYWdlc09uZVNlcnZlclRlc3RYTUw6dGVzdF9jcmVhdGVfZGVsZXRlX2ltYWdlKSBJbWFnZVwiIEFORCBtZXNzYWdlOlwiIGZhaWxlZCB0byByZWFjaCBBQ1RJVkUgc3RhdHVzIHdpdGhpbiB0aGUgcmVxdWlyZWQgdGltZSAoMTk2IHMpLiBDdXJyZW50IHN0YXR1czogU0FWSU5HLlwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDAyMjMzOTQwMjA1fQ== To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1327775/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1325425] Re: Serverfault on API tests
Pretty old and not encountered again by anyone else. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1325425 Title: Serverfault on API tests Status in Glance: Won't Fix Status in tempest: Invalid Bug description: One of the test runs failed in several unrelated categories to the tested patch with an error like the one below: ft15.1: setUpClass (tempest.api.compute.v3.servers.test_server_addresses.ServerAddressesV3Test)_StringException: Traceback (most recent call last): File "tempest/api/compute/v3/servers/test_server_addresses.py", line 32, in setUpClass resp, cls.server = cls.create_test_server(wait_until='ACTIVE') File "tempest/api/compute/base.py", line 247, in create_test_server raise ex ServerFault: Got server fault Details: The server has either erred or is incapable of performing the requested operation. Full test results: http://logs.openstack.org/57/96957/1/check/check-grenade-dsvm-neutron/e15aebd/logs/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1325425/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
