[Yahoo-eng-team] [Bug 2008116] Re: In train, current version is 2.1 instead of 2.10
Stable Train does not have API v.2.10. this is RH Downstream product
related issue. Not really a bug.
** Changed in: glance
Importance: Undecided => Wishlist
** Changed in: glance
Status: In Progress => 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/2008116
Title:
In train, current version is 2.1 instead of 2.10
Status in Glance:
Invalid
Bug description:
In train, current version is 2.1 instead of 2.10:
(undercloud) [stack@undercloud-0 ~]$ curl http://10.10.10.10:9292 | jq .
{
"versions": [
{
"id": "v2.1",
"status": "CURRENT",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.9",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.8",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.7",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.6",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.5",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.4",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.3",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.2",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.1",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
},
{
"id": "v2.0",
"status": "SUPPORTED",
"links": [
{
"rel": "self",
"href": "http://10.10.10.10:9292/v2/;
}
]
}
]
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/2008116/+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 1978869] Re: bindep: SUSE & dpkg-based platforms require some fixes
** Also affects: glance/zed Importance: Undecided Assignee: Cyril Roelandt (cyril-roelandt) Status: In Progress ** Also affects: glance/xena Importance: Undecided Status: New ** Also affects: glance/yoga 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/1978869 Title: bindep: SUSE & dpkg-based platforms require some fixes 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: tl;dr: - On OpenSUSE Tumbleweed, pg_config is provided by postgresql-server-devel - On OpenSUSE Tumbleweed, qemu-img is provided by qemu-tools (not qemu-img) Details: On Tumbleweed, I ran the following commands: $ tox -ebindep ... Missing packages: gcc libffi48-devel libmysqlclient-devel mariadb postgresql postgresql-devel postgresql-server python3-devel qemu-img ... $ sudo zypper install gcc libffi48-devel libmysqlclient-devel mariadb postgresql postgresql-devel postgresql-server python3-devel qemu-img $ tox -epy3 ... Collecting psycopg2>=2.8.4 Using cached psycopg2-2.9.3.tar.gz (380 kB) Preparing metadata (setup.py): started Preparing metadata (setup.py): finished with status 'error' error: subprocess-exited-with-error × python setup.py egg_info did not run successfully. │ exit code: 1 ╰─> [25 lines of output] running egg_info creating /tmp/pip-pip-egg-info-rk_ofq01/psycopg2.egg-info writing /tmp/pip-pip-egg-info-rk_ofq01/psycopg2.egg-info/PKG-INFO writing dependency_links to /tmp/pip-pip-egg-info-rk_ofq01/psycopg2.egg-info/dependency_links.txt writing top-level names to /tmp/pip-pip-egg-info-rk_ofq01/psycopg2.egg-info/top_level.txt writing manifest file '/tmp/pip-pip-egg-info-rk_ofq01/psycopg2.egg-info/SOURCES.txt' /home/vagrant/glance/.tox/py3/lib/python3.8/site-packages/setuptools/config/setupcfg.py:458: DeprecationWarning: The license_file parameter is dep recated, use license_files instead. warnings.warn(msg, warning_class) Error: pg_config executable not found. ... $ sudo zypper install postgresql-server-devel # Now pg_config is available $ which qemu-img which: no qemu-img in (/home/vagrant/glance/.tox/py3/bin:/home/vagrant/bin:/usr/local/bin:/usr/bin:/bin) # Installing qemu-tools made qemu-img available. I still could not run "tox -epy3" successfully because of issues with stestr on this OS, but it's pretty clear that bindep.txt should be fixed for OpenSUSE. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1978869/+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 1972666] [NEW] Configgen does not pick up all groups from wsgi.py
Public bug reported: 'cli_opts' and 'cache_opts' from glance/common/wsgi.py are not picked up by the configgen nor listed through the functions in glance/opts.py. ** Affects: glance Importance: Medium Status: Triaged ** Affects: glance/wallaby Importance: Undecided Status: New ** Affects: glance/xena Importance: Undecided Status: New ** Affects: glance/yoga Importance: Undecided Status: New ** Affects: glance/zed Importance: Medium Status: Triaged ** Tags: low-hanging-fruit ** Also affects: glance/zed Importance: Medium Status: Triaged ** Also affects: glance/yoga Importance: Undecided Status: New ** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/xena 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/1972666 Title: Configgen does not pick up all groups from wsgi.py Status in Glance: Triaged Status in Glance wallaby series: New Status in Glance xena series: New Status in Glance yoga series: New Status in Glance zed series: Triaged Bug description: 'cli_opts' and 'cache_opts' from glance/common/wsgi.py are not picked up by the configgen nor listed through the functions in glance/opts.py. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1972666/+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 1947146] Re: 'qemu-img: command not found' when testing on Centos
** Also affects: glance/wallaby
Importance: Undecided
Status: New
** Also affects: glance/xena
Importance: Undecided
Status: New
** Also affects: glance/yoga
Importance: Undecided
Assignee: Andre Aranha (afariasa)
Status: In Progress
** Also affects: glance/victoria
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/1947146
Title:
'qemu-img: command not found' when testing on Centos
Status in Glance:
In Progress
Status in Glance victoria series:
New
Status in Glance wallaby series:
New
Status in Glance xena series:
New
Status in Glance yoga series:
In Progress
Bug description:
While running the tests for Glance on Centos, the 'qemu-img' is failing due
to missing qemu-img command[1]:
~~~
/bin/sh: qemu-img: command not found
{4}
glance.tests.functional.test_healthcheck_middleware.HealthcheckMiddlewareTest.test_healthcheck_enabled
[6.082316s] ... ok
{2}
glance.tests.functional.v2.test_images.TestImages.test_owning_tenant_can_communitize_image
[5.017702s] ... ok
{7}
glance.tests.functional.test_cache_middleware.TestImageCacheSqlite.test_partial_download_of_cached_images_v2_api
[6.331016s] ... ok
{7}
glance.tests.functional.test_client_redirects.TestClientRedirects.test_redirect_to_new_host
[0.033611s] ... ok
{6} glance.tests.functional.test_logging.TestLogging.test_no_debug
[6.030891s] ... ok
{6} glance.tests.functional.test_sqlite.TestSqlite.test_big_int_mapping ...
SKIPPED: test requires exe: sqlite3
{5}
glance.tests.functional.v2.test_images.TestImageDirectURLVisibility.test_image_direct_url_visible
[3.947811s] ... ok
{3}
glance.tests.functional.v2.test_images.TestImages.test_image_import_qcow_virtual_size_calculation
[5.023139s] ... FAILED
Captured traceback:
~~~
Traceback (most recent call last):
File
"/home/zuul/src/opendev.org/openstack/glance/glance/tests/functional/v2/test_images.py",
line 959, in test_image_import_qcow_virtual_size_calculation
fn = self._create_qcow(128 * units.Mi)
File
"/home/zuul/src/opendev.org/openstack/glance/glance/tests/functional/v2/test_images.py",
line 911, in _create_qcow
shell=True)
File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output
**kwargs).stdout
File "/usr/lib64/python3.6/subprocess.py", line 438, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'qemu-img create -f qcow2
/tmp/glance-unittest-images-05gx9_p1.qcow2 134217728' returned non-zero exit
status 127.
~~~
We need to add qemu-img on the bindep.txt to have it working on
Centos.
[1]
https://zuul.opendev.org/t/openstack/build/b1e5959024d34af795912478ac9809ff/console
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1947146/+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] Re: Bump oslo.policy minimum version to 3.8.1
** Also affects: glance/yoga Importance: Undecided Status: In Progress ** Also affects: glance/xena Importance: Undecided Status: New ** Changed in: glance/xena Milestone: None => xena-rc2 ** Changed in: glance/yoga Milestone: None => yoga-1 -- 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] Re: Glance fails to build with oslo.log 4.4.0 for Debian platform
** Also affects: glance/xena Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: In Progress ** Changed in: glance/xena Importance: High => 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/1943985 Title: Glance fails to build with oslo.log 4.4.0 for Debian platform Status in Glance: In Progress Status in Glance xena series: In Progress Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1943985/+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
Any idea if this reaches further back than Wallaby? ** Also affects: glance/xena Importance: High Assignee: Dan Smith (danms) Status: Fix Released ** Also affects: glance/wallaby 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/1922928 Title: Image tasks API excludes in-progress tasks Status in Glance: Fix Released Status in Glance wallaby series: New Status in Glance xena series: 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 1943264] [NEW] Configuring doc refers to "image_formats"
Public bug reported: The correct config section is "image_format". ** Affects: glance Importance: Medium Assignee: Adrien Cunin (adri2000) Status: In Progress ** Affects: glance/ussuri Importance: Undecided Status: New ** Affects: glance/victoria Importance: Undecided Status: New ** Affects: glance/wallaby Importance: Undecided Status: New ** Affects: glance/xena Importance: Medium Assignee: Adrien Cunin (adri2000) Status: In Progress ** Tags: documentation ** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/xena Importance: Medium Assignee: Adrien Cunin (adri2000) Status: In Progress ** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria 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/1943264 Title: Configuring doc refers to "image_formats" Status in Glance: In Progress Status in Glance ussuri series: New Status in Glance victoria series: New Status in Glance wallaby series: New Status in Glance xena series: In Progress Bug description: The correct config section is "image_format". To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1943264/+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 1939555] [NEW] Cache management allows queueing non-existing image-IDs
Public bug reported: Glance's cache management commands allows adding non-existing image-IDs into the queue for prefetching. As these IDs don't exists the prefetcher cannot process them and they will be just sitting in the queue until manually cleaned out wasting time and resources. ** Affects: glance Importance: High Assignee: Erno Kuvaja (jokke) 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/1939555 Title: Cache management allows queueing non-existing image-IDs Status in Glance: In Progress Bug description: Glance's cache management commands allows adding non-existing image- IDs into the queue for prefetching. As these IDs don't exists the prefetcher cannot process them and they will be just sitting in the queue until manually cleaned out wasting time and resources. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1939555/+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 1938265] Re: Nova snapshot fail with multiple rbd stores
** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria Importance: Undecided Status: New ** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/xena 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/1938265 Title: Nova snapshot fail with multiple rbd stores Status in Glance: New Status in Glance ussuri series: New Status in Glance victoria series: New Status in Glance wallaby series: New Status in Glance xena series: New Bug description: As of now, with multi store enabled, adding a new location to an image will make the add_location API call to fail if the store metadata is missing: Code in glance: https://github.com/openstack/glance/blob/master/glance/location.py#L134 Then in glance_store: https://github.com/openstack/glance_store/blob/master/glance_store/location.py#L111 This will raise a "KeyError: None" and raise a very standard "Invalid Location" 400 error when adding a new location. Point is, with a rbd backend, nova never specify this metadata when creating the image during the direct snapshot process (flatten the image directly in ceph image pool + adding the location directly in glance), so snapshot will always fail. A solution can be to infer the backend from the location uri, like we do during the store metadata lazy population. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1938265/+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 1930597] Re: Doc for "Configuring SSL Support" outdated in glance
Thanks Jean! I noticed this today too and filed a bug tracking it as I missed yours. ** Changed in: glance Status: New => Triaged ** Changed in: glance Importance: Undecided => High ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria Importance: Undecided Status: New ** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/xena Importance: High Assignee: Erno Kuvaja (jokke) Status: Triaged ** Changed in: glance/wallaby Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/victoria Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/ussuri Assignee: (unassigned) => Erno Kuvaja (jokke) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1930597 Title: Doc for "Configuring SSL Support" outdated in glance Status in Glance: In Progress Status in Glance ussuri series: Triaged Status in Glance victoria series: Triaged Status in Glance wallaby series: Triaged Status in Glance xena series: In Progress Bug description: The "Configuring SSL Support" states that `cert_file`, `key_file` and `ca_file` can be set to enable TLS. But on the [changelog of Ussuri](https://docs.openstack.org/releasenotes/glance/ussuri.html) it is mentioned that: > If upgrade is conducted from PY27 where ssl connections has been terminated into glance-api, the termination needs to happen externally from now on. So the `cert_file`, `key_file` and `ca_file` configuration options should be removed from the documentation. --- Release: 22.0.0.0rc2.dev2 on 2020-05-24 10:41:41 SHA: b5437773b20db3d6ef20d449a8a43171c8fc7f69 Source: https://opendev.org/openstack/glance/src/doc/source/configuration/configuring.rst URL: https://docs.openstack.org/glance/wallaby/configuration/configuring.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1930597/+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 1938441] Re: Configuring docs are still referring to ssl cert options
** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/xena Importance: Undecided Status: New ** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria Importance: High Assignee: Erno Kuvaja (jokke) Status: In Progress ** Changed in: glance/wallaby Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/xena Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/ussuri Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/wallaby Importance: Undecided => High ** Changed in: glance/xena Importance: Undecided => High ** Changed in: glance/ussuri 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/1938441 Title: Configuring docs are still referring to ssl cert options Status in Glance: In Progress Status in Glance ussuri series: New Status in Glance victoria series: In Progress Status in Glance wallaby series: New Status in Glance xena series: New Bug description: glance-api does not have native ssl since we moved to PY3, yet the configuring documentation still refers to the config options and indicates that ssl termination to the service would be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1938441/+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 1938441] [NEW] Configuring docs are still referring to ssl cert options
Public bug reported: glance-api does not have native ssl since we moved to PY3, yet the configuring documentation still refers to the config options and indicates that ssl termination to the service would be supported. ** Affects: glance Importance: High Assignee: Erno Kuvaja (jokke) Status: In Progress ** Tags: docs -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1938441 Title: Configuring docs are still referring to ssl cert options Status in Glance: In Progress Bug description: glance-api does not have native ssl since we moved to PY3, yet the configuring documentation still refers to the config options and indicates that ssl termination to the service would be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1938441/+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 1926404] Re: HTTP 413 : Failed to add object to Swift. Got error from Swift
** Changed in: glance Status: New => Triaged ** Changed in: glance Importance: Undecided => High ** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/victoria Importance: High Status: Triaged ** Also affects: glance/xena Importance: Undecided Status: New ** Changed in: glance/wallaby Status: New => Triaged ** Changed in: glance/xena Status: New => Triaged ** Changed in: glance/wallaby Importance: Undecided => High ** Changed in: glance/xena Importance: Undecided => High ** Changed in: glance/victoria Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/wallaby Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/xena Assignee: (unassigned) => Erno Kuvaja (jokke) ** No longer affects: glance/victoria ** No longer affects: glance/wallaby ** No longer affects: glance/xena ** Project changed: glance => glance-store ** Also affects: glance-store/victoria Importance: High Assignee: Erno Kuvaja (jokke) Status: Triaged ** Also affects: glance-store/wallaby Importance: Undecided Status: New ** Also affects: glance-store/xena Importance: Undecided Status: New ** Changed in: glance-store/wallaby Status: New => Triaged ** Changed in: glance-store/xena Status: New => Triaged ** Changed in: glance-store/wallaby Importance: Undecided => High ** Changed in: glance-store/xena Importance: Undecided => High ** Changed in: glance-store/wallaby Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance-store/xena Assignee: (unassigned) => Erno Kuvaja (jokke) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1926404 Title: HTTP 413 : Failed to add object to Swift. Got error from Swift Status in glance_store: In Progress Status in glance_store victoria series: In Progress Status in glance_store wallaby series: Triaged Status in glance_store xena series: Triaged Bug description: Hi, Openstack Glance Version : Victoria Openstack Swift Version : Victoria During image_upload, the HTTP 413 error is generated in glance-api logs if swift quota is full and hence the entire image_upload fails and delete operation is triggered : Caught error: Failed to add object to Swift. Got error from Swift: Object PUT failed: https://objectstore-3.xxx:443/v1/AUTH_22a2e2dfd8dd4156ba5c945bed320f50/glance_6a5e5cae-180c-42ca-ad0f-b459cb8ad8f7/6a5e5cae-180c-42ca-ad0f-b459cb8ad8f7-00118 413 Request Entity Too Large b'Upload exceeds quota.'. BackendException Failed to add object to Swift. Got error from Swift: Object PUT failed: https://objectstore-3.xxx:443/v1/AUTH_22a2e2dfd8dd4156ba5c945bed320f50/glance_6a5e5cae-180c-42ca-ad0f-b459cb8ad8f7/6a5e5cae-180c-42ca-ad0f-b459cb8ad8f7-00118 413 Request Entity Too Large b'Upload exceeds quota.'. Unfortunately the user receives : The error message is :HttpException: 500: Server Error for url: https://image-3.xxx/v2/images/6a5e5cae-180c-42ca-ad0f- b459cb8ad8f7/file, Internal Server Error The swift error is generated from : https://github.com/openstack/python- swiftclient/blob/master/swiftclient/client.py#L1491-L1492 To manage notifications about this bug go to: https://bugs.launchpad.net/glance-store/+bug/1926404/+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 1885928] Re: Unable to spawn VM from community image
** Changed in: glance Status: New => Triaged ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Also affects: glance/victoria Importance: Undecided Assignee: Erno Kuvaja (jokke) Status: Triaged ** Also affects: glance/xena Importance: Undecided Status: New ** Also affects: glance/wallaby Importance: Undecided Status: New ** Also affects: glance/ussuri Importance: Undecided Status: New ** Changed in: glance/xena Status: New => Triaged ** Changed in: glance/wallaby Status: New => Triaged ** Changed in: glance/ussuri Status: New => Triaged ** Changed in: glance/xena Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/wallaby Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/ussuri Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/xena Importance: Undecided => High ** Changed in: glance/wallaby Importance: Undecided => High ** Changed in: glance/victoria Importance: Undecided => High ** Changed in: glance/ussuri 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/1885928 Title: Unable to spawn VM from community image Status in Glance: Triaged Status in Glance ussuri series: Triaged Status in Glance victoria series: Triaged Status in Glance wallaby series: Triaged Status in Glance xena series: Triaged Bug description: Hi, I am planning to introduce community images in my production. Release : Train Backend : Swift I can spawn images from Public, private and shared images. The logs point me to HTTP 403 from swift : 2020-06-30T11:16:03.522021578+00:00 - api - 2020-06-30 11:16:03,093.093 42 WARNING glance.location [req-4d5aede4-0d3a-4dd7-bc2b-055de4f60dbc 3eda6592ccadd54d787c8d58c2c7c3e7ba0236ddb339c08eba531b056ae9e50e 606094098b04421b8041ef54c734b664 - 41aac04ce58c428b9ed2262798d0d336 41aac04ce58c428b9ed2262798d0d336] Get image b833841e-f92a-4495-8e8e-bfc6f68f9f31 data failed: Object GET failed: https:// :443/v1/AUTH_51edc18acfca49099e77dc66e8dc2f48/glance_b833841e-f92a-4495-8e8e-bfc6f68f9f31/b833841e-f92a-4495-8e8e-bfc6f68f9f31 403 Forbidden [first 60 chars of response] b'ForbiddenAccess was denied to this resourc'.: swiftclient.exceptions.ClientException: Object GET failed: https://:443/v1/AUTH_51edc18acfca49099e77dc66e8dc2f48/glance_b833841e-f92a-4495-8e8e-bfc6f68f9f31/b 833841e-f92a-4495-8e8e-bfc6f68f9f31 403 Forbidden [first 60 chars of response] b'ForbiddenAccess was denied to this resourc' 2020-06-30T11:16:03.522032543+00:00 - api - 2020-06-30 11:16:03,093.093 42 ERROR glance.location [req-4d5aede4-0d3a-4dd7-bc2b-055de4f60dbc 3eda6592ccadd54d787c8d58c2c7c3e7ba0236ddb339c08eba531b056ae9e50e 606094098b04421b8041ef54c734b664 - 41aac04ce58c428b9ed2262798d0d336 41aac04ce58c428b9ed2262798d0d336] Glance tried all active locations/stores to get data for image b833841e-f92a-4495-8e8e-bfc6f68f9f31 but all have failed I did refer all the available documents : https://specs.openstack.org/openstack/glance-specs/specs/ocata/implemented/glance/community_visibility.html https://blueprints.launchpad.net/glance/+spec/community-level-v2-image-sharing https://wiki.openstack.org/wiki/Glance-v2-community-image-sharing#Accepting_a_.27Community.27_Image, Is this issue related to ACL's ? https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/swift/store.py#L1524 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1885928/+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 1916052] Re: Unable to create trust errors in glance-api
** Also affects: glance/wallaby Importance: Undecided Status: New ** Changed in: glance/victoria Status: Fix Released => In Progress ** Changed in: glance/wallaby Status: New => In Progress ** Changed in: glance/wallaby Importance: Undecided => High ** Also affects: glance/xena Importance: Undecided Status: New ** Changed in: glance/xena Status: New => Fix Committed ** Changed in: glance/xena Importance: Undecided => High ** Changed in: glance/wallaby Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/xena Assignee: (unassigned) => Erno Kuvaja (jokke) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1916052 Title: Unable to create trust errors in glance-api Status in Glance: In Progress Status in Glance ussuri series: In Progress Status in Glance victoria series: In Progress Status in Glance wallaby series: In Progress Status in Glance xena series: Fix Committed Bug description: Hi, I enabled swift_store_expire_soon_interval = 1800 for images taking long time to complete the upload, but it doesnt seem to work as planned, i see a trust issue (based on docu, this is True by default) but i see the below in the glance-api logs : 021-02-18 14:04:52,948.948 30 INFO glance.api.v2.image_data [req- bb9660d8-c24c-4350-9d4e-7cfaffebf8d9 332d21d621e27dd887ff1f3388312be975597e42b755eec00ceff70d033228b8 97bf741678d44e8da33c43f4c4662ade - ec213443e8834473b579f7bea9e8c194 ec213443e8834473b579f7bea9e8c194] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token 2021-02-18 12:02:43,166.166 33 INFO glance.api.v2.image_data [req- 8a48bfa1-9d37-4095-8f7f-70438d4daff6 a10475412aa34d05a815fac977df8620 caa6209d2c38450f8266311fd0f05446 - default 582d6603e91d4d3d8193fa9160a599f0] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. http://paste.openstack.org/show/802787/ Ref : https://bugs.launchpad.net/keystone/+bug/1775140 https://review.opendev.org/c/openstack/glance/+/479047 Glance Version : Victoria Release, 21.0.0 Glance_Store Version : 2.3.0 Swift Version (Backend) : Victoria (i have enabled multi-tenant) Keystone : Train Please let me know if further information is required. Regards, Rajiv To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1916052/+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 1934673] [NEW] Policy deprecations falsely claims defaulting to role based policies.
Public bug reported: The deprecation message is "The image API now supports and default roles" whis is not true. We support roles, we do not default to them. ** Affects: glance Importance: High Assignee: Erno Kuvaja (jokke) Status: In Progress ** Affects: glance/wallaby Importance: High Assignee: Erno Kuvaja (jokke) Status: New ** Also affects: glance/wallaby Importance: Undecided Status: New ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/wallaby Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance Importance: Undecided => High ** Changed in: glance/wallaby 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/1934673 Title: Policy deprecations falsely claims defaulting to role based policies. Status in Glance: In Progress Status in Glance wallaby series: New Bug description: The deprecation message is "The image API now supports and default roles" whis is not true. We support roles, we do not default to them. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1934673/+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 1916052] Re: Unable to create trust errors in glance-api
** Changed in: glance Status: Incomplete => Triaged ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance Importance: Undecided => High ** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria Importance: High Assignee: Erno Kuvaja (jokke) Status: Triaged ** Changed in: glance/ussuri Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/ussuri Status: New => Triaged ** Changed in: glance/ussuri 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/1916052 Title: Unable to create trust errors in glance-api Status in Glance: In Progress Status in Glance ussuri series: Triaged Status in Glance victoria series: In Progress Bug description: Hi, I enabled swift_store_expire_soon_interval = 1800 for images taking long time to complete the upload, but it doesnt seem to work as planned, i see a trust issue (based on docu, this is True by default) but i see the below in the glance-api logs : 021-02-18 14:04:52,948.948 30 INFO glance.api.v2.image_data [req- bb9660d8-c24c-4350-9d4e-7cfaffebf8d9 332d21d621e27dd887ff1f3388312be975597e42b755eec00ceff70d033228b8 97bf741678d44e8da33c43f4c4662ade - ec213443e8834473b579f7bea9e8c194 ec213443e8834473b579f7bea9e8c194] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token 2021-02-18 12:02:43,166.166 33 INFO glance.api.v2.image_data [req- 8a48bfa1-9d37-4095-8f7f-70438d4daff6 a10475412aa34d05a815fac977df8620 caa6209d2c38450f8266311fd0f05446 - default 582d6603e91d4d3d8193fa9160a599f0] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. http://paste.openstack.org/show/802787/ Ref : https://bugs.launchpad.net/keystone/+bug/1775140 https://review.opendev.org/c/openstack/glance/+/479047 Glance Version : Victoria Release, 21.0.0 Glance_Store Version : 2.3.0 Swift Version (Backend) : Victoria (i have enabled multi-tenant) Keystone : Train Please let me know if further information is required. Regards, Rajiv To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1916052/+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 1799588] Re: default paste_deploy.flavor is none, but config file text implies it is 'keystone' (was: non-admin users can see all tenants' images even when image is private)
The fix for this was released back in 2018 it seems. Closing the bug. ** 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/1799588 Title: default paste_deploy.flavor is none, but config file text implies it is 'keystone' (was: non-admin users can see all tenants' images even when image is private) Status in Glance: Fix Released Status in OpenStack Security Advisory: Incomplete Bug description: [root@vm013 glance]# cat /etc/redhat-release CentOS Linux release 7.5.1804 (Core) [root@vm013 glance]# rpm -qa |grep glance |sort openstack-glance-16.0.1-1.el7.noarch openstack-glance-doc-16.0.1-1.el7.noarch python2-glanceclient-2.10.0-1.el7.noarch python2-glance-store-0.23.0-1.el7.noarch python-glance-16.0.1-1.el7.noarch python-glanceclient-doc-2.10.0-1.el7.noarch [root@vm013 glance]# md5sum /etc/glance/policy.json a4f29d0f75bbc04f1d83a1abdf0fda6f /etc/glance/policy.json I am running only Glance v2 API. In this demo, as an un-privileged user, I will list all glance images, from all tenants, and they are all marked 'private'. (as admin): [root@vm013 ~]# openstack role assignment list --effective --names |grep jonathan | user| jonathan@Default| | ozoneaq@ndc| | False | (as jonathan): [root@vm013 ~]# . keystonerc_jonathan [root@vm013 ~]# printenv |grep OS_ |sort OS_AUTH_URL=https://keystone.gpcprod:5000/v3 OS_CACERT=/etc/openldap/cacerts/gpcprod_root_ca.pem OS_IDENTITY_API_VERSION=3 OS_PASSWORD=XX OS_PROJECT_DOMAIN_NAME=NDC OS_PROJECT_NAME=ozoneaq OS_USER_DOMAIN_NAME=Default OS_USERNAME=jonathan OS_VOLUME_API_VERSION=3 [root@vm013 ~]# openstack image list +--+---++ | ID | Name | Status | +--+---++ | 0099a343-1376-49f4-85f9-795624fb2ce8 | CentOS-7-x86_64-GenericCloud-1808 | active | | 53d7c007-318b-4dad-b7cb-38b1dd31f884 | Ubuntu1604-180919 | active | | 482f52ca-e56c-4555-a0e3-93eb491db389 | Ubuntu1604-20181016 | active | | 212aaf3c-18f6-4327-8a11-c726c2e21780 | Ubuntu1804-20181016 | active | | 051d2fff-6b90-4321-9c64-c613f0ddf3da | Windows2016Std-20181003r4 | active | | ac6baa7c-fd2f-48e2-84e0-37a86f623e38 | Windows2016std-20181003r2 | active | | 2264c6b9-40e7-492d-a5bc-dd11a7b4ee10 | Windows2016std-20181004 | active | | 6d865748-ae7a-4c43-9d01-bc35c9002fd9 | Windows2016std-20181004r2 | active | | 26ba1766-aa67-4b1b-81cd-90dda8d41384 | WindowsServer2016-20180926| active | | 3fc3c155-c7a2-4556-a5d0-de7eff208d7d | WindowsStd2016-20181010 | active | | b6d161ca-e03b-46c5-95a0-5fe31723c5c7 | centos7-201810100 | active | | 8bdc33be-1eb5-429b-b0ca-682b24df45f0 | centos7-gi-build-test1| active | | 34a915b8-cca6-45c3-9348-5e15dace444f | cirros| active | | 84102d5c-1641-47bb-b727-a59e707e871c | keyshotslave-1604-snap2 | active | | cedf9ae7-6adc-44d4-b7cb-d5664ea3fef0 | keyshotslave1604-snap1| active | | be4dbd67-d56f-41dd-8378-8aa6ca064f55 | mm-cirros-test| active | | be67cf99-b545-4a91-a3d8-fe9f26a8854d | mm-cirros-test2 | active | | a8dfd028-5911-4178-a77d-bb3da8996372 | mm-test-image4| active | | b6d9d44d-2e3c-48a9-9bf5-b6fca20979f9 | testt2-snap | active | | 1c401eea-0e6e-475b-9a46-ffbfb388ca35 | ubuntu1804-180919 | active | +--+---++ [root@vm013 ~]# openstack image show cirros +--+-+ | Field| Value |
[Yahoo-eng-team] [Bug 1888661] Re: glance-api fails to start when ceph.conf doesn't end in a newline
** Project changed: glance => glance-store -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1888661 Title: glance-api fails to start when ceph.conf doesn't end in a newline Status in glance_store: New Bug description: glance-api fails to start when the provided ceph.conf does not end in a newline. Take a working ceph.conf, trim all whitespace at the end and start glance-api. It aborts with the error message ERROR: [errno 22] RADOS invalid argument (error calling conf_read_file) Add a newline at the end, start it again and it works. Other compontents of Openstack (cinder, nova, gnocchi) work without the newline at the ende, this should be consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/glance-store/+bug/1888661/+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 1545092] Re: Images v2 api image-create vulnerability
I think by now this is safe to close as opinion. I don't see us doing the rate limiting on Glance side, but assume it being done on the loadbalancer or encryption termination level instead. ** 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/1545092 Title: Images v2 api image-create vulnerability Status in Glance: Opinion Status in OpenStack Security Advisory: Opinion Status in OpenStack Security Notes: Fix Released Bug description: This report applies to all versions of Glance. The POST v2/images call creates an image (record) in 'queued' status. There is no limit enforced in glance on the number of images a single tenant may create, just on the total amount of storage a single user may consume [0]. Thus a user could either maliciously or by mistake clog up multiple database tables (images, image_properties, image_tags, image_members) with useless image records, thereby causing a denial of service. This is a concern because the approved 2016.0 DefCore specification requires the 'images-v2-index' capability [1, 2]. The tempest test for this capability functions by creating several image records and then checking the GET v2/images response to make sure all these records are returned [3]. Thus any cloud that wishes to qualify under 2016.01 must expose POST v2/images to all end users, thereby exposing such clouds to this vulnerability, which could otherwise be mitigated by restricting POST v2/images to trusted users. [0] https://github.com/openstack/glance/blob/132906146dd74a2eeae67706e19e4fa44559bb8b/etc/glance-api.conf#L89 [1] https://github.com/openstack/defcore/blob/master/2016.01.json#L48 [2] https://github.com/openstack/defcore/blob/master/2016.01.json#L1391-L1412 [3] https://github.com/openstack/tempest/blob/df88737b9cdaabb5633b4fefb723676e71cd1af0/tempest/api/image/v2/test_images.py#L184-L191 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1545092/+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 1529836] Re: Fix deprecated library function (os.popen()).
** No longer affects: glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1529836 Title: Fix deprecated library function (os.popen()). Status in bilean: In Progress Status in Blazar: Fix Released Status in Ceilometer: Fix Released Status in ceilometer-powervm: Fix Released Status in Cinder: Fix Released Status in congress: In Progress Status in glance_store: Fix Released Status in group-based-policy-specs: Fix Released Status in OpenStack Heat: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in horizon-cisco-ui: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Released Status in Kwapi: In Progress Status in OpenStack Shared File Systems Service (Manila): Fix Released Status in Murano: Fix Released Status in networking-powervm: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in nova-powervm: Fix Released Status in python-heatclient: Fix Released Status in python-keystoneclient: Fix Released Status in Python client library for Zaqar: In Progress Status in Sahara: Fix Released Status in senlin: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in tempest: Fix Released Status in Zaqar-ui: Fix Released Bug description: Deprecated library function os.popen is still in use at some places. Need to replace it using subprocess module. To manage notifications about this bug go to: https://bugs.launchpad.net/bilean/+bug/1529836/+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 1454087] Re: Image data stays in store if image is deleted after creating image using import task (CVE-2015-3289)
** 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/1454087
Title:
Image data stays in store if image is deleted after creating image
using import task (CVE-2015-3289)
Status in Glance:
Fix Released
Status in OpenStack Security Advisory:
Fix Released
Bug description:
Image data stays in store if image is deleted after creating image
using import task
Trying to delete image created using task api (import-from) image gets
deleted from the database, but image data remains in the backend.
Steps to reproduce:
1. Create image using task api
$ curl -i -X POST -H 'User-Agent: python-glanceclient' -H 'Content-
Type: application/json' -H 'Accept-Encoding: gzip, deflate, compress'
-H 'Accept: */*' -H 'X-Auth-Token: 35a9e49237b74eddbe5057eb434b3f9e'
-d '{"type": "import", "input": {"import_from":
"http://releases.ubuntu.com/14.10/ubuntu-14.10-server-i386.iso;,
"import_from_format": "raw", "image_properties": {"disk_format":
"raw", "container_format": "bare", "name": "task_image"}}}'
http://10.69.4.176:9292/v2/tasks
2. wait until image becomes active.
3. Confirm image is in active state.
$ glance image-list
4. Delete the image
$ glance image-delete
5. Verify image-list does not show deleted image
$ glance image-list
Image gets deleted from the database but image data presents in the
backend.
Note:
This issue is fixed in master by this patch
https://review.openstack.org/#/c/181345/4
This issue will be resolved by back-porting above patch to stable/kilo.
Affected branches: stable/kilo
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1454087/+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 1911700] Re: glance status upgrade check fails with TypeError
** 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/1911700
Title:
glance status upgrade check fails with TypeError
Status in Glance:
Fix Released
Bug description:
When the 'enabled_backends' option has not been set, it defaults to
None and we get the following error:
$ touch test.conf
$ glance-status --config-file=./test.conf upgrade check
Error:
Traceback (most recent call last):
File
"/home/cyril/openstack/glance/v/lib/python3.9/site-packages/oslo_upgradecheck/upgradecheck.py",
line 196, in run
return conf.command.action_fn()
File
"/home/cyril/openstack/glance/v/lib/python3.9/site-packages/oslo_upgradecheck/upgradecheck.py",
line 106, in check
result = func(self)
File "/home/cyril/openstack/glance/glance/cmd/status.py", line 36, in
_check_sheepdog_store
if 'sheepdog' in getattr(CONF, 'enabled_backends', {}):
TypeError: argument of type 'NoneType' is not iterable
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1911700/+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 1908074] Re: swift backend: openstack image-download / glance image-save fails
Thanks Thomas and Jim,
Closed the bug as invalid.
** 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/1908074
Title:
swift backend: openstack image-download / glance image-save fails
Status in Glance:
Invalid
Bug description:
Hi,
I'm the maintainer of OpenStack in Debian. Using a deployment with
Swift as backend, with glance-api.conf configured this way:
[swift]
swift_store_cacert=/etc/ssl/certs/oci-pki-oci-ca-chain.pem
swift_store_create_container_on_put=True
swift_store_endpoint_type=internalURL
swift_store_config_file=/etc/glance/glance-swift.conf
default_swift_reference=ref1
# cat /etc/glance/glance-swift.conf
[ref1]
user = services:glance
key = PASSWORD
auth_version = 3
auth_address = https://:443/identity/v3
user_domain_id=default
project_domain_id=default
I could upload an image to Glance. It's really there in Swift, I
checked for that fact. Though saving the image fails: when I do
"openstack image save", my swift-proxy recieves a HTTP/1.1 499 (ie:
Client Closed Request), then glance-api returns a 502 (bad gatway).
Unfortunately, using uwsgi and https for Glance wasn't very much
verbose, so I downgraded Glance-api to use eventlet without ssl, and
then I could see in the glance-api.log:
2020-12-14 10:43:47.367 16080 DEBUG swiftclient
[req-f1a898a5-e202-45b7-80e1-7bb68c3b3f52 dcc01371101246afacc8403030921f53
d71a5d98aef04386b57736a4ea4f3644 - default default] RESP STATUS: 200 OK
http_log /usr/lib/python3/dist-packages/swiftclient/client.py:188
2020-12-14 10:43:47.367 16080 DEBUG swiftclient
[req-f1a898a5-e202-45b7-80e1-7bb68c3b3f52 dcc01371101246afacc8403030921f53
d71a5d98aef04386b57736a4ea4f3644 - default default] RESP HEADERS:
{'Content-Type': 'application/octet-stream', 'Etag':
'aef23ab9c77b8caa2e6042fa30aadd95', 'Last-Modified': 'Mon, 14 Dec 2020 10:18:04
GMT', 'X-Timestamp': '1607941083.89546', 'Accept-Ranges': 'bytes',
'X-Trans-Id': 'txdabda903f73c47d1a266e-005fd741e1', 'X-Openstack-Request-Id':
'txdabda903f73c47d1a266e-005fd741e1', 'Connection': 'close',
'Strict-Transport-Security': 'max-age=63072000'} http_log
/usr/lib/python3/dist-packages/swiftclient/client.py:189
2020-12-14 10:43:47.368 16080 WARNING glance.location
[req-f1a898a5-e202-45b7-80e1-7bb68c3b3f52 dcc01371101246afacc8403030921f53
d71a5d98aef04386b57736a4ea4f3644 - default default] Get image
8d2ca7c8-de71-41c1-a6bc-73dd0dd37646 data failed: int() argument must be a
string, a bytes-like object or a number, not 'NoneType'.
2020-12-14 10:43:47.368 16080 ERROR glance.location
[req-f1a898a5-e202-45b7-80e1-7bb68c3b3f52 dcc01371101246afacc8403030921f53
d71a5d98aef04386b57736a4ea4f3644 - default default] Glance tried all active
locations to get data for image 8d2ca7c8-de71-41c1-a6bc-73dd0dd37646 but all
have failed.
Then later on, I get some:
File "/usr/lib/python3/dist-packages/webob/dec.py", line 143, in __call__
return resp(environ, start_response)
File "/usr/lib/python3/dist-packages/webob/dec.py", line 143, in __call__
return resp(environ, start_response)
TypeError: 'ImageProxy' object is not callable
but that's a consequence of Glance-api not being able to properly
download the image from Swift (so I didn't past all the stack-dump
above).
My setup is with the packages from Debian (which I maintain), running
Victoria over Buster. If you want to try, with Buster you can do:
apt-get install extrepo
extrepo enable openstack_victoria
apt-get update
apt-get install glance-api...
If you are brave enough, you can also try directly in Debian Unstable
(that's the same packages which I upload there, and maintain as
backports for Debian Stable).
Cheers,
Thomas Goirand
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1908074/+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 1897773] Re: Images API did not have version bump when cinder locations uri changed to support multi-store
** Changed in: glance/victoria 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/1897773 Title: Images API did not have version bump when cinder locations uri changed to support multi-store Status in Glance: Fix Released Status in Glance victoria series: Fix Released Bug description: As part of making Cinder store driver multi-store compatible, we changed the location URI format for the cinder stores. This URI gets posted via Images API when "show_multiple_locations" is enabled. What we did not do is to bump the API version to indicate that there was a change. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1897773/+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 1901467] Re: Listing images which have tens of tags is too slow
** Changed in: glance Status: New => Opinion ** Changed in: glance Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1901467 Title: Listing images which have tens of tags is too slow Status in Glance: Opinion Bug description: Our client application retrieves all the images we have. The images have tens of tags with it. When asking these images with "limit=1000", it took 10+ seconds in my environment that uses 'mariadb'. The API query we currently use: `GET /v2/images?limit=1001=public` We have about 200+ public images and half of them have more then 30 tags. AFAIK, the main reason for this seems to be SQLalchemy and its generated queries, which use several 'left outer join'; images, image_properties, image_locations, and image_tags tables are joined. With 'limit=1000', this produces tremendous numbers of rows to be scanned. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1901467/+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 1886657] Re: Global request ID erroneously interpreted as local ID
Unfortunately the request ID mess was one of those things where existing implementations were not considered while designing new ones. Pretty much since the introduction of request IDs to Glance the g-api and g-reg services accepted request ID from the header and used the same ID to allow keeping track of the request without mapping the request IDs. Well, this was one of those things that was ignored when the wide usage of request IDs were started and unfortunately the direction was non- compatible with behaviour of FE. Glance. Changing this now would be API breaking change, so unfortunately this is something that needs to be taken into account when Designing Images API v3. ** Changed in: glance Importance: Undecided => Wishlist ** 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/1886657 Title: Global request ID erroneously interpreted as local ID Status in Glance: Won't Fix Bug description: This is about the Global Request ID functionality of OpenStack [1]. While observing the Glance log file, I noticed Glance always logging the global_request_id instead of a local one if it is available, erroneously displaying the global ID as if it was a local ID. # Technical summary Using "%(global_request_id)s" within "logging_context_format_string" [2] in the glance-api.conf will always print "None" in the logs whereas "%(request_id)s" will either be an ID generated by Glance if no global ID is available or the received global ID. Culprit seems to be the context middleware of Glance where the global ID in form of the "X-Openstack-Request-Id" header is parsed from the request and passed as "request_id" instead of "global_request_id" to the "glance.context.RequestContext.from_environ()" call [3]. This is in contrast to other services such as Nova or Neutron where the two variables actually print the values according to their name (request_id always being the local one, whereas global_request_id is the global one or None). # Proposed solution The parsed header value should be passed as "global_request_id" to the RequestContext call's kwargs in the code path referenced above. # How to reproduce 1. Set the following setting in the Glance API configuration: logging_context_format_string = %(levelname)s %(name)s [%(request_id)s | %(global_request_id)s %(user_identity)s] %(instance)s%(message)s 2. Observe the Glance API log while making requests without specifying a global request id: export OS_TOKEN=... export GLANCE_ADDR=... curl -g -i -X GET "http://$GLANCE_ADDR:9292/v2/images; -H "X-Auth-Token: $OS_TOKEN" 3. Observe the Glance API log while making requests while explicitly specifying a global request id using the "X-Openstack-Request-Id" header: export OS_TOKEN=... export GLOBAL_ID=1593a32f-0912-49df-994d-5992c8a2a0c4 export GLANCE_ADDR=... curl -g -i -X GET "http://$GLANCE_ADDR:9292/v2/images; -H "X-Auth-Token: $OS_TOKEN" -H "X-Openstack-Request-Id: $GLOBAL_ID" For step 2, you will see that %(request_id)s changes between requests, whereas %(global_request_id)s is None. This correct behavior and identical to other OpenStack API services. For step 3, you will see that %(request_id)s is actually replaced by the passed global ID, while %(global_request_id)s is still None. This is an error since the former should still be a local ID whereas the latter should display the passed global ID header content instead. # Link references [1] https://specs.openstack.org/openstack/oslo-specs/specs/pike/global-req-id.html [2] https://docs.openstack.org/oslo.context/2.17.0/user/usage.html#context-variables [3] https://github.com/openstack/glance/blob/e6db0b10a703037f754007bef6f56451086850cd/glance/api/middleware/context.py#L201 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1886657/+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 1897773] Re: Images API did not have version bump when cinder locations uri changed to support multi-store
** Also affects: glance/victoria Importance: Critical Assignee: Erno Kuvaja (jokke) Status: Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1897773 Title: Images API did not have version bump when cinder locations uri changed to support multi-store Status in Glance: In Progress Status in Glance victoria series: In Progress Bug description: As part of making Cinder store driver multi-store compatible, we changed the location URI format for the cinder stores. This URI gets posted via Images API when "show_multiple_locations" is enabled. What we did not do is to bump the API version to indicate that there was a change. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1897773/+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 1897773] [NEW] Images API did not have version bump when cinder locations uri changed to support multi-store
Public bug reported: As part of making Cinder store driver multi-store compatible, we changed the location URI format for the cinder stores. This URI gets posted via Images API when "show_multiple_locations" is enabled. What we did not do is to bump the API version to indicate that there was a change. ** Affects: glance Importance: Critical Assignee: Erno Kuvaja (jokke) Status: Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1897773 Title: Images API did not have version bump when cinder locations uri changed to support multi-store Status in Glance: Triaged Bug description: As part of making Cinder store driver multi-store compatible, we changed the location URI format for the cinder stores. This URI gets posted via Images API when "show_multiple_locations" is enabled. What we did not do is to bump the API version to indicate that there was a change. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1897773/+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 1889676] Re: "stores" can be set as property breaking multistore indication of stores where the images are present
** Changed in: glance/ussuri Assignee: (unassigned) => Erno Kuvaja (jokke) ** No longer affects: glance/train -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1889676 Title: "stores" can be set as property breaking multistore indication of stores where the images are present Status in Glance: Fix Released Status in Glance ussuri series: In Progress Status in Glance victoria series: Fix Released Bug description: Glance API happily accepts `glance image-create --property stores:test1,test2` while stores is reserved for indication in which store IDs the image is actually present. For the fix we need client patch [0] merged and released. [0] https://review.opendev.org/#/c/744024/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1889676/+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 1889676] Re: "stores" can be set as property breaking multistore indication of stores where the images are present
** Also affects: glance/train Importance: Undecided Status: New ** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria Importance: Critical Assignee: Erno Kuvaja (jokke) Status: Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1889676 Title: "stores" can be set as property breaking multistore indication of stores where the images are present Status in Glance: Triaged Status in Glance train series: New Status in Glance ussuri series: New Status in Glance victoria series: Triaged Bug description: Glance API happily accepts `glance image-create --property stores:test1,test2` while stores is reserved for indication in which store IDs the image is actually present. For the fix we need client patch [0] merged and released. [0] https://review.opendev.org/#/c/744024/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1889676/+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 1889676] [NEW] "stores" can be set as property breaking multistore indication of stores where the images are present
Public bug reported: Glance API happily accepts `glance image-create --property stores:test1,test2` while stores is reserved for indication in which store IDs the image is actually present. For the fix we need client patch [0] merged and released. [0] https://review.opendev.org/#/c/744024/ ** Affects: glance Importance: Critical Assignee: Erno Kuvaja (jokke) Status: Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1889676 Title: "stores" can be set as property breaking multistore indication of stores where the images are present Status in Glance: Triaged Bug description: Glance API happily accepts `glance image-create --property stores:test1,test2` while stores is reserved for indication in which store IDs the image is actually present. For the fix we need client patch [0] merged and released. [0] https://review.opendev.org/#/c/744024/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1889676/+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 1889664] [NEW] Image Import 'web-download' is broken with py37+
Public bug reported: The image import method 'web-download' is broken when running under Python 3.7 or newer due to the evenlet issue [0] The fix is merged in eventlet master but not released yet. Also We need to sort out our current requirements cap to be able to get advantage of it. [0] https://github.com/eventlet/eventlet/issues/632 ** Affects: glance Importance: High Status: Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1889664 Title: Image Import 'web-download' is broken with py37+ Status in Glance: Triaged Bug description: The image import method 'web-download' is broken when running under Python 3.7 or newer due to the evenlet issue [0] The fix is merged in eventlet master but not released yet. Also We need to sort out our current requirements cap to be able to get advantage of it. [0] https://github.com/eventlet/eventlet/issues/632 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1889664/+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 1889640] [NEW] Image import might result 'active' image with no data.
Public bug reported: There is two scenarios where Interoperable Image Import might result 'Active' image without image data in it. 1) If the data from staging was deleted by the time task tries to delete it. * In This scenario the taskflow will hit revert chain, delete the image from the stores it had just uploaded, but will not revert the set_image_data() changing the image to active. 2) If the 'all_stores_must_succeed' was set to 'false' and all uploads fails. * As we ignore the individual store failures in this scenario the taskflow will finish and when it gets to _SaveImage it will finally set the image active even we have no locations. ** Affects: glance Importance: Critical Assignee: Erno Kuvaja (jokke) Status: Triaged ** Affects: glance/ussuri Importance: Undecided Assignee: Erno Kuvaja (jokke) Status: New ** Affects: glance/victoria Importance: Critical Assignee: Erno Kuvaja (jokke) Status: Triaged ** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria Importance: Critical Assignee: Erno Kuvaja (jokke) Status: Triaged ** Changed in: glance/ussuri Assignee: (unassigned) => Erno Kuvaja (jokke) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1889640 Title: Image import might result 'active' image with no data. Status in Glance: Triaged Status in Glance ussuri series: New Status in Glance victoria series: Triaged Bug description: There is two scenarios where Interoperable Image Import might result 'Active' image without image data in it. 1) If the data from staging was deleted by the time task tries to delete it. * In This scenario the taskflow will hit revert chain, delete the image from the stores it had just uploaded, but will not revert the set_image_data() changing the image to active. 2) If the 'all_stores_must_succeed' was set to 'false' and all uploads fails. * As we ignore the individual store failures in this scenario the taskflow will finish and when it gets to _SaveImage it will finally set the image active even we have no locations. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1889640/+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 1887099] Re: Invalid metadefs for watchdog
** Also affects: glance/ussuri
Importance: Undecided
Status: New
** Also affects: glance/train
Importance: Undecided
Status: New
** Also affects: glance/victoria
Importance: Undecided
Assignee: Cyril Roelandt (cyril-roelandt)
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/1887099
Title:
Invalid metadefs for watchdog
Status in Glance:
In Progress
Status in Glance train series:
New
Status in Glance ussuri series:
New
Status in Glance victoria series:
In Progress
Bug description:
The metadefs for the watchdog features, located in etc/metadefs
/compute-watchdog.json, seem to be invalid and should read:
"resource_type_associations": [
{
"name": "OS::Glance::Image",
"prefix": "hw_"
},
{
"name": "OS::Nova::Flavor",
"prefix": "hw:"
}
],
The "hw" prefix should also be removed from the property.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1887099/+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 1886537] Re: Missing parameters in python-glanceclient image-import command documentation
Thanks for pointing this out. I targeted it to python-glanceclient instead of the service. ** Project changed: glance => python-glanceclient ** Changed in: python-glanceclient Status: New => Triaged ** Changed in: python-glanceclient Importance: Undecided => Medium ** Tags added: low-hanging-fruit -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1886537 Title: Missing parameters in python-glanceclient image-import command documentation Status in Glance Client: Triaged Bug description: Description python-glanceclient documentation [0] for image-import command shows just an optional parameter: ``` usage: glance image-import [--import-method ] ``` But in the actual CLI there're more parameters available: ``` $ glance help image-import usage: glance image-import [--import-method ] [--uri ] [--store ] [--stores ] [--all-stores [True|False]] [--allow-failure [True|False]] ``` How to reproduce 1. Open python-glanceclient image-import command documentation [0] 2. Check the params Expected behavior -- To have all the parameters documented Actual behavior -- Parameters are missing, compared to an actual `glance help image- import` command output. [0] https://docs.openstack.org/python- glanceclient/latest/cli/details.html#glance-image-import To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1886537/+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 1885725] [NEW] 'copy-image' import job should not try to run additional plugins
Public bug reported: The import plugins were designed to be additional tasks to be performed against the image data or metadata before image being set to active. Things like uncompression or conversion etc. just does not make sense while target is just to copy the data between stores. ** Affects: glance Importance: High Assignee: Erno Kuvaja (jokke) Status: New ** Affects: glance/ussuri Importance: High Assignee: Erno Kuvaja (jokke) Status: New ** Affects: glance/victoria Importance: High Assignee: Erno Kuvaja (jokke) Status: New ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria Importance: Undecided Assignee: Erno Kuvaja (jokke) Status: New ** Changed in: glance/ussuri Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance/victoria Importance: Undecided => High ** Changed in: glance/ussuri 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/1885725 Title: 'copy-image' import job should not try to run additional plugins Status in Glance: New Status in Glance ussuri series: New Status in Glance victoria series: New Bug description: The import plugins were designed to be additional tasks to be performed against the image data or metadata before image being set to active. Things like uncompression or conversion etc. just does not make sense while target is just to copy the data between stores. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1885725/+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 1885003] Re: Interrupted copy-image may break a subsequent operation
** Also affects: glance/ussuri Importance: Undecided Status: New ** Also affects: glance/victoria Importance: High 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/1885003 Title: Interrupted copy-image may break a subsequent operation Status in Glance: In Progress Status in Glance ussuri series: New Status in Glance victoria series: In Progress Bug description: Consider this scenario: 1. Upload image to glance to one store, everything is good 2. Start an image_import(method='copy-image') to copy the image to another store 3. Power failure, network failure, or `killall -9 glance-api` 4. After the failure, re-request the copy-to-store At this point, one of two cases will happen (we think) depending on the copy request: 5a. If all_stores_must_succeed=False, then we will see the partial staging residue, try to copy it to the store 6a. After we copy what was in the staging area to the new store, we will compare the size to that of the actual image, see that it is wrong and fail the operation 7a. The residue in the staging area will be deleted, but the storage on the backend will neither be updated in locations nor deleted, which is a LEAK (bad). 8a. The user could retry and it should succeed this time because the staging residue is gone, but the storage was leaked in the above step. the other option is: 5b. If all_stores_must_succeed=True, then we will see the partial staging residue, try to copy it to the store 6b. After we copy what was in the staging area to the new store and compare the size, we will fail the operation 7b. We will not delete the residue from the staging dir, but _will_ delete the backend storage, avoiding the leak. 8b. The user will retry, which will repeat the same and fail again, over and over. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1885003/+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 1884587] Re: image import copy-to-store API should reflect proper authorization
** Also affects: glance/victoria Importance: Undecided Status: In Progress ** Also affects: glance/ussuri Importance: Undecided Status: New ** Changed in: glance/ussuri Importance: Undecided => High ** Changed in: glance/victoria 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/1884587 Title: image import copy-to-store API should reflect proper authorization Status in Glance: In Progress Status in Glance ussuri series: New Status in Glance victoria series: In Progress Bug description: In testing the image import copy-to-store mechanism from Nova, I hit an issue that seems clearly to be a bug. Scenario: A user boots an instance from an image they have permission to see. Nova uses their credentials to start an image import copy-to-store operation, which succeeds: "POST /v2/images/e6b1a7d0-ccd8-4be3-bef7-69c68fca4313/import HTTP/1.1" 202 211 0.481190 Task [888e97e5-496d-4b94-b530-218d633f866a] status changing from pending to processing Note the 202 return code. My code polls for a $timeout period, waiting for the image to either arrive at the new store, or be marked as error, which never happens ($timeout=600s). The glance log shows (trace truncated): glance-api[14039]: File "/opt/stack/glance/glance/async_/flows/api_image_import.py", line 481, in get_flow glance-api[14039]: stores if glance-api[14039]: File "/opt/stack/glance/glance/api/authorization.py", line 296, in forbidden_key glance-api[14039]: raise exception.Forbidden(message % key) glance-api[14039]: glance.common.exception.Forbidden: You are not permitted to modify 'os_glance_importing_to_stores' on this image. So apparently Nova is unable to use the user's credentials to initiate a copy-to-store operation. That surprises me and I think it likely isn't the access control we should be enforcing. However, if we're going to reject the operation, we should reject it at the time the HTTP response is sent, not later async, since we can check authorization right then and there. The problem in this case is that from the outside, I have no way of knowing that the task fails subsequently. I receive a 202, which means I should start polling for completion. The task fails to load/run and thus can't update any status on the image, and I'm left to wait for 600s before I give up. So, at the very least, we're not checking the same set of permissions during the HTTP POST call, and we should be. I also would tend to argue that the user should be allowed to copy the image and not require an admin to do it, perhaps with some additional policy element to control that. However, I have to be able to determine when and when not to wait for 600s. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1884587/+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] Re: read-only http store should not be used if --all-stores specified for import/copy image workflow
** Also affects: glance/ussuri Importance: High Assignee: Abhishek Kekane (abhishek-kekane) Status: In Progress ** Also affects: glance/victoria Importance: Undecided Status: New ** Changed in: glance/ussuri Status: In Progress => Triaged ** Changed in: glance/victoria Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance/victoria Status: New => Triaged ** Changed in: glance/victoria Importance: Undecided => High ** Changed in: glance/victoria Status: Triaged => 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/1881958 Title: read-only http store should not be used if --all-stores specified for import/copy image workflow Status in Glance: Triaged Status in Glance ussuri series: Triaged Status in Glance victoria series: In Progress 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 1855708] Re: Reload tests broken in Py3
** Also affects: glance/train 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/1855708 Title: Reload tests broken in Py3 Status in Glance: Triaged Status in Glance train series: New Bug description: Looks like our reload is also broken in PY3 that has gone unnoticed as the test breakage was blamed on ssl. Test fails on timeout at worker change. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1855708/+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 1376605] Re: Invalid url for glance image upload does not abort, cannot be deleted.
** 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/1376605 Title: Invalid url for glance image upload does not abort, cannot be deleted. Status in Glance: Invalid Bug description: Apparently I had provided an invalid url. So glance kept trying and trying to upload the image that I had just created. When I tried to "delete" the image, I got no error message. But the page re-painted with the same problem image in the list. Logging out, using a new browser window, all showed the problem image once again, so it was not just a stuck javascript. It would be good to provide some "abort" functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1376605/+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 1523941] Re: (Import Refactor) Header changes
** 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/1523941 Title: (Import Refactor) Header changes Status in Glance: Won't Fix Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ This spec requires new headers to be added to some of our calls. For example, the image-create call should return the upload path for the image data as it was discussed in the spec. This bug likely depends on this one: https://bugs.launchpad.net/glance/+bug/1523937 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1523941/+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 1540934] Re: glance-cache-prefetcher is broken
No longer relevant ** 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/1540934 Title: glance-cache-prefetcher is broken Status in Glance: Won't Fix Bug description: Glance prefetcher is still configured to use keystone v1. As it still does not use the right uri or pass the values as json but rather uses headers. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1540934/+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 1549428] Re: castellan unnecessarily included in requirements.txt
** Changed in: glance Status: In Progress => 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/1549428 Title: castellan unnecessarily included in requirements.txt Status in Glance: Opinion Bug description: The castellan dependency is only used for glance/common/signature_utils.get_certificate. Based on that being the only usage, this can be made an optional dependency for glance and not a hard requirement to be pulled in as part of requirements.txt To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1549428/+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] Re: Image data stays in staging store if image is deleted while its in importing state
** Also affects: glance/train Importance: Undecided Status: New ** Changed in: glance/train Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane) ** Changed in: glance/train Importance: Undecided => Critical ** Changed in: glance/train Status: New => 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/1855417 Title: Image data stays in staging store if image is deleted while its in importing state Status in Glance: Fix Released Status in Glance train series: In Progress 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 1855708] Re: Reload tests broken in Py3
** Changed in: glance Status: Invalid => Triaged ** 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/1855708 Title: Reload tests broken in Py3 Status in Glance: Triaged Bug description: Looks like our reload is also broken in PY3 that has gone unnoticed as the test breakage was blamed on ssl. Test fails on timeout at worker change. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1855708/+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 1855708] [NEW] Reload tests broken in Py3
Public bug reported: Looks like our reload is also broken in PY3 that has gone unnoticed as the test breakage was blamed on ssl. Test fails on timeout at worker change. ** Affects: glance Importance: Undecided Status: Invalid ** Changed in: glance Status: New => Triaged ** Changed in: glance Status: Triaged => 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/1855708 Title: Reload tests broken in Py3 Status in Glance: Invalid Bug description: Looks like our reload is also broken in PY3 that has gone unnoticed as the test breakage was blamed on ssl. Test fails on timeout at worker change. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1855708/+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 1838332] Re: Glance adding image member fails with multibackend
** Also affects: glance/stein Importance: Critical Assignee: Abhishek Kekane (abhishek-kekane) Status: Fix Released ** Also affects: glance/train Importance: Undecided Status: New ** Changed in: glance/train Importance: Undecided => High ** Changed in: glance/train Status: New => In Progress ** Changed in: glance/train Status: In Progress => Fix Released ** Changed in: glance/train Importance: High => Critical ** Changed in: glance/stein Importance: Critical => High ** Changed in: glance/stein Status: Fix Released => In Progress ** 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/1838332 Title: Glance adding image member fails with multibackend Status in Glance: In Progress Status in Glance stein series: In Progress Status in Glance train series: Fix Released Bug description: When adding an image member to a shared image, we get the following traceback on glance-api: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/glance/common/wsgi.py", line 1427, in __call__ request, **action_args) File "/usr/lib/python2.7/site-packages/glance/common/wsgi.py", line 1470, in dispatch return method(*args, **kwargs) File "/usr/lib/python2.7/site-packages/glance/common/utils.py", line 417, in wrapped return func(self, req, *args, **kwargs) File "/usr/lib/python2.7/site-packages/glance/api/v2/image_members.py", line 117, in create member_repo.add(new_member) File "/usr/lib/python2.7/site-packages/glance/api/authorization.py", line 170, in add self.member_repo.add(image_member) File "/usr/lib/python2.7/site-packages/glance/notifier.py", line 556, in add super(ImageMemberRepoProxy, self).add(member) File "/usr/lib/python2.7/site-packages/glance/domain/proxy.py", line 121, in add self.base.add(self.member_proxy_helper.unproxy(member)) File "/usr/lib/python2.7/site-packages/glance/api/policy.py", line 254, in add self.member_repo.add(member) File "/usr/lib/python2.7/site-packages/glance/location.py", line 567, in add self._set_acls() File "/usr/lib/python2.7/site-packages/glance/location.py", line 563, in _set_acls context=self.context) File "/usr/lib/python2.7/site-packages/glance_store/backend.py", line 550, in set_acls loc = location.get_location_from_uri(location_uri, conf=CONF) File "/usr/lib/python2.7/site-packages/glance_store/location.py", line 77, in get_location_from_uri raise exceptions.UnknownScheme(scheme=pieces.scheme) UnknownScheme: Unknown scheme 'file' found in URI Related config is: [DEFAULT] enabled_backends = gpfs:file [gpfs] filesystem_store_datadir = /path/to/Openstack/Glance If I'm reading this right, the issue is related to glance_store.location.SCHEME_TO_CLS_MAP being empty. This causes backend.get_location_from_uri to fail to look up the scheme. I think this is happening because backend.py is populating location.SCHEME_TO_CLS_MAP, but multi_backend is populating location.SCHEME_TO_CLS_BACKEND_MAP. Because location.get_location_from_uri is only looking at SCHEME_TO_CLS_MAP, when it is called with a multi-backend config, it fails to find any registered schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1838332/+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 1843891] [NEW] False claim on deprecation message
Public bug reported: 4265e61bc84ce9bd085a95d8734647f4875af740 introduced DEPRECATION message into the glance-api.conf claiming that "it is no longer necessary to reserve a local directory for the temporary image staging area." Similar claim was made towards tasks workspace area. Both of the claims are wrong, the dedicated directories are still necessary for these features to operate properly, only the internal mechanics how these folders are accessed are being cleaned up and new ways to configure them was introduced. To avoid any operator confusion, we should remove those claims from the deprecation messages. ** Affects: glance Importance: High Assignee: Erno Kuvaja (jokke) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance Status: New => In Progress ** 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/1843891 Title: False claim on deprecation message Status in Glance: In Progress Bug description: 4265e61bc84ce9bd085a95d8734647f4875af740 introduced DEPRECATION message into the glance-api.conf claiming that "it is no longer necessary to reserve a local directory for the temporary image staging area." Similar claim was made towards tasks workspace area. Both of the claims are wrong, the dedicated directories are still necessary for these features to operate properly, only the internal mechanics how these folders are accessed are being cleaned up and new ways to configure them was introduced. To avoid any operator confusion, we should remove those claims from the deprecation messages. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1843891/+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 1831997] [NEW] Unit tests relying on external dependencies
Public bug reported: As noted on Brian's comment here [0] we are using code from "irrelevant" dependencies to unittest some of our code. We should identify these points and make sure correct amount of mockery is done to isolate the unittests to those units of code only. [0] https://review.opendev.org/#/c/663840/1 ** 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/1831997 Title: Unit tests relying on external dependencies Status in Glance: New Bug description: As noted on Brian's comment here [0] we are using code from "irrelevant" dependencies to unittest some of our code. We should identify these points and make sure correct amount of mockery is done to isolate the unittests to those units of code only. [0] https://review.opendev.org/#/c/663840/1 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1831997/+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 1828333] Re: changing path of filesystem_store_datadir does not reflect
Flagging this to Devstack as Glance parses the config files as designed. ** Also affects: devstack Importance: Undecided Status: New ** 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/1828333 Title: changing path of filesystem_store_datadir does not reflect Status in devstack: New Status in Glance: Invalid 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/devstack/+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 1792710] Re: glance backend is in crazy resize when an image is uploading
PTG May 2nd Cinder/Glance session: Lets not make the size user settable and instead just resize bigger chunks at the time and shrink back after EOF. ** Changed in: glance Importance: Undecided => High ** Changed in: glance Milestone: None => next ** Also affects: glance-store Importance: Undecided Status: New ** Changed in: glance-store Importance: Undecided => High ** No longer affects: glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1792710 Title: glance backend is in crazy resize when an image is uploading Status in Cinder: In Progress Status in glance_store: New Bug description: When uploading a volume to glance as an image, the glance server don't know the image size, so the backend storage server(such as ceph) need to resize the image every time it received new chunk of data(by default 64K). So there will be huge times of resize operations that will impact the performance. - regarding cinder, it has not calculate the image size and pass the correct size to glance - regarding glance, it should allow the client to set image size. This is an known issue which can be found in driver files of all kinds of backend storage system: In file: glance_store/_drivers/rbd.py, function: add In file: glance_store/_drivers/cinder.py, function: add In file: glance_store/_drivers/sheepdog.py, function: add In all these files, there're comments like below: # If the image size provided is zero we need to do # a resize for the amount we are writing. This will # be slower so setting a higher chunk size may # speed things up a bit. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1792710/+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 1796178] Re: community type images are not view able by admin, potential cause of dos
glance image-list has --visibility filter that can be set to "community" to list the by default not listed community images. ** 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/1796178 Title: community type images are not view able by admin, potential cause of dos Status in Glance: Invalid Bug description: At the moment is is for an admin not possible to list all images being uploaded to glance. Images marked as public are only listed by the user doing the upload. That means for example an automated system uploads community images as the result of a build process they will take up space. That could lead to disks being filled with images if this process does not implement any kind of cleanup. The admin will not be able to see that this is causing the problem. Currently the only mitigation I can think of, is putting quota's in place which will limit the amount of storage that can be allocated by the user. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1796178/+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 1789376] Re: image conversion spelling mistake vdmk
*** This bug is a duplicate of bug 1809462 *** https://bugs.launchpad.net/bugs/1809462 Marking this as duplicate of the newer bug due that being used when this was addressed. ** This bug has been marked a duplicate of bug 1809462 Glance image conversion cannot convert to vmdk -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1789376 Title: image conversion spelling mistake vdmk Status in Glance: Incomplete Bug description: In the stable/rocky branch, the image conversion refers to a format "vdmk", which I presume is actually the "vmdk" format. Enclosed is a patch, which replaces all occurrences of "vdmk" with "vmdk". To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1789376/+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 1806912] Re: devstack timeout because g-api takes longer than 60 seconds to start
** Project changed: glance => devstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1806912 Title: devstack timeout because g-api takes longer than 60 seconds to start Status in devstack: Incomplete Status in OpenStack-Gate: Confirmed Bug description: For example: http://logs.openstack.org/60/620660/1/check/heat-functional-orig- mysql-lbaasv2/bc7ef21/logs/devstacklog.txt#_2018-11-30_20_14_13_418 2018-11-30 20:14:13.418 | + lib/glance:start_glance:353 : die 353 'g-api did not start' The g-api logs show it took 62 seconds to start: http://logs.openstack.org/60/620660/1/check/heat-functional-orig- mysql-lbaasv2/bc7ef21/logs/screen-g-api.txt.gz#_Nov_30_20_14_12_852280 Nov 30 20:14:12.852280 ubuntu-xenial-ovh-bhs1-840057 devstack@g-api.service[7937]: WSGI app 0 (mountpoint='') ready in 62 seconds on interpreter 0xb23d10 pid: 7942 (default app) Looks like this primarily happens on ovh-bhs1 nodes. http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22-api%20did%20not%20start%5C%22%20AND%20tags%3A%5C%22console%5C%22=7d To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1806912/+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 1818851] Re: Snapshots of volume backed instances default to qcow2
** 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 Glance. https://bugs.launchpad.net/bugs/1818851 Title: Snapshots of volume backed instances default to qcow2 Status in Cinder: New Status in Glance: New Bug description: This report applies to a production Ocata cloud and also to a Rocky lab environment. I'm not entirely sure which component is responsible exactly but the inconsistency is strongly related to glance. This report results from a mailing list thread I started in October 2018 [1], I only could put the pieces together step by step as some of the behavior was not reproducible, so this took a while, and my conclusion is summed up in [2]. I'll recap here: The backend for nova, cinder and glance is ceph. 1. Creating an instance from a (regular) glance image with 'disk_format = qcow2' results in a "flat" nova instance with no parent data. Although a snapshot seems to create a "raw" image it's actually "qcow2", resulting in more flat images if instances are launched from this new image. 2. Creating a snapshot of a volume based nova instance (raw format) unexpectedly results in a glance image with 'disk_format = qcow2'. But launching a new instance from that snapshot does *not* result in a flat image as I would have expected because of 1. Instead the new instance is a cow-clone of the original volume, which in fact is expected because of the ceph backend. So the workflow seems fine, but I find it very confusing (obviously) that the volume based snapshot is declared as a qcow2 image, that doesn't seem right. Steps to reproduce (part I): 1. Create qcow2 image. 2. Launch instance from qcow2 image. 3. Instance has no parent data, it's a flat rbd image without 'parent data'. Steps to reproduce (part II): 1. Create raw image. 2. Launch volume backed instance from raw image. 3. Create snapshot of instance, resulting in a glance image with 'disk_format = qcow2'. 4. Launch instance from that image, results in a new copy-on-write clone (volume). Expected result: Snapshot of a volume backed instance should also have 'disk_format=raw'. The consequences of the image property 'disk_format' should always be the same, no matter how the image was created. Actual result: Depending on the image creation the same property 'disk_format' has different effects on the ceph backend and the resulting usability. [1] https://www.mail-archive.com/openstack@lists.openstack.org/msg20935.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003383.html To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1818851/+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 1816662] Re: tempest jobs fails because g-api service didn't start
** Project changed: glance => devstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1816662 Title: tempest jobs fails because g-api service didn't start Status in devstack: New Bug description: In neutron's jobs we noticed at least couple of times that tempest job was failed because devstack failure. In devstack log in such case there was an error that "g-qpi service didn't start". Example of error: http://logs.openstack.org/99/630999/8/check/neutron- tempest-plugin-scenario- linuxbridge/1425980/controller/logs/devstacklog.txt.gz#_2019-02-18_12_21_56_122 Logstash query which I used to search for such issues: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C %22g-api%20did%20not%20start%5C%22 To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1816662/+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 1818919] Re: CooperativeReader not py3-ready
** Also affects: glance/queens Importance: Undecided Status: New ** Also affects: glance/stein Importance: High Status: Triaged ** Also affects: glance/rocky 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/1818919 Title: CooperativeReader not py3-ready Status in Glance: Triaged Status in Glance queens series: New Status in Glance rocky series: New Status in Glance stein series: Triaged Bug description: Tim Burke noticed this in IRC today: https://github.com/openstack/glance/blob/17.0.0/glance/common/utils.py#L231 Should be returning b'' since we're supposed to be returning bytes. Apparently our unit tests could use some beefing up, because they're not breaking under py3. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1818919/+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 1562758] Re: generate an uuid for image id
** 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/1562758
Title:
generate an uuid for image id
Status in Glance:
Won't Fix
Bug description:
Why not use `oslo_utils.uuidutils.generate_uuid` function
def new_image(self, image_id=None, name=None, visibility='private',
min_disk=0, min_ram=0, protected=False, owner=None,
disk_format=None, container_format=None,
extra_properties=None, tags=None, **other_args):
extra_properties = extra_properties or {}
self._check_readonly(other_args)
self._check_unexpected(other_args)
self._check_reserved(extra_properties)
if image_id is None:
image_id = str(uuid.uuid4())
created_at = timeutils.utcnow()
updated_at = created_at
status = 'queued'
I think :
image_id = uuidtils.generate_uuid()
don't use
mage_id = str(uuid.uuid4())
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1562758/+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 1778784] Re: mox_fixture = self.useFixture(moxstubout.MoxStubout()) usage is deprecated from oslo.test 3.5.0
** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Importance: Undecided => Medium -- 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/1778784 Title: mox_fixture = self.useFixture(moxstubout.MoxStubout()) usage is deprecated from oslo.test 3.5.0 Status in Glance: New Status in OpenStack Compute (nova): In Progress Bug description: Due to this deprecation in oslo.test 3.5.0: https://github.com/openstack/oslotest/commit/cae8c8d51a94b891ce5b311a91d01b4264b296d2 #diff-72a674ad74b628edbd0f73729c353b85R24 We get this warning quite a bit: nova/test.py:323: DeprecationWarning: Using class 'MoxStubout' (either directly or via inheritance) is deprecated in version '3.5.0' mox_fixture = self.useFixture(moxstubout.MoxStubout()) A simple alternative for nova is to just use the same fixture from mox3: http://git.openstack.org/cgit/openstack/mox3/tree/mox3/fixture.py#n21 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1778784/+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 1775782] Re: glance-image-import.conf not parsed when running under wsgi
Taken into consideration that we don't currently support nor encourage anyone running under wsgi mode either mod_wsgi nor uwsgi , I'd say the priority for this bug is very low, specially as you mentioned in your comment the fix needs to happen in Devstack rather than in Glance. ** Changed in: glance Importance: Undecided => Low ** 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/1775782 Title: glance-image-import.conf not parsed when running under wsgi Status in Glance: Opinion 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 1774402] Re: Glance scrubber SELinux denials
This is a bug in RDO packaging rather than bug in Glance. Please file
the bug in RDO [0] and you have much more luck to get it fixed.
[0] https://bugzilla.redhat.com/enter_bug.cgi?product=RDO
** 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/1774402
Title:
Glance scrubber SELinux denials
Status in Glance:
Invalid
Bug description:
Glance scrubber on RHEL7 from RDO with SELinux enabled get denied
connecting to cinder & swift
type=AVC msg=audit(1527765224.059:149655): avc: denied { name_connect } for
pid=1283 comm="glance-scrubber" dest=8776
scontext=system_u:system_r:glance_scrubber_t:s0 tcontext=
system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket
type=AVC msg=audit(1527765228.066:149656): avc: denied { name_connect } for
pid=1283 comm="glance-scrubber" dest=8776
scontext=system_u:system_r:glance_scrubber_t:s0 tcontext=
system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket
type=AVC msg=audit(1527765228.690:149657): avc: denied { name_connect } for
pid=1283 comm="glance-scrubber" dest=8080
scontext=system_u:system_r:glance_scrubber_t:s0 tcontext=
system_u:object_r:http_cache_port_t:s0 tclass=tcp_socket
Enabling the nis_enabled seboolean allows connections to cinder,
swift looks to need
allow glance_scrubber_t http_cache_port_t:tcp_socket name_connect;
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1774402/+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] Re: Remove glance-direct from enabled_import_methods config option
** Changed in: glance Status: In Progress => 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/1770325 Title: Remove glance-direct from enabled_import_methods config option Status in Glance: Invalid 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 1747848] Re: qcow2 format image uploaded to raw format, failed to start the virtual machine with ceph as backend storage
Glance does not, by default, intervene with the image data. It is really user's responsibility to provide the correct metadata related to the image data they are uploading to provide bootable image. ** Changed in: glance Status: Incomplete => 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/1747848 Title: qcow2 format image uploaded to raw format, failed to start the virtual machine with ceph as backend storage Status in Glance: Opinion Bug description: In the glance-api.conf configuration（Use ceph with backend storage）: [DEFAULT] .. show_image_direct_url = True show_multiple_locations = True .. [glance_store] filesystem_store_datadir = /opt/stack/data/glance/images/ default_store = rbd stores = rbd rbd_store_pool = images rbd_store_user = admin rbd_store_ceph_conf = /etc/ceph/ceph.conf rbd_store_chunk_size = 8 rbd_secret_uuid = 08bf86f1-09c0-4f03-90e6-ae361d520c57 If the qcow2 format image is uploaded as raw format, use this mirror launch virtual machine, to be completed when the virtual machine is created, open the virtual machine console. In the console, you can see "No boot device", the virtual machine can not start from this image. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1747848/+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 1765309] Re: 500 error on image-download if image is not present at any location
So if you look at the code there that you modified to introduce this bug, you are bypassing the try..catch block that will set the exception that would be raised at the failure causing it trying to raise None which obviously will fail. ** 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/1765309 Title: 500 error on image-download if image is not present at any location Status in Glance: Invalid Bug description: As of now for downloading the image it iterates through all the locations and if data (image) is not present at any of the location in the end it Logs the error message as "Glance tried all active locations to get data for image but all have failed." Further it fails with 500 error. This issue can occur either if image is not available in any of the location or any error occured during the download process. NOTE: To reproduce this issue I have manually added 'continue' statement at [1] to assume that image is not available at any of the location. [1] https://github.com/openstack/glance/blob/master/glance/location.py#L470 Steps to reproduce: 1. Modify glance/location.py as mentioned in NOTE 2. Restart glance-api service 3. Download image using: $ glance image-download --file downloaded_image Expected Result: Image data should be downloaded and saved in 'downloaded_image' file Actual Result: glance image-download 780ffe26-b95a-4b6f-b2c0-c38803bed73a --file abcdUnable to download image '780ffe26-b95a-4b6f-b2c0-c38803bed73a'. (502 Proxy Error: Proxy Error: The proxy server received an invalid: response from an upstream server.: The proxy server could not handle the request GET/image/v2/images/780ffe26-b95a-4b6f-b2c0-c38803bed73a/file.: Reason: Error reading from remote server: Apache/2.4.18 (Ubuntu) Server at 192.168.0.6 Port 80 (HTTP 502)) Glance API logs: Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance.location [None req-cfca70d4-d9a7-495f-9762-0fb2a8eee769 admin admin] Glance tried all active locations to get data for image 780ffe26-b95a-4b6f-b2c0-c38803bed73a but all have failed. Apr 19 06:37:58 signature devstack@g-api.service[5419]: CRITICAL glance [None req-cfca70d4-d9a7-495f-9762-0fb2a8eee769 admin admin] Unhandled error: TypeError: 'ImageProxy' object is not callable Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance Traceback (most recent call last): Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 131, in __call__ Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance resp = self.call_func(req, *args, **self.kwargs) Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 196, in call_func Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance return self.func(req, *args, **kwargs) Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/oslo_middleware/base.py", line 131, in __call__ Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance response = req.get_response(self.application) Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1327, in send Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance application, catch_exc_info=False) Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1291, in call_application Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance app_iter = application(self.environ, start_response) Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 131, in __call__ Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance resp = self.call_func(req, *args, **self.kwargs) Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 196, in call_func Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance return self.func(req, *args, **kwargs) Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/oslo_middleware/base.py", line 131, in __call__ Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance response = req.get_response(self.application) Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance File "/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1327, in send Apr 19
[Yahoo-eng-team] [Bug 1744494] Re: Swift backend does not support insecure Keystone v3 with SSL
** Also affects: glance-store
Importance: Undecided
Status: New
** Changed in: glance
Importance: Undecided => Low
** 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/1744494
Title:
Swift backend does not support insecure Keystone v3 with SSL
Status in Glance:
New
Status in glance_store:
New
Bug description:
The swift glance_store client does not create an insecure auth client
when using Keystone v3 with an unsigned cert delivering Swift service
endpoints. With keystone authtoken insecure=true and
swift_store_auth_insecure=true, Glance returns the following error
when uploading a new image:
http://paste.openstack.org/show/648868/
glance-api_1 | 2018-01-20 19:50:43.409 208 ERROR glance.common.wsgi
BackendException: Cannot find swift service endpoint : Unable to
establish connection to https://192.168.1.44:35357/v3/auth/tokens:
HTTPSConnectionPool(host='192.168.1.44', port=35357): Max retries
exceeded with url: /v3/auth/tokens (Caused by SSLError(SSLError("bad
handshake: Error([('SSL routines', 'tls_process_server_certificate',
'certificate verify failed')],)",),))
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1744494/+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 1747727] Re: Unit test test_download_service_unavailable fails behind proxy
by the looks of it, this affected only v1 tests ** 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/1747727 Title: Unit test test_download_service_unavailable fails behind proxy Status in Glance: Won't Fix Bug description: A patch was submitted some time back to allow some tests to run behind a http proxy [0]. It's unclear to me why '0.0.0.0:1' was used rather than something like '127.0.0.1' which will be commonly in an environment's $no_proxy variable, whereas the former will not. Unless there's some special reason this value was used I propose switching instances of 0.0.0.0:1 with 127.0.0.1 [0] https://review.openstack.org/#/c/316965/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1747727/+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 1665851] Re: Newton: Heat not validating images
ditto ** 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/1665851 Title: Newton: Heat not validating images Status in Glance: Invalid Status in OpenStack Heat: Invalid Bug description: I'm seeing this error when Heat validates the existence of an image: 2017-02-18 00:44:03.777 7906 INFO heat.engine.resource [req-593e2bad-c87f-4308-8fe8-fe8652286201 - - - - -] Validating Server "server" 2017-02-18 00:44:03.779 7906 DEBUG heat.engine.stack [req-593e2bad-c87f-4308-8fe8-fe8652286201 - - - - -] Property error: resources.server.properties.image: "cirros" does not validate glance.image (constraint not found) validate /usr/lib/python2.7/dist-packages/heat/engine/stack.py:825 2017-02-18 00:44:03.783 7906 DEBUG oslo_messaging.rpc.server [req-593e2bad-c87f-4308-8fe8-fe8652286201 - - - - -] Expected exception during message handling () _process_incoming /usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py:158 The image, however, exists and is public: os@controller:~$ openstack image list +--+++ | ID | Name | Status | +--+++ | 7ab5d7aa-0d0d-4a38-bf05-03089f49d2d7 | cirros | active | +--+++ I have been updating some componentes related to Tacker and Openstackclient, so I think one of those updates triggered the bug. Please let me know which information to recollect. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1665851/+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 1764200] Re: Glance Cinder backed images & multiple regions
** Also affects: glance-store 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/1764200 Title: Glance Cinder backed images & multiple regions Status in Glance: New Status in glance_store: New Bug description: When using the cinder backed images as per https://docs.openstack.org/cinder/latest/admin/blockstorage-volume- backed-image.html We have multiple locations, glance configured as /etc/glance/glance-api.conf [glance_store] stores = swift, cinder default_store = swift -snip- cinder_store_auth_address = https://hostname:5000/v3 cinder_os_region_name = Region cinder_store_user_name = glance cinder_store_password = Password cinder_store_project_name = cinder-images cinder_catalog_info = volume:cinder:internalURL cinder clones the volume correctly, then talks to glance to add the location of cinder:// glance then talks to cinder to validate the volume id, however this step uses the wrong cinder endpoint and checks the other region. From /usr/lib/python2.7/site-packages/glance_store/_drivers/cinder.py It appears the region name is only used when not passing in the project/user/password. Passing the os_region_name to the cinderclient.Client call on line 351 appears to fix this. ie c = cinderclient.Client(username, password, project, auth_url=url, region_name=glance_store.cinder_os_region_name, insecure=glance_store.cinder_api_insecure, retries=glance_store.cinder_http_retries, cacert=glance_store.cinder_ca_certificates_file) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1764200/+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 1640706] Re: glance image-list throws 'An auth plugin is required to fetch a token' error
Might have been valid bug, we just missed to flag it'd fix. Anyways seems that this is not a problem anymore. ** 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/1640706 Title: glance image-list throws 'An auth plugin is required to fetch a token' error Status in Glance: Invalid Bug description: Following variables are defined via environment variable : OS_PROJECT_NAME OS_PASSWORD OS_AUTH_URL OS_USERNAME OS_TENANT_NAME OS_PROJECT_DOMAIN_NAME But while trying to get image list, glance throws error that 'An auth plugin is required to fetch a token' # glance image-list An auth plugin is required to fetch a token To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1640706/+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 1658590] Re: Windows2012 r2 OS deployment getting Blue Screen death using .qcow2
Good to hear this got fixed. Was never really a Glance bug and slipped under our radar. ** 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/1658590 Title: Windows2012 r2 OS deployment getting Blue Screen death using .qcow2 Status in Glance: Invalid Status in CentOS: Unknown Bug description: I was tried to deploy windows 2012 operating system as instance in my open stack set (Newton) To create instance I followed the below mentioned url http://docs.openstack.org/image-guide/windows-image.html Even I tried direct download qcow2 deployment also by using following url https://cloudbase.it/windows-cloud-images/ in all these cases we are getting Blue Screen Death with following error message "DRIVER_IRQL_NOT_LESS_OR_EQUAL" Please find the attached screenshot for your reference To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1658590/+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 1633561] Re: Downloaded latest devstack. Did stack.sh and getting glance error
closing this as we haven't seen this behavior nor heard back for over a year ** 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/1633561 Title: Downloaded latest devstack. Did stack.sh and getting glance error Status in Glance: Invalid Bug description: 2016-10-14 16:09:36.506 | 2016-10-14 12:09:36.506 INFO migrate.versioning.api [-] done 2016-10-14 16:09:36.506 | 2016-10-14 12:09:36.506 INFO migrate.versioning.api [-] 6 -> 7... 2016-10-14 16:09:37.325 | 2016-10-14 12:09:37.325 INFO migrate.versioning.api [-] done 2016-10-14 16:09:37.325 | 2016-10-14 12:09:37.325 INFO migrate.versioning.api [-] 7 -> 8... 2016-10-14 16:09:37.349 | 2016-10-14 12:09:37.334 INFO glance.db.sqlalchemy.migrate_repo.schema [-] creating table image_members 2016-10-14 16:09:39.162 | 2016-10-14 12:09:39.162 INFO migrate.versioning.api [-] done 2016-10-14 16:09:39.162 | 2016-10-14 12:09:39.162 INFO migrate.versioning.api [-] 8 -> 9... 2016-10-14 16:09:40.765 | 2016-10-14 12:09:40.765 INFO migrate.versioning.api [-] done 2016-10-14 16:09:40.765 | 2016-10-14 12:09:40.765 INFO migrate.versioning.api [-] 9 -> 10... 2016-10-14 16:09:40.830 | 2016-10-14 12:09:40.830 INFO migrate.versioning.api [-] done 2016-10-14 16:09:40.831 | 2016-10-14 12:09:40.830 INFO migrate.versioning.api [-] 10 -> 11... 2016-10-14 16:09:42.522 | 2016-10-14 12:09:42.522 INFO migrate.versioning.api [-] done 2016-10-14 16:09:42.522 | 2016-10-14 12:09:42.522 INFO migrate.versioning.api [-] 11 -> 12... 2016-10-14 16:09:42.580 | 2016-10-14 12:09:42.524 CRITICAL glance [-] File "/opt/stack/glance/glance/db/sqlalchemy/migrate_repo/versions/012_id_to_uuid.py", line 123 2016-10-14 16:09:42.580 | SyntaxError: Non-ASCII character '\x94' in file /opt/stack/glance/glance/db/sqlalchemy/migrate_repo/versions/012_id_to_uuid.py on line 123, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details 2016-10-14 16:09:42.580 | 2016-10-14 16:09:42.580 | 2016-10-14 12:09:42.524 TRACE glance Traceback (most recent call last): 2016-10-14 16:09:42.580 | 2016-10-14 12:09:42.524 TRACE glance File "/usr/local/bin/glance-manage", line 10, in 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance sys.exit(main()) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/opt/stack/glance/glance/cmd/manage.py", line 330, in main 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance return CONF.command.action_fn() 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/opt/stack/glance/glance/cmd/manage.py", line 190, in sync 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance CONF.command.current_version) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/opt/stack/glance/glance/cmd/manage.py", line 108, in sync 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance version) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration.py", line 78, in db_sync 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance migration = versioning_api.upgrade(engine, repository, version) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186, in upgrade 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance return _migrate(url, repository, version, upgrade=True, err=err, **opts) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "", line 2, in _migrate 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/usr/local/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py", line 160, in with_engine 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance return f(*a, **kw) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 366, in _migrate 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance schema.runchange(ver, change, changeset.step) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/usr/local/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 93, in runchange 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance change.run(self.engine, step) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File "/usr/local/lib/python2.7/dist-packages/migrate/versioning/script/py.py", line 141, in run 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance script_func = self._func(funcname) 2016-10-14 16:09:42.581 | 2016-10-14 12:09:42.524 TRACE glance File
[Yahoo-eng-team] [Bug 1751092] Re: install guide: statement about uwsgi
** Also affects: glance/queens Importance: Undecided Status: New ** Changed in: glance/queens Milestone: None => queens-stable-1 ** Changed in: glance/queens Assignee: (unassigned) => Brian Rosmaita (brian-rosmaita) ** Changed in: glance/queens Status: New => Triaged ** Changed in: glance/queens Importance: Undecided => High ** Tags removed: queens-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/1751092 Title: install guide: statement about uwsgi Status in Glance: Fix Committed Status in Glance queens series: Triaged Bug description: Add a statement to the install guide that Glance does not currently support deployment under uwsgi. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1751092/+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 1732837] Re: weather applet crashes on logout
** 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/1732837 Title: weather applet crashes on logout Status in Glance: Invalid Bug description: weather applet crashes on logout To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1732837/+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 1759510] Re: Image import fails with python 3.5, image stuck in importing state
** Also affects: glance/queens Importance: Undecided Status: New ** Changed in: glance/queens 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/1759510 Title: Image import fails with python 3.5, image stuck in importing state Status in Glance: Fix Released Status in Glance queens series: New Bug description: New image import api with glance-direct or web-download fails to import image if cloud is using python3.5. Image stuck in importing state forever. Steps: 1. Ensure you are running glance on python 3.5 Add below lines in your devstack/local.conf WSGI_MODE=mod_wsgi USE_PYTHON3=True PYTHON3_VERSION=3.5 2. Source devstack/openrc using "$ source devstack/openrc admin admin" 3. Create image using new import api $ glance image-create-via-import --container-format ami --disk-format ami --name cirros_image --file g-api logs: Mar 28 08:36:01 ubuntu-3 glance-api[23449]: |__Flow 'api_image_import': TypeError: Unicode-objects must be encoded before hashing Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor Traceback (most recent call last): Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/usr/local/lib/python3.5/dist-packages/taskflow/engines/action_engine/executor.py", line 53, in _execute_task Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor result = task.execute(**arguments) Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/opt/stack/glance/glance/async/flows/api_image_import.py", line 218, in execute Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor image_import.set_image_data(image, file_path or self.uri, self.task_id) Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/opt/stack/glance/glance/common/scripts/image_import/main.py", line 154, in set_image_data Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor "task_id": task_id}) Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/usr/local/lib/python3.5/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor self.force_reraise() Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/usr/local/lib/python3.5/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor six.reraise(self.type_, self.value, self.tb) Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/usr/local/lib/python3.5/dist-packages/six.py", line 693, in reraise Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor raise value Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/opt/stack/glance/glance/common/scripts/image_import/main.py", line 146, in set_image_data Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor image.set_data(data_iter) Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/opt/stack/glance/glance/domain/proxy.py", line 195, in set_data Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor self.base.set_data(data, size) Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/opt/stack/glance/glance/notifier.py", line 480, in set_data Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor _send_notification(notify_error, 'image.upload', msg) Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/usr/local/lib/python3.5/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor self.force_reraise() Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/usr/local/lib/python3.5/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor six.reraise(self.type_, self.value, self.tb) Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/usr/local/lib/python3.5/dist-packages/six.py", line 693, in reraise Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor raise value Mar 28 08:36:01 ubuntu-3 glance-api[23449]: ERROR glance.async.taskflow_executor File "/opt/stack/glance/glance/notifier.py",
[Yahoo-eng-team] [Bug 1753964] Re: Image remains in queued state for web-download when node_staging_uri end with "/"
** Summary changed:
- Image remains in queued state for web-download when node_staging_uri uses
default value
+ Image remains in queued state for web-download when node_staging_uri end with
"/"
** Also affects: glance/queens
Importance: Undecided
Status: New
** Changed in: glance/queens
Importance: Undecided => High
** Changed in: glance/queens
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1753964
Title:
Image remains in queued state for web-download when node_staging_uri
end with "/"
Status in Glance:
In Progress
Status in Glance queens series:
Triaged
Bug description:
The node_staging_uri has a default of file:///tmp/staging/
see:
https://github.com/openstack/glance/blob/a0aaa614712090e7cab19dc35a155c32ea8f2190/glance/common/config.py#L680
If operator does not set 'node_staging_uri' in glance-api.conf then
importing image using web-download remains in queued state.
Steps to reproduce:
1. Ensure glance-api is running under mod_wsgi (add WSGI_MODE=mod_wsgi in
local.conf and run stack.sh)
2. Do not set node_staging_uri in glance-api.conf
3. Create image using below curl command:
curl -i -X POST -H "x-auth-token: "
http://192.168.0.13:9292/v2/images -d
'{"container_format":"bare","disk_format":"raw","name":"Import web-download"}'
4. Import image using below curl command:
curl -i -X POST -H "Content-type: application/json" -H "x-auth-token:
"
http://192.168.0.13:9292/v2/images//import -d
'{"method":{"name":"web-download","uri":"https://www.openstack.org/assets/openstack-logo/2016R/OpenStack-Logo-Horizontal.eps.zip"}}'
Expected result:
Image should be in active state.
Actual result:
Image remains in queued state.
API Logs:
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: DEBUG glance_store.backend [-]
Attempting to import store file {{(pid=3506) _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:231}}
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: DEBUG glance_store.capabilities
[-] Store glance_store._drivers.filesystem.Store doesn't support updating
dynamic storage capabilities. Please overwrite 'update_capabilities' method of
the store to implement updating logics if needed. {{(pid=3506)
update_capabilities
/usr/local/lib/python2.7/dist-packages/glance_store/capabilities.py:97}}
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: Traceback (most recent call last):
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/usr/local/lib/python2.7/dist-packages/eventlet/greenpool.py", line 82, in
_spawn_n_impl
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: func(*args, **kwargs)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/notifier.py", line 581, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: super(TaskProxy,
self).run(executor)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/domain/__init__.py", line 438, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]:
executor.begin_processing(self.task_id)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/async/taskflow_executor.py", line 144, in
begin_processing
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: super(TaskExecutor,
self).begin_processing(task_id)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/async/__init__.py", line 63, in begin_processing
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self._run(task_id, task.type)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/async/taskflow_executor.py", line 165, in _run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: flow = self._get_flow(task)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/async/taskflow_executor.py", line 134, in _get_flow
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: invoke_kwds=kwds).driver
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/usr/local/lib/python2.7/dist-packages/stevedore/driver.py", line 61, in
__init__
Mar 07 09:26:07 ubuntu-16 glance-api[3499]:
warn_on_missing_entrypoint=warn_on_missing_entrypoint
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/usr/local/lib/python2.7/dist-packages/stevedore/named.py", line 81, in
__init__
Mar 07 09:26:07
[Yahoo-eng-team] [Bug 1758943] [NEW] Image Import greates taskflow for impossible import scenarios
Public bug reported: When the image_import call is made the taskflow is created and responsible handling the rest of the request. It does not do any prechecks if the import conditions are met (like verifying that the image status transition would be possible. This will create lots of tasks that will end up to the database with no apparent reason. We should make at least basic status checks (like if "glance-direct" method was called agains non "uploading" status or "web-download" method used against non "queued" image) before creating the taskflow. ** Affects: glance Importance: High Status: New ** Affects: glance/queens Importance: High Status: New ** Affects: glance/rocky Importance: High Status: New ** Changed in: glance Importance: Undecided => High ** Also affects: glance/queens Importance: Undecided Status: New ** Also affects: glance/rocky Importance: High Status: New ** Changed in: glance/queens 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/1758943 Title: Image Import greates taskflow for impossible import scenarios Status in Glance: New Status in Glance queens series: New Status in Glance rocky series: New Bug description: When the image_import call is made the taskflow is created and responsible handling the rest of the request. It does not do any prechecks if the import conditions are met (like verifying that the image status transition would be possible. This will create lots of tasks that will end up to the database with no apparent reason. We should make at least basic status checks (like if "glance-direct" method was called agains non "uploading" status or "web-download" method used against non "queued" image) before creating the taskflow. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1758943/+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 1754634] Re: Image Import call does not honour enabled methods config option
** Also affects: glance/queens Importance: Undecided Status: New ** Changed in: glance/queens Status: New => In Progress ** Changed in: glance/queens Importance: Undecided => High ** Changed in: glance/queens Assignee: (unassigned) => Brian Rosmaita (brian-rosmaita) ** Changed in: glance/queens Importance: High => 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/1754634 Title: Image Import call does not honour enabled methods config option Status in Glance: Fix Released Status in Glance queens series: In Progress Bug description: Regardless what is configured import call will always accept all the methods. This means that for example one cannot turn 'web-download' method off if the image import feature is enabled. This can be easily corrected by changing the request de-serializer to check the method in the request against the config option rather than hardcoded list. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1754634/+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 1754634] [NEW] Image Import call does not honour enabled methods config option
Public bug reported: Regardless what is configured import call will always accept all the methods. This means that for example one cannot turn 'web-download' method off if the image import feature is enabled. This can be easily corrected by changing the request de-serializer to check the method in the request against the config option rather than hardcoded list. ** Affects: glance Importance: Critical Status: New ** 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/1754634 Title: Image Import call does not honour enabled methods config option Status in Glance: New Bug description: Regardless what is configured import call will always accept all the methods. This means that for example one cannot turn 'web-download' method off if the image import feature is enabled. This can be easily corrected by changing the request de-serializer to check the method in the request against the config option rather than hardcoded list. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1754634/+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 1753964] Re: Image remains in queued state for web-download if node_staging_uri is not set
So, the actual bug is invalid, there is clearly a bug in the side effect
though, which is it throwing 500.
The node_staging_uri is used as local cache for the taskflow to store
the data it downloads before the rest of the tasks are ran. So it is
needed for the 'web-download' (In 'web-download' only use case it does
not need to be shared between the glance nodes). If the methods are
incorrectly configured, the image should stay in 'queued' but we should
fail the import call gracefully.
** 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/1753964
Title:
Image remains in queued state for web-download if node_staging_uri is
not set
Status in Glance:
Invalid
Bug description:
If operator does not set 'node_staging_uri' in glance-api.conf then
importing image using web-download remains in queued state.
Steps to reproduce:
1. Ensure glance-api is running under mod_wsgi (add WSGI_MODE=mod_wsgi in
local.conf and run stack.sh)
2. Do not set node_staging_uri in glance-api.conf
3. Create image using below curl command:
curl -i -X POST -H "x-auth-token: "
http://192.168.0.13:9292/v2/images -d
'{"container_format":"bare","disk_format":"raw","name":"Import web-download"}'
4. Import image using below curl command:
curl -i -X POST -H "Content-type: application/json" -H "x-auth-token:
"
http://192.168.0.13:9292/v2/images//import -d
'{"method":{"name":"web-download","uri":"https://www.openstack.org/assets/openstack-logo/2016R/OpenStack-Logo-Horizontal.eps.zip"}}'
Expected result:
Image should be in active state.
Actual result:
Image remains in queued state.
API Logs:
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: DEBUG glance_store.backend [-]
Attempting to import store file {{(pid=3506) _load_store
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:231}}
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: DEBUG glance_store.capabilities
[-] Store glance_store._drivers.filesystem.Store doesn't support updating
dynamic storage capabilities. Please overwrite 'update_capabilities' method of
the store to implement updating logics if needed. {{(pid=3506)
update_capabilities
/usr/local/lib/python2.7/dist-packages/glance_store/capabilities.py:97}}
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: Traceback (most recent call last):
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/usr/local/lib/python2.7/dist-packages/eventlet/greenpool.py", line 82, in
_spawn_n_impl
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: func(*args, **kwargs)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/notifier.py", line 581, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: super(TaskProxy,
self).run(executor)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/domain/__init__.py", line 438, in run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]:
executor.begin_processing(self.task_id)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/async/taskflow_executor.py", line 144, in
begin_processing
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: super(TaskExecutor,
self).begin_processing(task_id)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/async/__init__.py", line 63, in begin_processing
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self._run(task_id, task.type)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/async/taskflow_executor.py", line 165, in _run
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: flow = self._get_flow(task)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/opt/stack/glance/glance/async/taskflow_executor.py", line 134, in _get_flow
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: invoke_kwds=kwds).driver
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/usr/local/lib/python2.7/dist-packages/stevedore/driver.py", line 61, in
__init__
Mar 07 09:26:07 ubuntu-16 glance-api[3499]:
warn_on_missing_entrypoint=warn_on_missing_entrypoint
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: File
"/usr/local/lib/python2.7/dist-packages/stevedore/named.py", line 81, in
__init__
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: verify_requirements)
Mar 07 09:26:07 ubuntu-16
[Yahoo-eng-team] [Bug 1749525] [NEW] Image Import leaves state transition to way too late stage
Public bug reported: On the Interoperable Image Import when the image-import call is made, the image status gets set to 'importing'. This happens on quite late state of the task flow and the previous steps may take some time. During this time the user is not informed that the import is actually happening and can either reissue the image-import call or stage call. ** Affects: glance Importance: Critical Assignee: Erno Kuvaja (jokke) Status: New ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance Importance: Undecided => High ** Changed in: glance Importance: High => Critical ** Changed in: glance Milestone: None => queens-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1749525 Title: Image Import leaves state transition to way too late stage Status in Glance: New Bug description: On the Interoperable Image Import when the image-import call is made, the image status gets set to 'importing'. This happens on quite late state of the task flow and the previous steps may take some time. During this time the user is not informed that the import is actually happening and can either reissue the image-import call or stage call. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1749525/+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 1748916] [NEW] Glance default workers is total overkill for modern servers
Public bug reported: On modern servers we do see dozens of cores which is total overkill of Glance workers while each of them has eventlet pool size of 1000 threads. Maybe we should consider limiting the total number of workers unless sepcifically configured by deployer. ** Affects: glance Importance: High Assignee: Erno Kuvaja (jokke) Status: New ** Changed in: glance Importance: Undecided => High ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1748916 Title: Glance default workers is total overkill for modern servers Status in Glance: New Bug description: On modern servers we do see dozens of cores which is total overkill of Glance workers while each of them has eventlet pool size of 1000 threads. Maybe we should consider limiting the total number of workers unless sepcifically configured by deployer. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1748916/+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 1748512] [NEW] web-download is subject to same port scan vulnerability as v1 copy_from
Public bug reported: The feature is currently at parr with v1 copy_from which means https://bugs.launchpad.net/glance/+bug/1606495 does apply as well. ** Affects: glance Importance: Critical Assignee: Erno Kuvaja (jokke) Status: In Progress ** Changed in: glance Importance: Undecided => Critical ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance Milestone: None => queens-rc2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1748512 Title: web-download is subject to same port scan vulnerability as v1 copy_from Status in Glance: In Progress Bug description: The feature is currently at parr with v1 copy_from which means https://bugs.launchpad.net/glance/+bug/1606495 does apply as well. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1748512/+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 1747926] [NEW] Import plugins requires deployer to poke Glance code with internal details
Public bug reported: To enable 3rd party import plugins deployer needs to touch glance/opts.py that is filled with internal details, thus making it risky for errors affecting the whole service. The plugin imports should be separated to their dedicated location for decoupling the details. ** Affects: glance Importance: Critical Assignee: Erno Kuvaja (jokke) Status: Triaged ** Changed in: glance Importance: Undecided => Critical ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Changed in: glance Milestone: None => queens-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1747926 Title: Import plugins requires deployer to poke Glance code with internal details Status in Glance: Triaged Bug description: To enable 3rd party import plugins deployer needs to touch glance/opts.py that is filled with internal details, thus making it risky for errors affecting the whole service. The plugin imports should be separated to their dedicated location for decoupling the details. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1747926/+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 1508442] Re: LOG.warn is deprecated
** No longer affects: glance -- 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/1508442 Title: LOG.warn is deprecated Status in anvil: New Status in Aodh: Fix Released Status in Astara: Fix Released Status in Barbican: Fix Released Status in bilean: Fix Released Status in Ceilometer: Fix Released Status in cloud-init: In Progress Status in cloudkitty: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in django-openstack-auth: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in Evoque: In Progress Status in gce-api: Fix Released Status in Gnocchi: Fix Released Status in OpenStack Heat: Fix Released Status in heat-cfntools: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in KloudBuster: Fix Released Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in masakari: Fix Released Status in Mistral: Invalid Status in Monasca: New Status in networking-arista: Fix Released Status in networking-calico: Fix Released Status in networking-cisco: In Progress Status in networking-fujitsu: Fix Released Status in networking-odl: Fix Committed Status in networking-ofagent: Fix Committed Status in networking-plumgrid: In Progress Status in networking-powervm: Fix Released Status in networking-vsphere: Fix Released Status in OpenStack Compute (nova): Fix Released Status in nova-powervm: Fix Released Status in nova-solver-scheduler: In Progress Status in octavia: Fix Released Status in openstack-ansible: Fix Released Status in oslo.cache: Fix Released Status in oslo.middleware: New Status in Packstack: Fix Released Status in python-dracclient: Fix Released Status in python-magnumclient: Fix Released Status in RACK: In Progress Status in python-watcherclient: In Progress Status in Rally: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in senlin: Fix Committed Status in shaker: Fix Released Status in Solum: Fix Released Status in tacker: Fix Released Status in tempest: Fix Released Status in tripleo: Fix Released Status in trove-dashboard: Fix Released Status in Vitrage: Fix Committed Status in watcher: Fix Released Status in zaqar: Fix Released Bug description: LOG.warn is deprecated in Python 3 [1] . But it still used in a few places, non-deprecated LOG.warning should be used instead. Note: If we are using logger from oslo.log, warn is still valid [2], but I agree we can switch to LOG.warning. [1]https://docs.python.org/3/library/logging.html#logging.warning [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85 To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1508442/+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 1695299] Re: Glance installation fails if password contains '@' symbol
** Changed in: glance
Status: New => In Progress
** Changed in: glance
Importance: Undecided => High
** Also affects: glance/pike
Importance: Undecided
Status: New
** Also affects: glance/queens
Importance: High
Assignee: Aizuddin Zali (mymzbe)
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/1695299
Title:
Glance installation fails if password contains '@' symbol
Status in Glance:
In Progress
Status in Glance pike series:
New
Status in Glance queens series:
In Progress
Bug description:
I was doing a fresh installation of devstack today and had set the
admin password as "Test@321" in local.conf file. The installation
started failing for Glance and when I had a look at the backtrace, it
looks like it converts '@' to '%40' and starts failing.
Either this needs to be fixed or proper note needs to be added in
devstack setup stating that one cannot use '@' symbol in passwords.
ubuntu@openstack:~/devstack$ glance --version
2.6.0
ubuntu@openstack:~/devstack$
CRITICAL glance [-] Unhandled error: ValueError: invalid interpolation syntax
in 'mysql+pymysql://root:Test%40321@127.0.0.1/glance?charset=utf8' at position
27
ERROR glance Traceback (most recent call last):
ERROR glance File "/usr/local/bin/glance-manage", line 10, in
ERROR glance sys.exit(main())
ERROR glance File "/opt/stack/glance/glance/cmd/manage.py", line 452, in
main
ERROR glance return CONF.command.action_fn()
ERROR glance File "/opt/stack/glance/glance/cmd/manage.py", line 291, in
sync
ERROR glance self.command_object.sync(CONF.command.version)
ERROR glance File "/opt/stack/glance/glance/cmd/manage.py", line 117, in
sync
ERROR glance alembic_migrations.place_database_under_alembic_control()
ERROR glance File
"/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/__init__.py", line
73, in place_database_under_alembic_control
ERROR glance a_config = get_alembic_config()
ERROR glance File
"/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/__init__.py", line
37, in get_alembic_config
ERROR glance config.set_main_option('sqlalchemy.url', str(engine.url))
ERROR glance File
"/usr/local/lib/python2.7/dist-packages/alembic/config.py", line 218, in
set_main_option
ERROR glance self.set_section_option(self.config_ini_section, name, value)
ERROR glance File
"/usr/local/lib/python2.7/dist-packages/alembic/config.py", line 245, in
set_section_option
ERROR glance self.file_config.set(section, name, value)
ERROR glance File "/usr/lib/python2.7/ConfigParser.py", line 752, in set
ERROR glance "position %d" % (value, tmp_value.find('%')))
ERROR glance ValueError: invalid interpolation syntax in
'mysql+pymysql://root:Test%40321@127.0.0.1/glance?charset=utf8' at position 27
ERROR glance
+lib/glance:init_glance:1 exit_trap
+./stack.sh:exit_trap:492 local r=1
++./stack.sh:exit_trap:493 jobs -p
+./stack.sh:exit_trap:493 jobs=
+./stack.sh:exit_trap:496 [[ -n '' ]]
+./stack.sh:exit_trap:502 kill_spinner
+./stack.sh:kill_spinner:388 '[' '!' -z '' ']'
+./stack.sh:exit_trap:504 [[ 1 -ne 0 ]]
+./stack.sh:exit_trap:505 echo 'Error on exit'
Error on exit
+./stack.sh:exit_trap:506 generate-subunit 1496417170 632
fail
+./stack.sh:exit_trap:507 [[ -z /opt/stack/logs ]]
+./stack.sh:exit_trap:510
/home/ubuntu/devstack/tools/worlddump.py -d /opt/stack/logs
World dumping... see /opt/stack/logs/worlddump-2017-06-02-153642.txt for
details
+./stack.sh:exit_trap:516 exit 1
ubuntu@openstack:~/devstack$
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1695299/+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 1665037] Re: Virtual size not computed when creating an image
As the images API reference states null is valid value for virtual_size. Glance does not promise on any image format or backend basis to provide virtual size as integer. ** Changed in: glance Status: In Progress => 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/1665037 Title: Virtual size not computed when creating an image Status in Glance: Invalid Bug description: $ qemu-img info dsl-4.11.rc2.qcow2 image: dsl-4.11.rc2.qcow2 file format: qcow2 virtual size: 50M (52824064 bytes) disk size: 50M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false Note that qemu-img reports that the virtual size of this qcow2 image is 50M. Now, let's create an image in Glance: $ glance image-create --name test --file dsl-4.11.rc2.iso --disk-format qcow2 --container-format bare +--+--+ | Property | Value| +--+--+ | checksum | 4b61c7892eefc23b71d4931bdcc3f1f1 | | container_format | bare | | created_at | 2017-02-15T16:45:07Z | | disk_format | qcow2| | id | 430da280-857a-4fe0-9447-a2b42bc24fe8 | | min_disk | 0| | min_ram | 0| | name | test | | owner| a645c608c70b4fecb7dc42f2bcddbc9a | | protected| False| | size | 52824064 | | status | active | | tags | [] | | updated_at | 2017-02-15T16:45:08Z | | virtual_size | None | | visibility | shared | +--+--+ Here, the virtual size is "None". This is not just a bug with displaying the values: mysql> use glance; ... mysql> select name, virtual_size from images where name='test' and deleted=0; +--+--+ | name | virtual_size | +--+--+ | test | NULL | +--+--+ The value is the "wrong" one in the database as well. The size is computed during the treatment of the PUT request, but the virtual size is never computed anywhere. This might be a job for glance_store though. The "_Introspect" flow does this computation, but since the task API has been deprecated, I do not think we should attempt to use this code. How should we fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1665037/+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 1533970] Re: NotFound exception of registry client should not show trace logs with ERROR
As Images API v1 has been deprecated since Newton release, this does not seem critical enough bug to address. https://docs.openstack.org/developer/glance/glanceapi.html#images-v1-api ** 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/1533970 Title: NotFound exception of registry client should not show trace logs with ERROR Status in Glance: Won't Fix Bug description: registry client shows trace logs when images are not found: = ERROR glance.registry.client.v1.client [req-fa5967e3-7ee8-4eb9-adc1-f6c4b152089f e4f950c8940da8fb3f1ac086e9550a35538da9d135813666495525abadaf9d8c 852967d9dcb34ac3ae16452f24f4e74c - - -] Registry client request GET /images/26e5f7a4-84d0-41fb-b5cb-bbf04af7d90f raised NotFound ERROR glance.registry.client.v1.client Traceback (most recent call last): ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/registry/client/v1/client.py", line 121, in do_request ERROR glance.registry.client.v1.client **kwargs) ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 71, in wrapped ERROR glance.registry.client.v1.client return func(self, *args, **kwargs) ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 375, in do_request ERROR glance.registry.client.v1.client headers=copy.deepcopy(headers)) ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 88, in wrapped ERROR glance.registry.client.v1.client return func(self, method, url, body, headers) ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 521, in _do_request ERROR glance.registry.client.v1.client raise exception.NotFound(res.read()) ERROR glance.registry.client.v1.client NotFound: 404 Not Found ERROR glance.registry.client.v1.client ERROR glance.registry.client.v1.client The resource could not be found. ERROR glance.registry.client.v1.client ERROR glance.registry.client.v1.client ERROR glance.registry.client.v1.client INFO eventlet.wsgi.server [req-fa5967e3-7ee8-4eb9-adc1-f6c4b152089f e4f950c8940da8fb3f1ac086e9550a35538da9d135813666495525abadaf9d8c 852967d9dcb34ac3ae16452f24f4e74c - - -] 100.72.17.170 - - [18/Nov/2015 10:26:12] "HEAD /v1/images/26e5f7a4-84d0-41fb-b5cb-bbf04af7d90f HTTP/1.1" 404 213 0.071243 = This is mostly caused by requests from Horizon. It requests deleted images to show instance details, and these logs show at every request. However, this is a relatively common case because users can delete old images even instances based on the images are running. (Of course, users can't create new instances based on these old images.) Logs should be both necessary and sufficient. Following HEAD shows 404 as INFO level, so I think one-line DEBUG is enough for this 404 error instead of trace logs. In the case of other status codes, registry client should show trace logs as ERROR. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1533970/+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 1654270] Re: Glance image not found should be logged as WARNING and not ERROR
As Images API v1 has been deprecated since Newton release, this does not seem critical enough bug to address. https://docs.openstack.org/developer/glance/glanceapi.html#images-v1-api ** 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/1654270 Title: Glance image not found should be logged as WARNING and not ERROR Status in Glance: Won't Fix Bug description: We refresh public glance images in our public cloud every month, and we set the old images to private. When you do: openstack server show uuid of course the instance knows the uuid of the glance image that was originally used to create the instance. We noticed that Horizon, to write on the web interface the description of the image used to start the instance, makes a lot of requests for public images that are not public anymore. This is okay, but the 404 is not logged as a WARNING, but as an ERROR with a long stack trace. This is 18 lines for each 404 and is poisoning our log files: 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client [req-334f1f81-c661-4dda-b69f-2e84b8a48acf 870aab4e3af6441b8b5ebfb0dcaa8412 8fcf0992e82943089de7dabe728b78fa - - -] Registry client request GET /images/b34f66bc-02ea-4125-b4ed-8eca7b90de5a raised NotFound 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client Traceback (most recent call last): 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/registry/client/v1/client.py", line 123, in do_request 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client **kwargs) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 70, in wrapped 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client return func(self, *args, **kwargs) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 373, in do_request 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client headers=copy.deepcopy(headers)) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 87, in wrapped 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client return func(self, method, url, body, headers) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 528, in _do_request 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client raise exception.NotFound(read_body(res)) 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client NotFound: 404 Not Found 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client The resource could not be found. 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client 2017-01-05 13:11:09.074 10475 ERROR glance.registry.client.v1.client To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1654270/+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 1585122] Re: Uploading image failed with affirmative log
** 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/1585122
Title:
Uploading image failed with affirmative log
Status in Glance:
Won't Fix
Bug description:
description:
When uploading image by the way of "copy-from" failed because of "Remote
server where the image is present is unavailable".The function return, the
process will work on and print the log like this:
"Uploaded data of image 952a0e62-500e-44fb-bbc4-f8cc17b5b6a4 from request
payload successfully"
That is unreasonable.
glance/api/v1/images.py
if copy_from:
try:
image_data, image_size = self._get_from_store(req.context, copy_from,
dest=store)
except Exception:
upload_utils.safe_kill(req, image_meta['id'], 'queued')
msg = (_LE("Copy from external source '%(scheme)s' failed for "
"image: %(image)s") % {'scheme': scheme, 'image':
image_meta['id']})
LOG.exception(msg)
return
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1585122/+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 1584415] Re: Listing images with the created_at and updated_at filters fails if an operator is not specified
** Also affects: glance/mitaka Importance: Medium Assignee: Castulo J. Martinez (castulo-martinez) Status: In Progress ** Also affects: glance/newton Importance: Undecided Status: New ** Changed in: glance/mitaka Status: In Progress => New ** Changed in: glance/newton Status: New => In Progress ** Changed in: glance/newton Importance: Undecided => Medium ** Changed in: glance/newton Assignee: (unassigned) => Castulo J. Martinez (castulo-martinez) ** Changed in: glance/mitaka Assignee: Castulo J. Martinez (castulo-martinez) => (unassigned) ** Changed in: glance/mitaka Importance: Medium => Undecided -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1584415 Title: Listing images with the created_at and updated_at filters fails if an operator is not specified Status in Glance: New Status in Glance mitaka series: New Status in Glance newton series: In Progress Bug description: When listing images there are several optional parameters that can be used to filter the list of images retrieved by the API. All those optional parameters are documented in the API guide: http://developer.openstack.org/api-ref-image-v2.html#listImages-v2. The following two parameters are not working properly when used, the created_at and the updated_at. Before the Mitaka release a user could filter the list of images by using the following options: GET /v2/images?created_at= GET /v2/images?updated_at= Starting on the Mitaka release users can also use an operator (eq, neq, lt, lte, gt, gte) for comparison purposes when filtering images using the created_at or updated_at parameters. Something like: GET /v2/images?created_at=: GET /v2/images?updated_at=: The problem is that starting on Mitaka, if the user tries to filter the list of images by created_at and updated_at without using an operator the API errors and fails to retrieve the list of images. This means that the API is not backward compatible with Liberty for this operation. The glance API should be able to work with backward compatibility with Liberty when listing images using the created_at or updated_at filters. Steps to recreate: 1) Using an environment with the Liberty release, try listing images using the created_at parameter (filter). Example: GET http://my_env:9292/v2/images?created_at=2016-05-20T20:53:15Z Results: A list containing one image is successfully retrieved. 2) Using an environment with the Mitaka release try the same operation: GET http://my_env:9292/v2/images?created_at=2016-05-20T20:53:15Z Results: The API returns an error: 400 Bad Request . Bad "created_at" query filter format. Use ISO 8601 DateTime notation. The same API call should be consistent in both releases. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1584415/+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 1587821] Re: Absolute formatting used in help texts
Nova seems to have the same issue (bit less visible): http://docs.openstack.org/developer/nova/sample_config.html F.E. config_drive_skip_versions ** Also affects: nova 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/1587821 Title: Absolute formatting used in help texts Status in Glance: In Progress Status in OpenStack Compute (nova): New Status in osprofiler: New Bug description: Absolute formatting breaks configgenerator generated example configs. Good example what happens is here: https://review.openstack.org/#/c/323661/1/etc/glance-api.conf The cache related options and [profiler] section helps gets broken due to line lenghts. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1587821/+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 1587821] [NEW] Absolute formatting used in help texts
Public bug reported: Absolute formatting breaks configgenerator generated example configs. Good example what happens is here: https://review.openstack.org/#/c/323661/1/etc/glance-api.conf The cache related options and [profiler] section helps gets broken due to line lenghts. ** Affects: glance Importance: Undecided Assignee: Erno Kuvaja (jokke) Status: In Progress ** Affects: osprofiler Importance: Undecided Status: New ** Changed in: glance Assignee: (unassigned) => Erno Kuvaja (jokke) ** Also affects: osprofiler 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/1587821 Title: Absolute formatting used in help texts Status in Glance: In Progress Status in osprofiler: New Bug description: Absolute formatting breaks configgenerator generated example configs. Good example what happens is here: https://review.openstack.org/#/c/323661/1/etc/glance-api.conf The cache related options and [profiler] section helps gets broken due to line lenghts. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1587821/+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 1568191] Re: Pre-defined VirtCPUTopology metadata should have the same name as flavor extra specs in nova
Seems that Nova is looking for wrong keys from image metadef when putting this information together. ** Also affects: nova 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/1568191 Title: Pre-defined VirtCPUTopology metadata should have the same name as flavor extra specs in nova Status in Glance: In Progress Status in OpenStack Compute (nova): New Bug description: If I understand correctly, the concept of flavor extra specs has been replaced by metadata. On nova/virt/hardware.py, it's checking for some specific flavor extra specs in _get_cpu_topology_constraints(). https://github.com/openstack/nova/blob/f396826314b9f37eb57151f0dd8a8e3b7d8a8a5c/nova/virt/hardware.py These specific flavor extra specs are included in the pre-defined metadata json so the user can load them with command "glance-manage db_load_metadefs". However, the names are not exactly the same. https://github.com/openstack/glance/blob/1c242032fbb26fed3a82691abb030583b4f8940b/etc/metadefs /compute-vcputopology.json To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1568191/+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 1552404] Re: glance.tests.integration.v2.test_tasks_api.TestTasksApi fails on mismatch
** Also affects: glance/mitaka Importance: Critical Status: Triaged ** Also affects: glance/newton Importance: Undecided Status: New ** Changed in: glance/newton Status: New => Triaged ** Changed in: glance/newton Importance: Undecided => Critical ** Changed in: glance/mitaka Assignee: (unassigned) => Fei Long Wang (flwang) ** Changed in: glance/newton Assignee: (unassigned) => Fei Long Wang (flwang) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1552404 Title: glance.tests.integration.v2.test_tasks_api.TestTasksApi fails on mismatch Status in Glance: Triaged Status in Glance mitaka series: Triaged Status in Glance newton series: Triaged Bug description: All glance master py27 test runs seems to be failing with following: ft64.6: glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_all_task_api_StringException: Traceback (most recent call last): File "glance/tests/integration/v2/test_tasks_api.py", line 172, in test_all_task_api self.assertEqual(expected_keys, set(task.keys())) File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 362, in assertEqual self.assertThat(observed, matcher, message) File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 447, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = set(['created_at', 'expires_at', 'id', 'owner', 'schema', 'self', 'status', 'type', 'updated_at']) actual= set([u'created_at', u'id', u'owner', u'schema', u'self', u'status', u'type', u'updated_at']) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1552404/+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 1555476] Re: image delete() doesn't catch exceptions.HasSnapshot() from rbd driver
** Changed in: glance Importance: Undecided => High ** Also affects: glance/mitaka Importance: High Assignee: Danny Al-Gaaf (danny-al-gaaf) 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/1555476 Title: image delete() doesn't catch exceptions.HasSnapshot() from rbd driver Status in Glance: In Progress Status in Glance mitaka series: In Progress Bug description: The glance_store driver raises a exceptions.HasSnapshot() if a image can't be deleted because it has a snapshot. This exception is ignored in glance/glance/api/v2/images.py. The code should raise at least a HTTPConflict and print a useful error message to the user. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1555476/+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 1556050] [NEW] enable_v3_api config option does not have effect
Public bug reported: As experimental v3 API was removed from glance in favor or running artifacts under it's own service glance-glare the enable_v3_api is not needed (nor effective anywhere). It was deprecated for removal at December when the code itself wasn't yet. We should remove the enable_v3_api that was there for the experimental api to avoid any confusion. ** Affects: glance Importance: High Assignee: Erno Kuvaja (jokke) 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/1556050 Title: enable_v3_api config option does not have effect Status in Glance: New Bug description: As experimental v3 API was removed from glance in favor or running artifacts under it's own service glance-glare the enable_v3_api is not needed (nor effective anywhere). It was deprecated for removal at December when the code itself wasn't yet. We should remove the enable_v3_api that was there for the experimental api to avoid any confusion. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1556050/+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 1508442] Re: LOG.warn is deprecated
Removed glance. We use oslo.log that has not deprecated the warn alias for warning. ** No longer affects: glance ** No longer affects: glance-store -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1508442 Title: LOG.warn is deprecated Status in anvil: In Progress Status in Aodh: Fix Released Status in Astara: Fix Released Status in Barbican: Fix Released Status in bilean: Fix Released Status in Blazar: In Progress Status in Ceilometer: Fix Released Status in cloud-init: In Progress Status in cloudkitty: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in django-openstack-auth: Fix Released Status in django-openstack-auth-kerberos: In Progress Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in Evoque: In Progress Status in gce-api: In Progress Status in Gnocchi: Fix Committed Status in heat: Fix Released Status in heat-cfntools: In Progress Status in OpenStack Identity (keystone): Fix Released Status in KloudBuster: Fix Released Status in kolla: Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: In Progress Status in networking-arista: In Progress Status in networking-calico: In Progress Status in networking-cisco: In Progress Status in networking-fujitsu: Fix Released Status in networking-odl: In Progress Status in networking-ofagent: In Progress Status in networking-plumgrid: In Progress Status in networking-powervm: Fix Released Status in networking-vsphere: In Progress Status in neutron: In Progress Status in OpenStack Compute (nova): In Progress Status in nova-powervm: Fix Released Status in nova-solver-scheduler: In Progress Status in octavia: Fix Released Status in openstack-ansible: In Progress Status in oslo.cache: Fix Released Status in Packstack: Fix Released Status in python-dracclient: Fix Released Status in python-magnumclient: Fix Released Status in RACK: In Progress Status in python-watcherclient: In Progress Status in shaker: In Progress Status in Solum: Fix Released Status in tempest: In Progress Status in tripleo: In Progress Status in trove-dashboard: Fix Released Status in watcher: Fix Released Status in zaqar: In Progress Bug description: LOG.warn is deprecated in Python 3 [1] . But it still used in a few places, non-deprecated LOG.warning should be used instead. Note: If we are using logger from oslo.log, warn is still valid [2], but I agree we can switch to LOG.warning. [1]https://docs.python.org/3/library/logging.html#logging.warning [2]https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85 To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1508442/+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
