[Yahoo-eng-team] [Bug 2027728] Re: Horizon npm test job failed with jQuery Version >3.x
** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/2027728 Title: Horizon npm test job failed with jQuery Version >3.x Status in OpenStack Dashboard (Horizon): Fix Released Bug description: After migrating xstatic-Jquery version >3.x horizon npm test job started failing [1] and [2]. There is also an open issue reported for this https://github.com/lorenzofox3/lrDragNDrop/issues/15 Horizon npm job fails with the below error msg: Firefox 102.0 (Linux x86_64) ERROR An error was thrown in afterAll TypeError: window.jQuery.event.props is undefined isJqueryEventDataTransfer@/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:5:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:8:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:184:3 Firefox 102.0 (Linux x86_64): Executed 645 of 645 ERROR (0 secs / 7.806 secs) Firefox 102.0 (Linux x86_64) ERROR An error was thrown in afterAll TypeError: window.jQuery.event.props is undefined isJqueryEventDataTransfer@/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:5:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:8:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:184:3 Firefox 102.0 (Linux x86_64): Executed 645 of 645 ERROR (8.359 secs / 7.806 secs) Coverage / Threshold summary = Statements : 100% ( 0/0 ) Threshold : 92% Branches : 100% ( 0/0 ) Threshold : 84% Functions: 100% ( 0/0 ) Threshold : 91% Lines: 100% ( 0/0 ) Threshold : 92% npm ERR! Test failed. See above for more details. [1] https://review.opendev.org/c/openstack/requirements/+/887933 [2] https://review.opendev.org/c/openstack/horizon/+/886867 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/2027728/+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 2036378] [NEW] Python3.11 unit test failures
Public bug reported: There are 7 VolumeBackup test failures with python3.11: FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_available - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_available_incremental - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_from_snapshot_table - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_from_snapshot_volume_table - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_in_use - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_in_use_incremental - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_in_use_incremental_set_false - re.error: global flags not at the start of the expression at position 1 ** Affects: horizon Importance: High Status: New ** Changed in: horizon Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/2036378 Title: Python3.11 unit test failures Status in OpenStack Dashboard (Horizon): New Bug description: There are 7 VolumeBackup test failures with python3.11: FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_available - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_available_incremental - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_from_snapshot_table - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_from_snapshot_volume_table - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_in_use - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_in_use_incremental - re.error: global flags not at the start of the expression at position 1 FAILED openstack_dashboard/dashboards/project/backups/tests.py::VolumeBackupsViewTests::test_create_backup_in_use_incremental_set_false - re.error: global flags not at the start of the expression at position 1 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/2036378/+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 2027728] [NEW] Horizon npm test job failed with jQuery Version >3.x
Public bug reported: After migrating xstatic-Jquery version >3.x horizon npm test job started failing [1] and [2]. There is also an open issue reported for this https://github.com/lorenzofox3/lrDragNDrop/issues/15 Horizon npm job fails with the below error msg: Firefox 102.0 (Linux x86_64) ERROR An error was thrown in afterAll TypeError: window.jQuery.event.props is undefined isJqueryEventDataTransfer@/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:5:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:8:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:184:3 Firefox 102.0 (Linux x86_64): Executed 645 of 645 ERROR (0 secs / 7.806 secs) Firefox 102.0 (Linux x86_64) ERROR An error was thrown in afterAll TypeError: window.jQuery.event.props is undefined isJqueryEventDataTransfer@/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:5:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:8:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:184:3 Firefox 102.0 (Linux x86_64): Executed 645 of 645 ERROR (8.359 secs / 7.806 secs) Coverage / Threshold summary = Statements : 100% ( 0/0 ) Threshold : 92% Branches : 100% ( 0/0 ) Threshold : 84% Functions: 100% ( 0/0 ) Threshold : 91% Lines: 100% ( 0/0 ) Threshold : 92% npm ERR! Test failed. See above for more details. [1] https://review.opendev.org/c/openstack/requirements/+/887933 [2] https://review.opendev.org/c/openstack/horizon/+/886867 ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/2027728 Title: Horizon npm test job failed with jQuery Version >3.x Status in OpenStack Dashboard (Horizon): New Bug description: After migrating xstatic-Jquery version >3.x horizon npm test job started failing [1] and [2]. There is also an open issue reported for this https://github.com/lorenzofox3/lrDragNDrop/issues/15 Horizon npm job fails with the below error msg: Firefox 102.0 (Linux x86_64) ERROR An error was thrown in afterAll TypeError: window.jQuery.event.props is undefined isJqueryEventDataTransfer@/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:5:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:8:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:184:3 Firefox 102.0 (Linux x86_64): Executed 645 of 645 ERROR (0 secs / 7.806 secs) Firefox 102.0 (Linux x86_64) ERROR An error was thrown in afterAll TypeError: window.jQuery.event.props is undefined isJqueryEventDataTransfer@/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:5:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:8:9 @/home/zuul/src/opendev.org/openstack/horizon/.tox/npm/lib/python3.9/site-packages/xstatic/pkg/angular_lrdragndrop/data/lrdragndrop.js:184:3 Firefox 102.0 (Linux x86_64): Executed 645 of 645 ERROR (8.359 secs / 7.806 secs) Coverage / Threshold summary = Statements : 100% ( 0/0 ) Threshold : 92% Branches : 100% ( 0/0 ) Threshold : 84% Functions: 100% ( 0/0 ) Threshold : 91% Lines: 100% ( 0/0 ) Threshold : 92% npm ERR! Test failed. See above for more details. [1] https://review.opendev.org/c/openstack/requirements/+/887933 [2] https://review.opendev.org/c/openstack/horizon/+/886867 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/2027728/+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 1996274] Re: Horizon: Monitoring > Overview error display AttributeError at /monitoring/
It looks like a bug of moansaca-ui, please report it there [1]. [1] https://storyboard.openstack.org/#!/project/openstack/monasca-ui ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1996274 Title: Horizon: Monitoring > Overview error display AttributeError at /monitoring/ Status in OpenStack Dashboard (Horizon): Invalid Bug description: I'm trying to be able to see the overview tab for monitoring. I get errors like the attachment: To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1996274/+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 1996638] Re: horizon-nodejs16/18-run-test job failing in Ubuntu Jammy (22.04)
Fixed by https://review.opendev.org/c/openstack/horizon/+/865453 ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1996638 Title: horizon-nodejs16/18-run-test job failing in Ubuntu Jammy (22.04) Status in OpenStack Dashboard (Horizon): Fix Released Bug description: As per the 2023.1 cycles community-wide goal of migrating the CI/CD to Ubuntu Jammy (22.04), we are testing all jobs in advance before the actual migration happens on m-1 (Nov 18). horizon-nodejs16-run-test, horizon-selenium-headless, horizon-integration-tests jobs are failing on Jammy - https://zuul.opendev.org/t/openstack/build/bbdfff9573894d469d7394a4da4c4274/log/job-output.txt#2564-2584 I guess we are hitting bug https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/ I have already discussed this topic with openstack-infra team, please refer https://meetings.opendev.org/irclogs/%23openstack-infra/%23openstack-infra.2022-11-09.log.html#t2022-11-09T17:27:06 Right now if we migrate nodeset of "horiozon-nodejs16-run-test" job from focal->jammy, it will be broken and all other horizon plugins which are running this job are also broken [1]. [1] https://codesearch.openstack.org/?q=horizon-nodejs- jobs=nope=nope=== To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1996638/+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 1999519] Re: Typo in French translation concerning admin state
This issue needs to be fixed in https://translate.openstack.org/ That's why marked it as invalid for the horizon. If you like to know more about the process of how translation happens, please refer https://docs.openstack.org/i18n/latest/ ** Project changed: horizon => openstack-i18n ** Also affects: horizon Importance: Undecided Status: New ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1999519 Title: Typo in French translation concerning admin state Status in OpenStack Dashboard (Horizon): Invalid Status in openstack i18n: New Bug description: In horizon we can read in the French translation: Etat administateur instead of Etat administrateur (a 'r' is missing). cf https://opendev.org/openstack/horizon/src/branch/master/openstack_dashboard/locale/fr/LC_MESSAGES/django.po#L498 --- openstack_dashboard/locale/fr/LC_MESSAGES/django.po.ori 2022-12-13 14:02:08.865183595 +0100 +++ openstack_dashboard/locale/fr/LC_MESSAGES/django.po 2022-12-13 14:00:29.410016035 +0100 @@ -495,7 +495,7 @@ msgstr "Mot de Passe Administrateur" msgid "Admin State" -msgstr "État Administateur" +msgstr "État Administrateur" msgid "Admin State =" msgstr "État Admin =" To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1999519/+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 1996638] [NEW] horizon-nodejs16/18-run-test job failing in Ubuntu Jammy (22.04)
Public bug reported: As per the 2023.1 cycles community-wide goal of migrating the CI/CD to Ubuntu Jammy (22.04), we are testing all jobs in advance before the actual migration happens on m-1 (Nov 18). horizon-nodejs16-run-test job is failing on Jammy - https://zuul.opendev.org/t/openstack/build/bbdfff9573894d469d7394a4da4c4274/log/job-output.txt#2564-2584 I guess we are hitting bug https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/ I have already discussed this topic with openstack-infra team, please refer https://meetings.opendev.org/irclogs/%23openstack-infra/%23openstack-infra.2022-11-09.log.html#t2022-11-09T17:27:06 Right now if we migrate nodeset of "horiozon-nodejs16-run-test" job from focal->jammy, it will be broken and all other horizon plugins which are running this job are also broken [1]. [1] https://codesearch.openstack.org/?q=horizon-nodejs- jobs=nope=nope=== ** Affects: horizon Importance: High Status: New ** Changed in: horizon Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1996638 Title: horizon-nodejs16/18-run-test job failing in Ubuntu Jammy (22.04) Status in OpenStack Dashboard (Horizon): New Bug description: As per the 2023.1 cycles community-wide goal of migrating the CI/CD to Ubuntu Jammy (22.04), we are testing all jobs in advance before the actual migration happens on m-1 (Nov 18). horizon-nodejs16-run-test job is failing on Jammy - https://zuul.opendev.org/t/openstack/build/bbdfff9573894d469d7394a4da4c4274/log/job-output.txt#2564-2584 I guess we are hitting bug https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/ I have already discussed this topic with openstack-infra team, please refer https://meetings.opendev.org/irclogs/%23openstack-infra/%23openstack-infra.2022-11-09.log.html#t2022-11-09T17:27:06 Right now if we migrate nodeset of "horiozon-nodejs16-run-test" job from focal->jammy, it will be broken and all other horizon plugins which are running this job are also broken [1]. [1] https://codesearch.openstack.org/?q=horizon-nodejs- jobs=nope=nope=== To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1996638/+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 1921388] Re: novaclient logs are logged as keystoneauth.session
** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1921388 Title: novaclient logs are logged as keystoneauth.session Status in OpenStack Dashboard (Horizon): Fix Released Status in python-novaclient: Fix Released Bug description: This is possibly as old as Train, but I only just noticed this when I tried to debug something. All logs that should be logged as novaclient, instead get logged as keystoneauth.session — this means we can't easily configure the log level for novaclient, and makes it hard to search the logs. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1921388/+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 1965969] [NEW] Panel Under Identity dashboard except Application Credentials doesn't works
Public bug reported: Panels Under Identity dashboard like Domains/Projects/Users/Groups/Roles failed with error msg "Invalid service catalog: identity". It happens after devstack stops creating the Identity admin endpoint [1]. [1] https://opendev.org/openstack/devstack/commit/65a5db8e3376fbeb6871629cbfe5d77fe848e039. Steps to reproduce this bug are below: 1. Update your devstack env. to the latest. 2. Open any panel under Identity dashboard except 'Application Credentials' and you will hit the error "Invalid service catalog: identity" ** Affects: horizon Importance: Critical Status: New ** Changed in: horizon Importance: Undecided => Critical ** Description changed: Panels Under Identity dashboard like Domains/Projects/Users/Groups/Roles failed with error msg "Invalid service catalog: identity". It happens after devstack stops creating the Identity admin endpoint [1]. [1] https://opendev.org/openstack/devstack/commit/65a5db8e3376fbeb6871629cbfe5d77fe848e039. Steps to reproduce this bug are below: - 1. Update your devstack env. to the latest. - 2. Open any panel under Identity dashboard except 'Application Credentials' and you will -hit the error "Invalid service catalog: identity" + 2. Open any panel under Identity dashboard except 'Application Credentials' and +you will hit the error "Invalid service catalog: identity" -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1965969 Title: Panel Under Identity dashboard except Application Credentials doesn't works Status in OpenStack Dashboard (Horizon): New Bug description: Panels Under Identity dashboard like Domains/Projects/Users/Groups/Roles failed with error msg "Invalid service catalog: identity". It happens after devstack stops creating the Identity admin endpoint [1]. [1] https://opendev.org/openstack/devstack/commit/65a5db8e3376fbeb6871629cbfe5d77fe848e039. Steps to reproduce this bug are below: 1. Update your devstack env. to the latest. 2. Open any panel under Identity dashboard except 'Application Credentials' and you will hit the error "Invalid service catalog: identity" To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1965969/+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 1928547] Re: Install and configure for openSUSE and SUSE Linux Enterprise in horizon
It is fixed by https://review.opendev.org/c/openstack/horizon/+/825254 ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1928547 Title: Install and configure for openSUSE and SUSE Linux Enterprise in horizon Status in OpenStack Dashboard (Horizon): Fix Released Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: OPENSTACK_KEYSTONE_URL = "http://%s/identity/v3; % OPENSTACK_HOST - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. OPENSTACK_KEYSTONE_URL = "http://%s:5000/v3; % OPENSTACK_HOST If you have a troubleshooting or support issue, use the following resources: - The mailing list: https://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 19.2.1.dev2 on 2021-01-02 14:56:33 SHA: 6745c8c62b246714fcda2bd65eacb3f9e95541c6 Source: https://opendev.org/openstack/horizon/src/doc/source/install/install-obs.rst URL: https://docs.openstack.org/horizon/wallaby/install/install-obs.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1928547/+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 1962488] Re: Show X-FORWARDED-FOR IP address if login failed
Looking at comment #4 of this bug. So Changing its status to invalid. ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1962488 Title: Show X-FORWARDED-FOR IP address if login failed Status in OpenStack Dashboard (Horizon): Invalid Bug description: Failed login syslog message shows the internal IP address from ha- proxy, not the real IP of the client. Tested via: horizon-21.2.6 Message sent to syslog on a failed login: httpd[4218]: [wsgi:error] [pid 4218] [remote 192.168.17.12:59680] Login failed for user "aa" using domain "default", remote address 192.168.17.12. (192.168.17.12 is the internal ha-proxy address) I couldn't find a filed bug or anything related, the error message is generated in openstack_auth/forms.py in "def clean(self)". Please let me know if there is a workaround for it, or if I should see to get a patch together to get the real client IP address into the log file. thx To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1962488/+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 1958290] [NEW] Horizon doc job fails with sphinx 4.4.0 version
Public bug reported: After openstack/requirements bump the Sphinx version to 4.4.0 from 4.3.2 by [1]. horizon doc job starts failing with error [2]. I think it is a new feature added in sphinx version 4.4.0 https://github.com/sphinx-doc/sphinx/pull/9800 which causes the failure. [1] https://review.opendev.org/c/openstack/requirements/+/825031 [2] https://paste.opendev.org/show/812198/ ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1958290 Title: Horizon doc job fails with sphinx 4.4.0 version Status in OpenStack Dashboard (Horizon): New Bug description: After openstack/requirements bump the Sphinx version to 4.4.0 from 4.3.2 by [1]. horizon doc job starts failing with error [2]. I think it is a new feature added in sphinx version 4.4.0 https://github.com/sphinx-doc/sphinx/pull/9800 which causes the failure. [1] https://review.opendev.org/c/openstack/requirements/+/825031 [2] https://paste.opendev.org/show/812198/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1958290/+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 1958291] [NEW] Horizon doc job fails with sphinx 4.4.0 version
Public bug reported: After openstack/requirements bump the Sphinx version to 4.4.0 from 4.3.2 by [1]. horizon doc job starts failing with error [2]. I think it is a new feature added in sphinx version 4.4.0 https://github.com/sphinx-doc/sphinx/pull/9800 which causes the failure. [1] https://review.opendev.org/c/openstack/requirements/+/825031 [2] https://paste.opendev.org/show/812198/ ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1958291 Title: Horizon doc job fails with sphinx 4.4.0 version Status in OpenStack Dashboard (Horizon): New Bug description: After openstack/requirements bump the Sphinx version to 4.4.0 from 4.3.2 by [1]. horizon doc job starts failing with error [2]. I think it is a new feature added in sphinx version 4.4.0 https://github.com/sphinx-doc/sphinx/pull/9800 which causes the failure. [1] https://review.opendev.org/c/openstack/requirements/+/825031 [2] https://paste.opendev.org/show/812198/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1958291/+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 1957173] [NEW] Horizon uses wrong value of OPENSTACK_KEYSTONE_DEFAULT_ROLE
Public bug reported: Horizon uses '_member_' as default value of OPENSTACK_KEYSTONE_DEFAULT_ROLE. So if a user tries to create a new project leads to "horizon.exceptions.NotFound: Could not find default role '_member_' in Keystone" [1] error. horizon must use OPENSTACK_KEYSTONE_DEFAULT_ROLE = 'member' to fix it. [1] https://paste.opendev.org/show/812074/ ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1957173 Title: Horizon uses wrong value of OPENSTACK_KEYSTONE_DEFAULT_ROLE Status in OpenStack Dashboard (Horizon): New Bug description: Horizon uses '_member_' as default value of OPENSTACK_KEYSTONE_DEFAULT_ROLE. So if a user tries to create a new project leads to "horizon.exceptions.NotFound: Could not find default role '_member_' in Keystone" [1] error. horizon must use OPENSTACK_KEYSTONE_DEFAULT_ROLE = 'member' to fix it. [1] https://paste.opendev.org/show/812074/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1957173/+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 1957056] Re: project fliter of admin volumes
*** This bug is a duplicate of bug 1941186 *** https://bugs.launchpad.net/bugs/1941186 Hi, it is fixed by https://review.opendev.org/c/openstack/horizon/+/808517 in the master branch. I can purpose a cherry-pick to stable/wallaby and stable/xena branches. ** This bug has been marked a duplicate of bug 1941186 Admin Volume table doesn't work if you use 'Project' filter -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1957056 Title: project fliter of admin volumes Status in OpenStack Dashboard (Horizon): New Bug description: Hello, Release Wallaby and Xena When we use filter "project" in Admin -> Volumes, Horizon crushes with error: ``` ERROR horizon.tables.base Error while rendering table rows. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 1932, in get_rows row = self._meta.row_class(self, datum) File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 589, in __init__ self.load_cells() File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 618, in load_cells cell = table._meta.cell_class(datum, column, self) File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 739, in __init__ self.data = self.get_data(datum, column, row) File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 783, in get_data data = column.get_data(datum) File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 423, in get_data data = self.get_raw_data(datum) File "/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/volumes/tables.py", line 432, in get_raw_data group = volume.group File "/usr/share/openstack-dashboard/openstack_dashboard/api/base.py", line 139, in __getattribute__ return object.__getattribute__(self, attr) AttributeError: 'Volume' object has no attribute 'group' ERROR django.request Internal Server Error: /dashboard/admin/volumes/ Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 1932, in get_rows row = self._meta.row_class(self, datum) File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 589, in __init__ self.load_cells() File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 618, in load_cells cell = table._meta.cell_class(datum, column, self) File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 739, in __init__ self.data = self.get_data(datum, column, row) File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 783, in get_data data = column.get_data(datum) File "/usr/lib/python3.6/site-packages/horizon/tables/base.py", line 423, in get_data data = self.get_raw_data(datum) File "/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/volumes/tables.py", line 432, in get_raw_data group = volume.group File "/usr/share/openstack-dashboard/openstack_dashboard/api/base.py", line 139, in __getattribute__ return object.__getattribute__(self, attr) AttributeError: 'Volume' object has no attribute 'group' ``` After that, this page opens only after clearing the cache. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1957056/+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 1792028] Re: openstack_dashboard.test.integration_tests.tests.test_router tests failed o gates
This bug is fixed by https://review.opendev.org/c/openstack/horizon/+/685208 . ** Changed in: horizon Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1792028 Title: openstack_dashboard.test.integration_tests.tests.test_router tests failed o gates Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Logs are available here: http://paste.openstack.org/show/729899/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1792028/+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 1462493] Re: when cinder isn't using default quota class, quotas cannot be updated through Horizon
Oops, I have pasted comments for some other bug in this bug summary, please ignore my above comment. ** Changed in: horizon Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1462493 Title: when cinder isn't using default quota class, quotas cannot be updated through Horizon Status in OpenStack Dashboard (Horizon): Confirmed Bug description: To re-create: edit cinder.conf so that use_default_quota_class=false restart cinder. Attempt to edit cinder related values through Horizon, such as Volumes, Volume Snapshots, or Total Size of Volumes and Snapshots (GB) although it appears the edits succeed, they actually don't. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1462493/+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 1462493] Re: when cinder isn't using default quota class, quotas cannot be updated through Horizon
It is fixed by https://review.opendev.org/c/openstack/horizon/+/685208 ** Changed in: horizon Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1462493 Title: when cinder isn't using default quota class, quotas cannot be updated through Horizon Status in OpenStack Dashboard (Horizon): Confirmed Bug description: To re-create: edit cinder.conf so that use_default_quota_class=false restart cinder. Attempt to edit cinder related values through Horizon, such as Volumes, Volume Snapshots, or Total Size of Volumes and Snapshots (GB) although it appears the edits succeed, they actually don't. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1462493/+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 1928953] Re: Volume uuid of deleted volume is visible in volume list while restoring volume backup in horizon.
** Project changed: cinder => horizon ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1928953 Title: Volume uuid of deleted volume is visible in volume list while restoring volume backup in horizon. Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Issue: When I deleted a volume and try to restore a backup of same volume which I deleted , the selected value in drop-down shows the UUID of volume which lead to problem. Analysis: When I checked the code and found that the value of volume UUID is picked from backup, but volume is not present anymore in the cloud. The default value is set by this block of code: https://github.com/openstack/horizon/blob/2d2f944e2fe127433f2973ef77ba86ec997cf434/horizon/forms/fields.py#L303 the template used here for rendering: https://github.com/openstack/horizon/blob/master/horizon/templates/horizon/common/fields/_themable_select.html#L5 Code block responsible for choices of available volume: https://github.com/openstack/horizon/blob/stable/train/openstack_dashboard/dashboards/project/backups/forms.py#L107 Steps to reproduce: 1. create a volume backup let's say vol 2. create backup 'backup' of volume 'vol' 3. delete the volume 'vol' 4. now restore backup 'back' A list of all available volume is shown, but the UUID of deleted volume 'vol' is also present in the list. Actual: UUID of deleted volume is visible in the list Expected: Volume UUID of deleted should not be present Proposed Solution: If initial_value is not present in choices then take the first value of choices. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1928953/+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 1950659] [NEW] Horizon Integration tests Fails after devstack sop creating a keystone admin endpoint by default
Public bug reported: Some horizon integration tests[1] start failing after devstack stops creating default keystone admin endpoint[2]. [1] https://paste.openstack.org/show/810942/ [2] https://review.opendev.org/c/openstack/devstack/+/777345 ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1950659 Title: Horizon Integration tests Fails after devstack sop creating a keystone admin endpoint by default Status in OpenStack Dashboard (Horizon): New Bug description: Some horizon integration tests[1] start failing after devstack stops creating default keystone admin endpoint[2]. [1] https://paste.openstack.org/show/810942/ [2] https://review.opendev.org/c/openstack/devstack/+/777345 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1950659/+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 1947847] [NEW] Horizon selenium-headless/integration-tests job start failing after updating selenium version to4.0.0
Public bug reported: After Updating the selenium version to 4.0.0 from 3.141.0 horizon selenium-headless and integration tests start failing. More Error logs can be found here https://paste.opendev.org/show/810092/ ** Affects: horizon Importance: High Status: New ** Changed in: horizon Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1947847 Title: Horizon selenium-headless/integration-tests job start failing after updating selenium version to4.0.0 Status in OpenStack Dashboard (Horizon): New Bug description: After Updating the selenium version to 4.0.0 from 3.141.0 horizon selenium-headless and integration tests start failing. More Error logs can be found here https://paste.opendev.org/show/810092/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1947847/+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 1709765] Re: Failed to create keypair in ng create instance form when the quota exceeded
It is fixed by https://review.opendev.org/c/openstack/horizon/+/677580 ** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1709765 Title: Failed to create keypair in ng create instance form when the quota exceeded Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In ng create instance form, we can create and import keypair, keypair has quota management, when the keypair quota exceeded, if we create or import keypair, it will fail and the API will return "Quota exceeded, too many key pairs. (HTTP 403) (Request-ID: req-841e0499-ae34-4029-9a2f-04a5a6d3e3f7)" We should like keypairs panel to add quota check in ng create instance keypair tab page. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1709765/+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 1600004] Re: UX: Inconsistent table color in Flavor Popover
it is fixed by https://review.openstack.org/#/c/534602/ ** Changed in: horizon Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/164 Title: UX: Inconsistent table color in Flavor Popover Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Looks like tr:hover bgcolor attributes are propagated to a child table that exists in a popover shown when user clicks on flavor name. How to reproduce: 1) Go to Project->Instances 2) Locate Size Column (Flavor) 3) Click on Flavor Name. 4) Mouse over and out some of the table rows and see how the table that shows "Flavor Details" changes its background color. See screenshots: 1. http://pasteboard.co/8JUQd3oMS.png 2. http://pasteboard.co/8JWTGTYde.png Note: this behavior is more notorious when seeing a flavor detail of a row with class "even" (tr.even). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/164/+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 1941186] [NEW] Admin Volume table doesn't work if you use 'Project' filter
Public bug reported: If you use 'Project' filter in the admin volume table then horizon broke with "TemplateSyntaxError at /admin/volumes/" on UI. More detailed error message cand be found here https://paste.opendev.org/show/808303/ ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1941186 Title: Admin Volume table doesn't work if you use 'Project' filter Status in OpenStack Dashboard (Horizon): New Bug description: If you use 'Project' filter in the admin volume table then horizon broke with "TemplateSyntaxError at /admin/volumes/" on UI. More detailed error message cand be found here https://paste.opendev.org/show/808303/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1941186/+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 1921448] Re: Release Note containing possible typo
** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1921448 Title: Release Note containing possible typo Status in OpenStack Dashboard (Horizon): Fix Released Bug description: While translating, I've come across the following sentence which I could not comprehend: ``Users`` tab displaying all users which have roles on the project (and their roles on it), including users which have roles on the project throw their membership to a group. Found the source here: https://github.com/openstack/horizon/blob/73f6dcebd5d81133f2604fa224f572e46da443df/releasenotes/notes/bug-1785263-46edf7313d833b4c.yaml Is "throw" possibly a typo for "through"? If so, my interpretation is as below. Could you please confirm if I understand it correctly? ``Users`` tab now displays all users who have roles in the project, as well as their roles in the project. This includes users who have roles in the project through their membership to a group. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1921448/+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 1874705] Re: Websso fails when HTTP_REFERRER that horizon is unable to connect to gets used
** Also affects: keystone Importance: Undecided Status: New -- 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/1874705 Title: Websso fails when HTTP_REFERRER that horizon is unable to connect to gets used Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (keystone): New Bug description: I am currently having an issue where a request to Horizon's websso endpoint fails to respond in time as the token validation request fails to connect between Horizon and Keystone. (On Openstack Train) I am trying to login to Horizon using an external identity provider. I have set the WEBSSO_KEYSTONE_URL to keystones external facing endpoint as the IDP is on an external network. The POST request to https://horizon_ip/auth/websso/ that includes a keystone token for validation in its params is failing. This request routes to the horizon view 'websso' (https://opendev.org/openstack/horizon/src/branch/master/openstack_auth/views.py#L165) The token authentication request to keystone in this view uses the requests HTTP_REFERRER when available as the keystone endpoint to use. The previous request was to keystone on its external endpoint (as used by the external identity provider) to its route 'auth/OS-FEDERATION/websso/openid', and therefore the HTTP_REFERRER for this POST request is the external keystone endpoint. Our Openstack services have minimal external connectivity for security reasons. So in our setup the horizon service is unable to make connections to the external keystone endpoint. Therefore in the horizon apache logs I see: Unable to establish connection to https://keystone_external_ip:5000/v3/auth/tokens Which eventually leads to a time out. As this is request between Horizon and Keystone ideally for us it should be using the internal endpoint. I've had a go at setting the auth_url to be settings.OPENSTACK_KEYSTONE_URL and this lets me login successfully. I am unsure as to why the HTTP_REFERRER gets used in preference over the settings.OPENSTACK_KEYSTONE_URL for this request? I propose either: 1. Removing the use of HTTP_REFERRER in favor of settings.OPENSTACK_KEYSTONE_URL. 2. Providing a setting to toggle between using the HTTP_REFERRER or settings.OPENSTACK_KEYSTONE_URL to build the auth request with. Original commit in django_openstack_auth for websso view: https://github.com/openstack/django_openstack_auth/commit/302f422568a32b513ffbb3089ba799a4416df108 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1874705/+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 1930551] Re: Instance image assumes that volume's image metadata exists
Hi, looks like you are not using the horizon master branch. This bug is
already fixed by
https://review.opendev.org/c/openstack/horizon/+/777654.
Feel free to backport it if you are using an old branch.
** Changed in: horizon
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1930551
Title:
Instance image assumes that volume's image metadata exists
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
When I access an instance through /project/instance/${(ID), the
dashboard always show an error notification with message: Failed to
get attached volume.
The instance is working fine and the volume can be verified through openstack
cli.
A quick grep for the error message shows the below code path in which, the
instance.image processing in the Try path makes an assumption that volume
metadata always exists. This is not the case when the volume was created with
"no source, empty source" as Volume Source.
Also there is no logging code in this code path, so although we see
the error in dashboard, we don't find any log message that can
indicate the issue.
class OverviewTab(tabs.Tab):
name = _("Overview")
slug = "overview"
template_name = ("project/instances/"
"_detail_overview.html")
def get_context_data(self, request):
instance = self.tab_group.kwargs['instance']
if instance.volumes and not instance.image:
try:
volume = api.cinder.volume_get(
self.request, volume_id=instance.volumes[0].volumeId)
instance.image = {
'id': volume.volume_image_metadata['image_id'],
'name': volume.volume_image_metadata['image_name']}
except Exception:
exceptions.handle(self.request,
_('Failed to get attached volume.'))
return {"instance": instance}
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1930551/+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 1930563] Re: oslopolicy-convert-json-to-yaml
Hi, Could you please check the format of policy files under ``POLICY_FILES`` [1] for both nodes. looking at the logs for the first node you are using '.json' format that's why you are seeing those deprecation warnings and for node2 maybe you are using '.yaml' format that's why you are only seeing specific deprecation warning for different backends services. [1] https://github.com/openstack/horizon/tree/master/openstack_dashboard/conf ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1930563 Title: oslopolicy-convert-json-to-yaml Status in OpenStack Dashboard (Horizon): Invalid Bug description: The error in node1 is as follows: [Wed Jun 02 16:00:32.837954 2021] [wsgi:error] [pid 361523:tid 140707810875136] [remote 10.80.0.229:61350] WARNING oslo_policy.policy JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [Wed Jun 02 16:00:33.096518 2021] [wsgi:error] [pid 361523:tid 140707810875136] [remote 10.80.0.229:61350] WARNING oslo_policy.policy JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [Wed Jun 02 16:00:33.109075 2021] [wsgi:error] [pid 361523:tid 140707810875136] [remote 10.80.0.229:61350] WARNING oslo_policy.policy JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [Wed Jun 02 16:00:33.116617 2021] [wsgi:error] [pid 361523:tid 140707810875136] [remote 10.80.0.229:61350] WARNING oslo_policy.policy JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [Wed Jun 02 16:00:33.140800 2021] [wsgi:error] [pid 361523:tid 140707810875136] [remote 10.80.0.229:61350] WARNING oslo_policy.policy JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [Wed Jun 02 16:00:33.147785 2021] [wsgi:error] [pid 361523:tid 140707810875136] [remote 10.80.0.229:61350] WARNING oslo_policy.policy JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [Wed Jun 02 16:00:33.168505 2021] [wsgi:error] [pid 361523:tid 140707810875136] [remote 10.80.0.229:61350] WARNING oslo_policy.policy JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [Wed Jun 02 16:00:33.169357 2021] [wsgi:error] [pid 361523:tid 140707810875136] [remote 10.80.0.229:61350] WARNING oslo_policy.policy JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. [Wed Jun 02 16:00:33.175743 2021] [wsgi:error] [pid 361523:tid 140707810875136]
[Yahoo-eng-team] [Bug 1930405] [NEW] Horizon Integration tests Fails if network backend is OVN
Public bug reported: Horizon integration test specifically router-related tests [1] start failing after devstack changes default Neutron backend to OVN From OVS. More details about migration to OVN can be found here [2]. [1] http://paste.openstack.org/show/806215/ [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022410.html ** Affects: horizon Importance: High Assignee: Vishal Manchanda (vishalmanchanda) Status: New ** Changed in: horizon Importance: Undecided => High ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1930405 Title: Horizon Integration tests Fails if network backend is OVN Status in OpenStack Dashboard (Horizon): New Bug description: Horizon integration test specifically router-related tests [1] start failing after devstack changes default Neutron backend to OVN From OVS. More details about migration to OVN can be found here [2]. [1] http://paste.openstack.org/show/806215/ [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022410.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1930405/+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 1674846] Re: using glance v2 api does not remove temporary files
hi, I tried to reproduce this bug on the master branch but not succeed. I think it is already fixed by [1]. So when you try to create an image using django(leagcy) way, it will create a temporary file which will be deleted once the upload is completed[2]. [1] https://review.opendev.org/c/openstack/horizon/+/703632 [2] https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/glance.py#L517 If you still face the same issue, please add more steps to reproduce it. ** Changed in: horizon Status: New => Incomplete ** No longer affects: horizon ** Also affects: horizon Importance: Undecided Status: New ** Changed in: horizon Status: New => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1674846 Title: using glance v2 api does not remove temporary files Status in OpenStack Dashboard (Horizon): Incomplete Status in OpenStack Security Advisory: Incomplete Bug description: Currently if you are using Glance v2 with TemporaryUploadedFile (legacy mode?) the temporary file created on disk is never removed. This will eventually cause the machine to run out of tmp disk space. The issue is that if Glance v2 is used, the code never calls image_update which is responsible for deleting the temporary file. https://github.com/openstack/horizon/blob/446e5aefb4354c9092d1cbc5ff258ee74558e769/openstack_dashboard/api/glance.py#L439 https://github.com/openstack/horizon/blob/446e5aefb4354c9092d1cbc5ff258ee74558e769/openstack_dashboard/api/glance.py#L349 Either the function image_update should always be called, or if data is a TemporaryUploadedFile object, the call should always try to delete the temporary file once done. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1674846/+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 1927261] [NEW] Support for Angular 1.8.x in Horizon
Public bug reported: Some of the horizon angular panels (keypair and glance) are broken in Debian Bullseye distribution. As of now, we use angular 1.5.8.0 in the horizon [1], [2]. We can try to update angularjs to 1.8.2 maybe that fixes the issue. [1] https://github.com/openstack/horizon/blob/master/requirements.txt#L44 [2] https://pypi.org/project/XStatic-Angular/ Related thread: http://lists.openstack.org/pipermail/openstack- discuss/2021-May/022243.html ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: New ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1927261 Title: Support for Angular 1.8.x in Horizon Status in OpenStack Dashboard (Horizon): New Bug description: Some of the horizon angular panels (keypair and glance) are broken in Debian Bullseye distribution. As of now, we use angular 1.5.8.0 in the horizon [1], [2]. We can try to update angularjs to 1.8.2 maybe that fixes the issue. [1] https://github.com/openstack/horizon/blob/master/requirements.txt#L44 [2] https://pypi.org/project/XStatic-Angular/ Related thread: http://lists.openstack.org/pipermail/openstack- discuss/2021-May/022243.html To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1927261/+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 1546149] Re: Launch from new volume fails with flavor.disksize = 0
Fixed by https://review.opendev.org/c/openstack/horizon/+/680603. ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1546149 Title: Launch from new volume fails with flavor.disksize = 0 Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Environment: - I'm using Liberty (on RDO) - I'm using the angularjs launch instance. - I have a flavor with disk = 0 GB. - I use Ceph RBD backend and always create volume on instantiation (If I don't, the actual image size should be used when creating temporary volume etc of RBD) Work flow: - I go to project / instances and open "Launch Instance" panel - I click Yes to Create volume - I pick an image with min_disk 1, - I see warning that my volume size must be minimum 2 (don't mind the GB/GiB inconsistency) - I up the volume size to 2 GB - I continue to selecting flavor dialogue panel - Any flavor with disk size = 0 GB is grayed out, hitting the warnings at https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/flavor/flavor.controller.js#L302 Expected behaviour: - since I am creating a volume and defining its size, - and since that the size of the volume I'm creating has already been verified, - i expect that disksize = 0 GB in a volume should be allowed in the flavor checking (code line referenced above) Disk size = 0 GB is a special value, according to for instance: http://docs.openstack.org/openstack-ops/content/flavors.html . And it makes sense (to me at least) that I should be able to detach disk size information from flavors when using Ceph / RBD and I as the user always configure the volume. And if I do not set the volume size, and eg boot from image, Nova, Glance and Ceph should take care of instantiating a snap or similar of the original image to its predefined size already - "no user input required". I.e. flavor disk size = 0 GB should mean that either the source image or the volume size applies for the volume to be created (or not, in the boot from image case). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1546149/+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 1340197] Re: Horizon doesn't notify when fail to attach a volume
Hi, this bug looks quite old. I am not able to reproduce it in the master branch. Please find below the steps how I tried to reproduce it: 1. I have updated the status for a volume(name= test). 2. Then If I try to attach to a nova instance, I get an error in the horizon. I have also attached a screenshot for the same. So I am changing this bug status to invalid. Feel free to open it if you are still facing the same issue and add the steps to reproduce it. ** Attachment added: "bug.PNG" https://bugs.launchpad.net/horizon/+bug/1340197/+attachment/5490975/+files/bug.PNG ** Changed in: horizon Status: New => Invalid ** Changed in: horizon Importance: Wishlist => Undecided -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1340197 Title: Horizon doesn't notify when fail to attach a volume Status in OpenStack Dashboard (Horizon): Invalid Bug description: Description of problem: Horizon doesn't notify when the attachment of volume process fail with Errors. The nova-compute log show errors during the process of the volume attachment but the Horizon doesn't present the failure and the error. Version-Release number of selected component (if applicable): python-django-horizon-2014.1-7.el7ost.noarch openstack-nova-network-2014.1-7.el7ost.noarch python-novaclient-2.17.0-2.el7ost.noarch openstack-nova-common-2014.1-7.el7ost.noarch openstack-nova-compute-2014.1-7.el7ost.noarch openstack-nova-conductor-2014.1-7.el7ost.noarch openstack-nova-scheduler-2014.1-7.el7ost.noarch openstack-nova-api-2014.1-7.el7ost.noarch openstack-nova-cert-2014.1-7.el7ost.noarch openstack-nova-novncproxy-2014.1-7.el7ost.noarch python-nova-2014.1-7.el7ost.noarch openstack-nova-console-2014.1-7.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Follow the step of the bug: https://bugs.launchpad.net/nova/+bug/1340169 2. In the Horizon try to attach a volume Actual results: The Horizon shows an info message: Info: Attaching volume bowl-the-dust to instance cougar-01-fe5510a5-c50c-46ee-9d71-6f8e41a58ecc on /dev/vdc. The volume status changes to 'attaching' then change back to available. Expected results: An error should appear saying "Error: the volume attachment failed" Additional info: The Horizon log is attached. The nova-compute log with the volume attachment error is available in the bug https://bugs.launchpad.net/nova/+bug/1340169 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1340197/+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 1822849] Re: Timezone offset displayed in horizon / user / settings is always using daylight saving
It is fixed by https://review.opendev.org/c/openstack/horizon/+/649379/. ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1822849 Title: Timezone offset displayed in horizon / user / settings is always using daylight saving Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Timezone offset displayed in horizon / user / settings is always using daylight saving To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1822849/+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 1383580] Re: API calls in openstack_dashboard.usage.quotas should be wrapped with try/except
It is fixed by https://review.opendev.org/c/openstack/horizon/+/765144. ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1383580 Title: API calls in openstack_dashboard.usage.quotas should be wrapped with try/except Status in OpenStack Dashboard (Horizon): Fix Released Bug description: API calls in openstack_dashboard.usage.quotas should be wrapped with try/except. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1383580/+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 1920010] Re: Validation on fails on the Associate Floating IP when too many instances exist
It is fixed by https://review.opendev.org/c/openstack/horizon/+/780925. ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1920010 Title: Validation on fails on the Associate Floating IP when too many instances exist Status in OpenStack Dashboard (Horizon): Fix Released Bug description: If there are more than Nova's pagination limit instances, and one tries to associate a floating IP with a new instance, the form's validation will fail. This is because that form populates the drop-down field for association target differently on initial display of the form (where it takes the instance_id from the URL) than on submitting of that form (when the information from the URL is lost). The latter attempts to get all eligible ports, but is limited by Nova's pagination. You can also observe weird behavior when that form has any error (for instance, because the floating IP wasn't selected) — after submitting, it will re-display the form with the error, but now the target drop- down will be populated with all possible ports, instead of only ones on the instance, like on the initial display. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1920010/+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 1920214] Re: User role assignments and groups tabs visible but don't work for non-admins
It is fixed by https://review.opendev.org/c/openstack/horizon/+/785123. ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1920214 Title: User role assignments and groups tabs visible but don't work for non- admins Status in OpenStack Dashboard (Horizon): Fix Released Bug description: # Steps to reproduce As a non admin user, navigate to Identity -> Users. Then click on the username of your user to go to the detail page. # Expected results Only the allowed Overview tab is visible. # Actual results The view shows three tabs: Overview, Role assignments, Groups. Click on either Role assignments or Groups. An error will appear, showing that the API call is unauthorised, and the table content will fail to load. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1920214/+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 1919120] Re: "Delete Force Volume Backup" should be "Force Delete Volume Backup"
** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1919120 Title: "Delete Force Volume Backup" should be "Force Delete Volume Backup" Status in OpenStack Dashboard (Horizon): Fix Released Bug description: While translating the Horizon UI strings in master branch, I found the following: https://opendev.org/openstack/horizon/blame/branch/master/openstack_dashboard/dashboards/admin/backups/tables.py#L45-L46 "Delete Force Volume Backup" "Delete Force Volume Backups" The word order seems to be incorrect. It should be "Force Delete" instead of "Delete Force". Please check. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1919120/+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 1793488] Re: Horizon logs a user out when created keypair is over quota
It is fixed by https://review.opendev.org/c/openstack/horizon/+/677580. ** Changed in: horizon Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1793488 Title: Horizon logs a user out when created keypair is over quota Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When a users creates a keypair in Horizon, but exceeds it's keypair quota, the user is logged out instead of presenting a nice message. Before presenting the login page, 2 errors are quickly shown, i had to record the output to get those: 'Error: Forbidden. Redirecting to login' 'Error: Unable to the keypair' When doing the same via the CLI the message 'Quota exceeded, too many key pairs. (HTTP 403) (Request-ID: req-b40e7839-290b- 4b8f-a640-2fc23d71aa0e)' is shown, which is much more descriptive. Version: python-django-horizon 3:13.0.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1793488/+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 1917483] Re: Horizon loads policy files partially when one of policy files are written in a wrong format
It is fixed by https://review.opendev.org/c/openstack/horizon/+/778207. So changing bugs status to fixed. ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1917483 Title: Horizon loads policy files partially when one of policy files are written in a wrong format Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Currently horizon stops loading policy rules when it detects any file in a wrong format. This results in a situation where horizon works with very incomplete policy rules because of only one invalid policy file. For example when horizon susceeds to load the keystone policy firstly and then fails to load the nova policy secondly, it recognizes policy rules for only keystone and doesn't recognize policy rules for not only nova but the remaining services like neutron, cinder and so on. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1917483/+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 1915308] Re: security group table doesn't observe Neutron policy settings
It is fixed by https://review.opendev.org/c/openstack/horizon/+/774922 ** Changed in: horizon Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1915308 Title: security group table doesn't observe Neutron policy settings Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Security Advisory: Won't Fix Bug description: The security group panel enables all actions (create/edit/delete/manage rules/etc.) regardless of the network policy.yaml settings or user account. In the code there's this telling readme: # TODO(amotoki): [drop-nova-network] Add neutron policy support In my deployment this is a bit alarming -- users who are intended to be read-only are nonetheless invited to delete things. Of course the Neutron backend /does/ observe the policy so this is ugly but not usually an actual security risk unless people have different back-end and front-end policy files. I'm flagging as security-related nonetheless for the odd edge case where it poses a risk. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1915308/+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 1793411] Re: Dashboard memory leaks
As mentioned in the above comments it is already fixed by https://review.openstack.org/c/614893/. So changing bug status to Fix Released and regarding the same issue in Queen and Rocky branch, you can apply the same fix in your env. I don't have an evn. to check if above patch not work in the old branches. Last but not least Rocky and Queen are EOL, So I am not sure it is good to purpose backport to old branches now. Feel Free to add your suggestions. ** Changed in: horizon Status: Fix Committed => Fix Released ** Changed in: horizon Importance: High => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1793411 Title: Dashboard memory leaks Status in OpenStack Dashboard (Horizon): Fix Released Bug description: 1.Issue description Recently, we found the server which hosts horizon dashboard had serveral times OOM caused by horizon services. After restarting the dashboard, the memory usage goes up very quickly if we access /project/network_topology/ path. 2.How to reproduce Login into the dashboard and go to 'Network Topology' tab, then leave it there (autorefresh 10s by default), now monitor the memory changes on the host. 3.Versions and Components Dashboard: Stable/Pike Server: uWSGI 1.9.17-1 OS: Ubuntu 14.04 trusty Python: 2.7.6 As the codes of memoized has little changes since Pike, if you use Queen/Rocky release, you may also succeed to reproduce it. 4.The investigation The root cause of the memory leak is the decorator memorized(horizon/utils/memoized.py) which is used to cache function calls in Horizon. After disable it, the memory increases has been controlled. The following is the comparison of memory change(with guppy) for each request of /project/network_topology: - original (no code change)684kb - do garbage collection manually 185kb - disable memorize cache 10kb As we known, memoized uses weakref to cache objects. A weak reference to an object is not enough to keep the object alive: when the only remaining references to a referent are weak references, garbage collection is free to destroy the referent and reuse its memory for something else. In the memory, we could see lots of weakref stuffs, the following is a example: Partition of a set of 394 objects. Total size = 37824 bytes. Index Count % Size % Cumulative % Kind (class / dict of class) 0197 5018912 50 18912 50 _cffi_backend.CDataGCP 1197 5018912 50 37824 100 weakref.KeyedRefq But the rest of them are not. the following result is the memory objects changes of per /project/network_topology access with garbage collection manually. Partition of a set of 1017 objects. Total size = 183680 bytes. Index Count % Size % Cumulative % Referrers by Kind (class / dict of class) 0419 4158320 32 58320 32 dict (no owner) 1100 1023416 13 81736 44 list 2135 1315184 8 96920 53 3 2 0 6704 4103624 56 urllib3.connection.VerifiedHTTPSConnection 4 2 0 6704 4110328 60 urllib3.connectionpool.HTTPSConnectionPool 5 1 0 3352 2113680 62 novaclient.v2.client.Client 6 2 0 2096 1115776 63 OpenSSL.SSL.Connection 7 2 0 2096 1117872 64 OpenSSL.SSL.Context 8 2 0 2096 1119968 65 Queue.LifoQueue 9 12 1 2096 1122064 66 dict of urllib3.connectionpool.HTTPSConnectionPool The most of them are dicts. Followings are the dicts sorted by class, as you can see most of them are not weakref objects: Partition of a set of 419 objects. Total size = 58320 bytes. Index Count % Size % Cumulative % Class 0362 8650712 87 50712 87 unicode 1 27 6 3736 6 54448 93 list 2 5 1 2168 4 56616 97 dict 3 22 5 1448 2 58064 100 str 4 2 0 192 0 58256 100 weakref.KeyedRef 5 1 0 64 0 58320 100 keystoneauth1.discover.Discover 5.The issue So the problem is that memoized does not work like what we expect. It allocates memory to cache objects but some of them could not be released. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1793411/+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 1914045] Re: Impossible to launch instance from community image
It is fixed by https://review.opendev.org/c/openstack/horizon/+/00 and patches for stable branches are also pushed https://review.opendev.org/q/c9bb0e95eaa7ae4f0cce21bc0a246a9b0cd2f880. ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1914045 Title: Impossible to launch instance from community image Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Hi, This seems to be a "duplicate" of bug 1779250 but not quite. I have trouble launching a community image from horizon: How to reproduce: - Create two projects, A and B. - In project A, create a snapshot of a VM - Set the snapshot to community - Switch to project B - Try to launch a new instance, and select "visibility: community" in the launch instance panel - Observe that no images are listed. The community image is visible in the images panel, but the same issue occurs if I try to launch a new instance of the community image from the images panel. Running CentOS 8.3 and openstack-dashboard.noarch 1:18.3.2-1.el8 This happens with both legacy and angular images_panel in the Horizon config. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1914045/+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 1439905] Re: [Launch Instance Fix] Show Admin Password
It is fixed by https://review.opendev.org/c/openstack/horizon/+/770528 ** Changed in: horizon Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1439905 Title: [Launch Instance Fix] Show Admin Password Status in OpenStack Dashboard (Horizon): Fix Released Bug description: We need to show admin password if enabled for the hypervisor type. https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L558 https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/nova.py#L939 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1439905/+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 1914782] [NEW] Horizon Integration tests Fails with XStatic-JQuery-Migrate 3.3.2.1 Version
Public bug reported: After Updating the XStatic-JQuery-Migrate version to 3.3.2.1 horizon integration tests start failing. Error logs can be found here http://paste.openstack.org/show/802398/ ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1914782 Title: Horizon Integration tests Fails with XStatic-JQuery-Migrate 3.3.2.1 Version Status in OpenStack Dashboard (Horizon): New Bug description: After Updating the XStatic-JQuery-Migrate version to 3.3.2.1 horizon integration tests start failing. Error logs can be found here http://paste.openstack.org/show/802398/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1914782/+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 1913447] [NEW] Unable to Swift create when running horizon on development server
Public bug reported: When you are running horizon on the development server(tox -e runserver) and tries to create a swift container then you are not able to enter the name for your server in the create container form although it runs fine if you are using apache devstack env. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1913447 Title: Unable to Swift create when running horizon on development server Status in OpenStack Dashboard (Horizon): New Bug description: When you are running horizon on the development server(tox -e runserver) and tries to create a swift container then you are not able to enter the name for your server in the create container form although it runs fine if you are using apache devstack env. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1913447/+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 1890947] Re: keypair integration test failing due to keypairs table id is missing in horizon dashboard
This Bug is a duplicate of the bug https://bugs.launchpad.net/horizon/+bug/1848129 ** Changed in: horizon Importance: Medium => Undecided ** Changed in: horizon Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1890947 Title: keypair integration test failing due to keypairs table id is missing in horizon dashboard Status in OpenStack Dashboard (Horizon): Invalid Bug description: keypairs integration test is failing due to keypairs table id is missing in horizon dashboard's "Key Pairs" page. But id was found in Ocata release, not sure why it's removed now. Due to that existing keypairs integration test is failing. Go to project-> Compute-> Key Pairs page current keypairs table html tag: It should be Captured traceback: ~~~ Traceback (most recent call last): File "openstack_dashboard/test/integration_tests/tests/test_keypairs.py", line 29, in test_keypair keypair_page.create_keypair(self.KEYPAIR_NAME) File "openstack_dashboard/test/integration_tests/pages/project/compute/keypairspage.py", line 69, in create_keypair create_keypair_form = self.keypairs_table.create_keypair() File "openstack_dashboard/test/integration_tests/pages/project/compute/keypairspage.py", line 59, in keypairs_table return KeypairsTable(self.driver, self.conf) File "openstack_dashboard/test/integration_tests/regions/tables.py", line 89, in __init__ super(TableRegion, self).__init__(driver, conf) File "openstack_dashboard/test/integration_tests/regions/baseregion.py", line 35, in __init__ src_elem = root.find_element(*self._default_src_locator) File "horizon/test/webdriver.py", line 44, in find_element by, value) File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/webdriver.py", line 978, in find_element 'value': value})['value'] File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute self.error_handler.check_response(response) File "/usr/local/lib/python2.7/dist-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.NoSuchElementException: Message: Unable to locate element: table#keypairs Full logs: http://paste.openstack.org/show/783880/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1890947/+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 1893305] [NEW] Details href still displayed when details is empty and redirect is false.
Public bug reported: Refactor error messages patch https://review.opendev.org/#/c/708069/ doesn't covers a scenerio when details is empty and redirect is false. It sill display the 'Details' href which is wrong. When we didn't pass redirect parametr in excecption.handle() then '_alert_message.html' template is used for displays the error mesage. We have to add some codition here https://review.opendev.org/#/c/708069/21/horizon/templates/horizon/client_side/_alert_message.html@18 to fi it. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1893305 Title: Details href still displayed when details is empty and redirect is false. Status in OpenStack Dashboard (Horizon): New Bug description: Refactor error messages patch https://review.opendev.org/#/c/708069/ doesn't covers a scenerio when details is empty and redirect is false. It sill display the 'Details' href which is wrong. When we didn't pass redirect parametr in excecption.handle() then '_alert_message.html' template is used for displays the error mesage. We have to add some codition here https://review.opendev.org/#/c/708069/21/horizon/templates/horizon/client_side/_alert_message.html@18 to fi it. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1893305/+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 1892679] [NEW] Missing Integration test for Volume Group-type
Public bug reported: Integration test for different volume group-type operations are missing. ** Affects: horizon Importance: Medium Assignee: Vishal Manchanda (vishalmanchanda) Status: Confirmed ** Tags: integration-tests ** Changed in: horizon Status: New => Confirmed ** Changed in: horizon Importance: Undecided => Medium ** Tags added: integration-tests ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1892679 Title: Missing Integration test for Volume Group-type Status in OpenStack Dashboard (Horizon): Confirmed Bug description: Integration test for different volume group-type operations are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1892679/+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 1891615] Re: AttributeError: module 'horizon.tables' has no attribute 'PagedTableWithPageMenu'
@men, hi looks like you are mixing the stable/train branch with master branch because "PagedTableWithPageMenu" class is added in master[1] by this patch https://review.opendev.org/#/c/705004/ . So it is not surprising that you are geetig above error in stable/train beacuse there is no such attribute in stable/train branch [2] . [1] https://opendev.org/openstack/horizon/src/branch/master/openstack_dashboard/dashboards/project/backups/views.py#L38 [2] https://opendev.org/openstack/horizon/src/branch/stable/train/openstack_dashboard/dashboards/project/backups/views.py#L34 Yeah, if you switch to master branch you will not get this error. ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1891615 Title: AttributeError: module 'horizon.tables' has no attribute 'PagedTableWithPageMenu' Status in OpenStack Dashboard (Horizon): Invalid Bug description: My Linux system can only be installed with source code git clone https://github.com/openstack/horizon.git -b stable/train [root@controller ~]# cd horizon/ [root@controller horizon]# pip3 install -r requirements.txt [root@controller horizon]# python3 setup.py install [root@controller01 openstack-dashboard]# ll total 8 -rwxr-xr-x 1 root apache 830 Aug 5 09:09 manage.py drwxr-xr-x 20 root apache 4096 Aug 5 09:08 openstack_dashboard -rw-r--r-- 1 root root 0 Aug 5 14:40 README.md drwxr-xr-x 10 root apache 114 Aug 5 09:12 static [root@controller01 openstack-dashboard]# ls openstack_dashboard/ apidefaults.py__init__.pypolicy.py templatetags usage conf django_pyscss_fix karma.conf.js __pycache__ test utils context_processors.py enabledlocal settings.py themes views.py contribexceptions.py locale static theme_settings.py wsgi dashboards hooks.py management templatesurls.py wsgi.py It's strange to encounter this problem. I don't know how to investigate it？ [root@controller01 openstack-dashboard]# python3 manage.py runserver /usr/local/lib64/python3.7/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() argspec = inspect.getargspec(function) /usr/local/lib64/python3.7/site-packages/scss/selector.py:54: FutureWarning: Possible nested set at position 329 ''', re.VERBOSE | re.MULTILINE) /usr/local/lib64/python3.7/site-packages/scss/namespace.py:172: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec() argspec = inspect.getargspec(function) /usr/local/lib64/python3.7/site-packages/scss/selector.py:54: FutureWarning: Possible nested set at position 329 ''', re.VERBOSE | re.MULTILINE) Performing system checks... Unhandled exception in thread started by .wrapper at 0xfffc08045d40> Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/utils/autoreload.py", line 225, in wrapper fn(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/runserver.py", line 120, in inner_run self.check(display_num_errors=True) File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 364, in check include_deployment_checks=include_deployment_checks, File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 351, in _run_checks return checks.run_checks(**kwargs) File "/usr/local/lib/python3.7/site-packages/django/core/checks/registry.py", line 73, in run_checks new_errors = check(app_configs=app_configs) File "/usr/local/lib/python3.7/site-packages/django/core/checks/urls.py", line 13, in check_url_config return check_resolver(resolver) File "/usr/local/lib/python3.7/site-packages/django/core/checks/urls.py", line 23, in check_resolver return check_method() File "/usr/local/lib/python3.7/site-packages/django/urls/resolvers.py", line 400, in check warnings.extend(check_resolver(pattern)) File "/usr/local/lib/python3.7/site-packages/django/core/checks/urls.py", line 23, in check_resolver return check_method() File "/usr/local/lib/python3.7/site-packages/django/urls/resolvers.py", line 399, in check for pattern in self.url_patterns: File "/usr/local/lib/python3.7/site-packages/django/utils/functional.py", line 36, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/usr/local/lib/python3.7/site-packages/django/urls/resolvers.py", line 542, in url_patterns iter(patterns) File
[Yahoo-eng-team] [Bug 1886298] Re: Few of the lower constraints are not compatible with python3.8
** Also affects: horizon 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/1886298 Title: Few of the lower constraints are not compatible with python3.8 Status in castellan: New Status in ec2-api: New Status in futurist: New Status in OpenStack Dashboard (Horizon): New Status in manila-ui: New Status in masakari: New Status in OpenStack Compute (nova): In Progress Status in os-win: New Status in oslo.messaging: New Status in oslo.policy: New Status in oslo.privsep: New Status in oslo.reports: New Status in oslo.vmware: New Status in Glance Client: New Status in python-keystoneclient: New Status in python-manilaclient: New Status in python-novaclient: In Progress Status in python-senlinclient: New Status in python-troveclient: New Status in python-watcherclient: New Status in Solum: New Status in tacker: New Status in taskflow: New Status in watcher: New Bug description: lower constraint are being tested with python.6 till now and jobs running fine. With the migration of testing to ubuntu focal where python3.8 is default, lower-constraints job started failing due to multiple issues. For example, Markupsafe 1.0 not compatible with new setuptools: - https://github.com/pallets/markupsafe/issues/116 paramiko 2.7.1 fixed the compatiblity for python3.7 onwards: https://github.com/paramiko/paramiko/issues/1108 greenlet 0.4.15 added wheels for python 3.8: https://github.com/python-greenlet/greenlet/issues/151 numpy 1.19.1 added python 3.8 support and testing: https://github.com/numpy/numpy/pull/14775 paramiko 2.7.1 fixed the compatibility for python3.7 onwards: https://github.com/paramiko/paramiko/commit/4753881223e0ff5e3b3be35bb687a18dfec4f672 Similarly there are many dependencies which added the python3.8 support in their later version. So we need to bump their lower constraints to compatible version. Approach to identify the required bump is by running lower-constraint job on Focal and star bumping for the failed things. I started with nova repos and found below version bump: For Nova: Markupsafe==1.1.1 cffi==1.14.0 greenlet==0.4.15 PyYAML==3.13 lxml==4.5.0 numpy==1.19.0 psycopg2==2.8 paramiko==2.7.1 For python-novaclient: Markupsafe==1.1.1 cffi==1.14.0 greenlet==0.4.15 PyYAML==3.13 For os-vif: Markupsafe==1.1.1 cffi==1.14.0 To manage notifications about this bug go to: https://bugs.launchpad.net/castellan/+bug/1886298/+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 1889087] Re: Add OPENSTACK_MANILA_FEATURES to KNOWN_SETTINGS
** Changed in: horizon Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1889087 Title: Add OPENSTACK_MANILA_FEATURES to KNOWN_SETTINGS Status in OpenStack Dashboard (Horizon): Invalid Bug description: Manila requires OPENSTACK_MANILA_FEATURES setting in config, but upgrade_check don't recognize setting. URL for config: https://docs.openstack.org/manila-ui/stein/configuration/ /usr/share/openstack-dashboard/manage.py upgrade_check ++ | Upgrade Check Results | ++ | Check: Unknown Settings| | Result: Warning| | Details: Unknown settings: OPENSTACK_MANILA_FEATURES | ++ | Check: Deprecated Settings | | Result: Success| | Details: None | ++ | Check: Required Settings | | Result: Success| | Details: None | ++ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1889087/+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 1744999] Re: Horizon incorrectly checks for flavor disk if volume-based instance is being created
*** This bug is a duplicate of bug 1563529 *** https://bugs.launchpad.net/bugs/1563529 It is already fixed in https://review.opendev.org/#/c/680603/. ** This bug has been marked a duplicate of bug 1563529 "Boot from volume" fails on image size restriction -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1744999 Title: Horizon incorrectly checks for flavor disk if volume-based instance is being created Status in OpenStack Dashboard (Horizon): New Bug description: Description === When creating a new VM through Horizon, it validates that its disk size is less than the flavor disk one. Such check doesn't make sense when creating a volume-based instance - either via image2volume process or by using previously existing image. There are no such restrictions in Nova for quite a while. - check in Horizon: https://github.com/openstack/horizon/blob/67eba6443900654b5c70501553e65ddb48f33bad/openstack_dashboard/dashboards/project/static/dashboard/project/workflow /launch-instance/flavor/flavor.controller.js#L382 - fixed bug with incorrect behaviour in Nova (in Kilo version): https://bugs.launchpad.net/nova/+bug/1457517 Steps to reproduce == 1. Create an image A with min_size of 50GB 2. Create a flavor B with disk size of 20GB 3. Try to create an instance C using boot source "image A" and requesting to create a new volume. 4. Select flavor B as a flavor. Expected result === Instance creation succeeds. Actual result = Warning is shown, instance creation button is disabled. Environment === OpenStack Pike. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1744999/+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 1511231] Re: sytle is inconsistence bettwen last step and other steps of wrokflow
** Changed in: horizon
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1511231
Title:
sytle is inconsistence bettwen last step and other steps of wrokflow
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
the template used is 'horizon/common/_workflow.html' , the inconsistences are
as follows:
1) Do not fill in the required fields, an error message is displayed beyond
field;
2) error message is not marked in red;
the finally reason is that，the style setting is error in
horizon.modals.js, such as:
// Add field errors.
$field = $fieldset.find('[name="' + field + '"]');
$field.closest('.form-group').addClass('error');
$.each(errors, function (index, error) {
$field.before(
'' +
error + '');
});
it maybe like this:
// Add field errors.
$field = $fieldset.find('[name="' + field + '"]');
$field.closest('.form-group').addClass('has-error');
$.each(errors, function (index, error) {
$field.after(
'' +
error + '');
});
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1511231/+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 1840843] Re: user with admin role get's logged out when trying to list images
*** This bug is a duplicate of bug 1840844 ***
https://bugs.launchpad.net/bugs/1840844
This bug is duplicate of https://bugs.launchpad.net/horizon/+bug/1840844
and fixes for this is already released.
** This bug has been marked a duplicate of bug 1840844
user with admin role gets logged out when trying to list images
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1840843
Title:
user with admin role get's logged out when trying to list images
Status in OpenStack Dashboard (Horizon):
Confirmed
Bug description:
When admin user tries to access project-> compute -> images, if the
user failed on the identity: get_project policy, user will get logged
out.
code that failed is in
openstack_dashboard/static/app/core/images/images.module.js
.tableColumns
.append(
{ id: 'owner', priority: 1, filters:
[$memoize(keystone.getProjectName)], policies: [
{rules: [['identity', 'identity:get_project']]}
]
})
it didn't happen in default Horizon. In our production cloud
environment, keystone policy is "identity:get_project":
"rule:cloud_admin or rule:admin_and_matching_target_project_domain_id
or project_id:%(target.project.id)s". If user is not a cloud_admin,
the admin user of a project, need to be member of the domain to
satisfies the rule.
The problem here is the admin user should not get logged out.
It is probably caused by horizon/static/framework/framework.module.js
if (error.status === 403) {
var msg2 = gettext('Forbidden. Redirecting to login');
handleRedirectMessage(msg2, $rootScope, $window, frameworkEvents,
toastService);
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1840843/+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 1833041] Re: importing a keypair when keypair limit is reached will logout user
Fixed in https://review.opendev.org/#/c/677580/ ** Changed in: horizon Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1833041 Title: importing a keypair when keypair limit is reached will logout user Status in OpenStack Dashboard (Horizon): Fix Released Bug description: when importing a keypair via horizon gui while the corresponding project quota limit is reached will automatically logout the current user and redirect him to the login screen. this has been testet with version openstack rocky on ubuntu 18 with the cloud archive repository. exact package: 3:14.0.2-0ubuntu2~cloud0 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1833041/+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 1856766] Re: disk information display error when perform volume multiattach
It is also fixed in stable/train. ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1856766 Title: disk information display error when perform volume multiattach Status in OpenStack Dashboard (Horizon): Invalid Bug description: Issue description: 1.When I perform volume multiattach and check volume information on dashboard, there is wrong disk information. Versions and Components - Dashboard: stable/queens - OS: Ubuntu 16.04.6 LTS - Python: Python 2.7.12 If you use rocky release, you may also succeed to reproduce it. Steps to reproduce: 1. create multiattach volume type: openstack volume type create --property multiattach=" True" matt 2. create a volume of multiattach volume type: openstack volume create --size 1 --type matt m1 3. perform multiattach(where cirros1 and cirros2 are instances created by openstack, f5966dde-7724-4c1c-8b43-7b98971de582 is the id of m1): nova volume-attach cirros1 f5966dde-7724-4c1c-8b43-7b98971de582;nova volume-attach cirros2 f5966dde-7724-4c1c-8b43-7b98971de582 4. log in horizon and click Project/Volumes/Volumes and find the volume m1 and click drop-down menu and click Manage Attachments, you will find disk information display error. Expected: 1. On instance cloumn, there are cirros1 and cirros2 Actual: 1. On instance cloumn, there are cirros1 and cirros1 or cirros2 and cirros2, that is to say,they are same. The issue: 1.In addition, I also faced the same question when i attach ceph muliattach volume to multiple instance. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1856766/+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 1795309] Re: server group quota exeeding makes forced log out
It is already fixed in https://review.opendev.org/#/c/677580/. ** Changed in: horizon Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1795309 Title: server group quota exeeding makes forced log out Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When creating a new server group and it exceeds server group quota, a user will be forced to log out. horizon 14.0.0.0rc2.dev93 In case of the default quota, server group quota is 10. This happens when we try to create 11th server group. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1795309/+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 1838950] Re: "Domain" panel under Identity is missing
** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1838950 Title: "Domain" panel under Identity is missing Status in OpenStack Dashboard (Horizon): Invalid Bug description: I am following this document for the Horizon development environment. When I run 'tox -e runserver' everything works fine but 'Domain' panel is missing under identity panel however, it is visible in my devstack setup. Steps to Reproduce: 1. Deploy OpenStack using devstack. 2. clone horizon repo https://opendev.org/openstack/horizon 3. Enter your devstack keystone url in 'OPENSTACK_KEYSTONE_URL' variable in openstack_dashboard/local/local_settings.py file. 4. Run tox -e runserver 5. Go to identity Panel. 6. Domain panel under Identity is missing. I don,t know whether I have to enable some setting in my local_settings.py file? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1838950/+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 1838950] [NEW] "Domain" panel under Identity is missing
Public bug reported: I am following this document for the Horizon development environment. When I run 'tox -e runserver' everything works fine but 'Domain' panel is missing under identity panel however, it is visible in my devstack setup. Steps to Reproduce: 1. Deploy OpenStack using devstack. 2. clone horizon repo https://opendev.org/openstack/horizon 3. Enter your devstack keystone url in 'OPENSTACK_KEYSTONE_URL' variable in openstack_dashboard/local/local_settings.py file. 4. Run tox -e runserver 5. Go to identity Panel. 6. Domain panel under Identity is missing. I don,t know whether I have to enable some setting in my local_settings.py file? ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1838950 Title: "Domain" panel under Identity is missing Status in OpenStack Dashboard (Horizon): New Bug description: I am following this document for the Horizon development environment. When I run 'tox -e runserver' everything works fine but 'Domain' panel is missing under identity panel however, it is visible in my devstack setup. Steps to Reproduce: 1. Deploy OpenStack using devstack. 2. clone horizon repo https://opendev.org/openstack/horizon 3. Enter your devstack keystone url in 'OPENSTACK_KEYSTONE_URL' variable in openstack_dashboard/local/local_settings.py file. 4. Run tox -e runserver 5. Go to identity Panel. 6. Domain panel under Identity is missing. I don,t know whether I have to enable some setting in my local_settings.py file? To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1838950/+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 1838606] [NEW] Incorrect Error message when user try to 'Create Application Credential' with past date
Public bug reported: When User tries to 'Create Application Credential' with a past/old date, User gets an error message "Unable to create application credential" on GUI but IMO we need to raise an error message like keystone "The 'expires_at' must not be before now". ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1838606 Title: Incorrect Error message when user try to 'Create Application Credential' with past date Status in OpenStack Dashboard (Horizon): In Progress Bug description: When User tries to 'Create Application Credential' with a past/old date, User gets an error message "Unable to create application credential" on GUI but IMO we need to raise an error message like keystone "The 'expires_at' must not be before now". To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1838606/+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 1714987] Re: description in _create_backup.html only assumes object storage service
@Nobuto Murata The current description in '_create_backup.html' looks
good to me. So mark it as invalid.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1714987
Title:
description in _create_backup.html only assumes object storage service
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
Actually cinder-backup driver can be something other than object
storage, such as Ceph, NFS. So mentioning "object storage service must
be enabled" is confusing to end users. The description below could
have some space for improvement.
[./openstack_dashboard/dashboards/project/backups/templates/backups/_create_backup.html]
{% block modal-body-right %}
{% trans "Volume Backup:" %} {% trans "Volume Backups
are stored using the Object Storage service. You must have this service
activated in order to create a backup." %}
{% trans "If no container name is provided, a default container named
volumebackups will be provisioned for you. Backups will be the same size as the
volume they originate from." %}
{% endblock %}
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1714987/+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 1837531] [NEW] Incorrect Error message when user try to Encrypt an 'Volume Type' in Use
Public bug reported: When User tries to encrypt a 'Volume Type' which is already in use, User gets an error message "Unable to create encrypted volume type" on the horizon. but IMO it needs to raise an error message like "Cannot create encryption specs. Volume type in use". Steps to reproduce: Go to Admin Panel> Volumes >> Volume Types >>> Create Encryption. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1837531 Title: Incorrect Error message when user try to Encrypt an 'Volume Type' in Use Status in OpenStack Dashboard (Horizon): New Bug description: When User tries to encrypt a 'Volume Type' which is already in use, User gets an error message "Unable to create encrypted volume type" on the horizon. but IMO it needs to raise an error message like "Cannot create encryption specs. Volume type in use". Steps to reproduce: Go to Admin Panel> Volumes >> Volume Types >>> Create Encryption. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1837531/+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 1833271] [NEW] tox-fast8 support which will run pep8 only on updated(delta) code
Public bug reported: We have to add "tox-fast8 support" for horizon which will run pep8 only on updated(delta) code. ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: New ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1833271 Title: tox-fast8 support which will run pep8 only on updated(delta) code Status in OpenStack Dashboard (Horizon): New Bug description: We have to add "tox-fast8 support" for horizon which will run pep8 only on updated(delta) code. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1833271/+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 1640427] Re: Error with the content of the Horizon dashboard tutorial at http://docs.openstack.org/developer/horizon/topics/table_actions.html#adding-the-url
This is already fixed in master branch. For more information please refer [1]. So marking it as invalid. [1] https://github.com/openstack/horizon/blob/master/doc/source/contributor/tutorials/dashboard.rst#urls ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1640427 Title: Error with the content of the Horizon dashboard tutorial at http://docs.openstack.org/developer/horizon/topics/table_actions.html #adding-the-url Status in OpenStack Dashboard (Horizon): Invalid Bug description: This tutorial specifies the following changes to be made to urls.py file: from django.conf.urls import url from openstack_dashboard.dashboards.mydashboard.mypanel import views urlpatterns = [, url(r'^$', views.IndexView.as_view(), name='index'), url(r'^(?P[^/]+)/create_snapshot/$', views.CreateSnapshotView.as_view(), name='create_snapshot'), ] After this change has been made, and after I restart the httpd I get an error in the horizon_error.log as posted below: __import__(name) [:error] [pid 11724] [remote 172.22.225.42:0] File "/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/mydashboard/mypanel/urls.py", line 6 [:error] [pid 11724] [remote 172.22.225.42:0] urlpatterns = [, [:error] [pid 11724] [remote 172.22.225.42:0]^ [:error] [pid 11724] [remote 172.22.225.42:0] SyntaxError: invalid syntax To fix this issue, we need to remove the comma next to the opening square bracket in urlpatterns = [, The resulting code should look like: urlpatterns = [ url(r'^$', views.IndexView.as_view(), name='index'), url(r'^(?P[^/]+)/create_snapshot/$', views.CreateSnapshotView.as_view(), name='create_snapshot'), ] To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1640427/+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 1625683] Re: Gives error while running command from Horizon quickstart
Unable to reproduce this bug on master branch so making it as invalid. ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1625683 Title: Gives error while running command from Horizon quickstart Status in OpenStack Dashboard (Horizon): Invalid Bug description: When I run Command : python manage.py migrate_settings --gendiff From: http://docs.openstack.org/developer/horizon/quickstart.html It gives error: http://paste.openstack.org/show/582262/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1625683/+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 1703074] Re: No success message for deleting resources on network topology panel
Unable to reprodue this bug for master branch so marking it as invalid. When i delete a resource like netwrok and subnet from the network topology panel,then it always shows a sucess message after the resource deletion. ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1703074 Title: No success message for deleting resources on network topology panel Status in OpenStack Dashboard (Horizon): Invalid Bug description: When adding a resource from the network topology panel, it shows a success message if the action is successful. However, when deleting a resource from the network topology panel, there’s no success message when the deletion is successful. I think it will be helpful to show the success message for the deletion as well. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1703074/+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 1829461] [NEW] Volume Group Under project panel not working
Public bug reported: Volume Group under project panel not working properly for master branch. Volume Group table under project panel is missing same is attached ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1829461 Title: Volume Group Under project panel not working Status in OpenStack Dashboard (Horizon): New Bug description: Volume Group under project panel not working properly for master branch. Volume Group table under project panel is missing same is attached To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1829461/+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 1828382] [NEW] Missing field "Rbac policy" in Edit quota table under Identity Panel
Public bug reported: "Rbac policy" filed is missing in Edit Quota table. Steps to Reproduce: Go to Identity>Projects>Select any Project>Select Modify Quota Action>Go to "Network" tab in Edit Quota table. Here 'Rbac policy' filed is missing form table. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1828382 Title: Missing field "Rbac policy" in Edit quota table under Identity Panel Status in OpenStack Dashboard (Horizon): New Bug description: "Rbac policy" filed is missing in Edit Quota table. Steps to Reproduce: Go to Identity>Projects>Select any Project>Select Modify Quota Action>Go to "Network" tab in Edit Quota table. Here 'Rbac policy' filed is missing form table. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1828382/+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 1826156] [NEW] Group Name is optional parameter to create Volume Group
Public bug reported: On Horizon dashboard, the field of "Volume Group name" is marked mandatory in the process of creating new volume group but volume group name is optional parameter while creating group volume using CLI. Proposal: change the field of "Volume Group name" on Horizon dashboard from mandatory to optional. This is supported by the fact that Horizon dashboard displays the group volume's ID for the group volume's name if its name is None or empty ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1826156 Title: Group Name is optional parameter to create Volume Group Status in OpenStack Dashboard (Horizon): New Bug description: On Horizon dashboard, the field of "Volume Group name" is marked mandatory in the process of creating new volume group but volume group name is optional parameter while creating group volume using CLI. Proposal: change the field of "Volume Group name" on Horizon dashboard from mandatory to optional. This is supported by the fact that Horizon dashboard displays the group volume's ID for the group volume's name if its name is None or empty To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1826156/+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 1820102] [NEW] Incorrect Error message when user change password to a previous password.
Public bug reported: When user change password to its previous password,then user get an error message "Unable to change password" on gui. but i thinks it need to raise an error message that "The new password cannot be identical to a previous password" ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1820102 Title: Incorrect Error message when user change password to a previous password. Status in OpenStack Dashboard (Horizon): New Bug description: When user change password to its previous password,then user get an error message "Unable to change password" on gui. but i thinks it need to raise an error message that "The new password cannot be identical to a previous password" To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1820102/+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 1818826] [NEW] Volume Type 'View Extra Specs' overrides existing key value
Public bug reported: When User create a new spec using 'View Extra Spec' with an existing key name under Volume Type panel, the existing spec will be overridden.In the cinder API, the behavior is "set" so it is not surprising to override an existing spec.However, in the horizon implementation, "Create" and "Edit" are used.So We it is better to suggest "Edit" when a specified key already exists in the "Create" spec form. ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: New ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1818826 Title: Volume Type 'View Extra Specs' overrides existing key value Status in OpenStack Dashboard (Horizon): New Bug description: When User create a new spec using 'View Extra Spec' with an existing key name under Volume Type panel, the existing spec will be overridden.In the cinder API, the behavior is "set" so it is not surprising to override an existing spec.However, in the horizon implementation, "Create" and "Edit" are used.So We it is better to suggest "Edit" when a specified key already exists in the "Create" spec form. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1818826/+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 1818791] [NEW] Volume Snapshot table has incorrect error message.
Public bug reported: Volume snapshot table to retrieve volume snapshot project project information has incorrect error message here [1]. [1] https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/admin/snapshots/tables.py#L52 ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1818791 Title: Volume Snapshot table has incorrect error message. Status in OpenStack Dashboard (Horizon): In Progress Bug description: Volume snapshot table to retrieve volume snapshot project project information has incorrect error message here [1]. [1] https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/admin/snapshots/tables.py#L52 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1818791/+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 1817887] [NEW] Modify Edit User information Success message
Public bug reported: When we 'Edit' a user information,then Success message doesn't show user name. ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1817887 Title: Modify Edit User information Success message Status in OpenStack Dashboard (Horizon): In Progress Bug description: When we 'Edit' a user information,then Success message doesn't show user name. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1817887/+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 1817169] Re: Volume Groups Under Project Panel not working
** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1817169 Title: Volume Groups Under Project Panel not working Status in OpenStack Dashboard (Horizon): Invalid Bug description: Volume Groups under Project panel does not show any data. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1817169/+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 1817169] [NEW] Volume Groups Under Project Panel not working
Public bug reported: Volume Groups under Project panel does not show any data. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1817169 Title: Volume Groups Under Project Panel not working Status in OpenStack Dashboard (Horizon): New Bug description: Volume Groups under Project panel does not show any data. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1817169/+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 1815859] [NEW] Volume Snapshot table 'Project' column have wrong information
Public bug reported: In volume snapshot table 'Project' column returns 'os-vol-tenant-attr:tenant_id' (response from volume) [1] but it have to return 'os-extended-snapshot-attributes:project_id' (response from snapshot). [1].https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/admin/snapshots/views.py#L68 ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1815859 Title: Volume Snapshot table 'Project' column have wrong information Status in OpenStack Dashboard (Horizon): New Bug description: In volume snapshot table 'Project' column returns 'os-vol-tenant-attr:tenant_id' (response from volume) [1] but it have to return 'os-extended-snapshot-attributes:project_id' (response from snapshot). [1].https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/admin/snapshots/views.py#L68 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1815859/+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 1815029] [NEW] Missing Project ID information in detail page
Public bug reported: Many detail view pages like instances,images,Volumes Snapshots are missing Project ID information. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1815029 Title: Missing Project ID information in detail page Status in OpenStack Dashboard (Horizon): New Bug description: Many detail view pages like instances,images,Volumes Snapshots are missing Project ID information. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1815029/+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 1812329] [NEW] Image details page, the name needs to be word wrap
Public bug reported: Image, Keypair details page, if the name is too long, it will affect the display. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1812329 Title: Image details page, the name needs to be word wrap Status in OpenStack Dashboard (Horizon): New Bug description: Image, Keypair details page, if the name is too long, it will affect the display. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1812329/+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 1807874] [NEW] cinder generic volume groups panel is not working properly
Public bug reported: When a user stop the cinder services Groups & Group Snapshot panel is disappeared from the horizon. Expected Behavior:Groups and Group Snapshot panel will appear in horizon and through an exception like 'Unable to retrieve Volume-Group list' as same happen in volume and snapshot panel. ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: New ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1807874 Title: cinder generic volume groups panel is not working properly Status in OpenStack Dashboard (Horizon): New Bug description: When a user stop the cinder services Groups & Group Snapshot panel is disappeared from the horizon. Expected Behavior:Groups and Group Snapshot panel will appear in horizon and through an exception like 'Unable to retrieve Volume- Group list' as same happen in volume and snapshot panel. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1807874/+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 1804139] [NEW] [doc] Modify the content of the configure access and security for instance
Public bug reported: This bug tracker is for errors with the documentation,the doc [1] is inaccurate in the following way: Step 7 of 'Add a key pair' instructs end users to respond to the prompt to download but Horizon now automatically download Key pair and no prompt to download the key pair is displayed. [1] https://github.com/openstack/horizon/blob/master/doc/source/user /configure-access-and-security-for-instances.rst ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: New ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1804139 Title: [doc] Modify the content of the configure access and security for instance Status in OpenStack Dashboard (Horizon): New Bug description: This bug tracker is for errors with the documentation,the doc [1] is inaccurate in the following way: Step 7 of 'Add a key pair' instructs end users to respond to the prompt to download but Horizon now automatically download Key pair and no prompt to download the key pair is displayed. [1] https://github.com/openstack/horizon/blob/master/doc/source/user /configure-access-and-security-for-instances.rst To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1804139/+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 1803486] [NEW] Floating and negative values accepted in volume size field.
Public bug reported: As we know that in cinder, volume size cannot be a decimal value, only integer values are accepted. So when a user create a volume from horizon,horizon allows user to enter a decimal value or negative value in Size (GiB) field. obviously, user can't create a volume in decimal size as there are some validation on create button, But we can enforce more validation on the volume Size field (like user can't enter alphabets which is currently enforced), we shouldn't allow negative symbol '-' and decimal point '.' in the field too, So the user can only enter number from (0-9). ** Affects: horizon Importance: Undecided Assignee: Vishal Manchanda (vishalmanchanda) Status: New ** Changed in: horizon Assignee: (unassigned) => Vishal Manchanda (vishalmanchanda) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1803486 Title: Floating and negative values accepted in volume size field. Status in OpenStack Dashboard (Horizon): New Bug description: As we know that in cinder, volume size cannot be a decimal value, only integer values are accepted. So when a user create a volume from horizon,horizon allows user to enter a decimal value or negative value in Size (GiB) field. obviously, user can't create a volume in decimal size as there are some validation on create button, But we can enforce more validation on the volume Size field (like user can't enter alphabets which is currently enforced), we shouldn't allow negative symbol '-' and decimal point '.' in the field too, So the user can only enter number from (0-9). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1803486/+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 1629227] Re: Floating-ip-creation
** Changed in: neutron Status: Opinion => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1629227 Title: Floating-ip-creation Status in neutron: Incomplete Bug description: On network node a floating ip is being created by assigning a range of floating ip address to external network pool on routers, where gateway addresses and dhcp is disabled, but here neutronclient/v2_0/client.py returns an empty list to ceilometer which is wrong it should return a floating ip status or something meaningful. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1629227/+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 1629227] Re: Floating-ip-creation
** Changed in: neutron Status: Incomplete => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1629227 Title: Floating-ip-creation Status in neutron: Opinion Bug description: On network node a floating ip is being created by assigning a range of floating ip address to external network pool on routers, where gateway addresses and dhcp is disabled, but here neutronclient/v2_0/client.py returns an empty list to ceilometer which is wrong it should return a floating ip status or something meaningful. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1629227/+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 1629227] [NEW] Floating-ip-creation
Public bug reported: On network node a floating ip is being created by assigning a range of floating ip address to external network pool on routers, where gateway addresses and dhcp is disabled, but here neutronclient/v2_0/client.py returns an empty list to ceilometer which is wrong it should return a floating ip status or something meaningful. ** Affects: neutron Importance: Undecided Status: New ** Tags: ceilometer floating ip neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1629227 Title: Floating-ip-creation Status in neutron: New Bug description: On network node a floating ip is being created by assigning a range of floating ip address to external network pool on routers, where gateway addresses and dhcp is disabled, but here neutronclient/v2_0/client.py returns an empty list to ceilometer which is wrong it should return a floating ip status or something meaningful. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1629227/+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 1553030] Re: Change optparse to argparse, optparse is Deprecated since pyhton version 2.7
** Also affects: oslo-incubator Importance: Undecided Status: New ** Changed in: oslo-incubator Assignee: (unassigned) => Vishal kumar mahajan (mahajan-vishal-mca) ** No longer affects: cinder ** No longer affects: ironic ** Changed in: python-swiftclient Assignee: Vishal kumar mahajan (mahajan-vishal-mca) => (unassigned) -- 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/1553030 Title: Change optparse to argparse, optparse is Deprecated since pyhton version 2.7 Status in Glance: New Status in Manila: New Status in OpenStack Compute (nova): New Status in oslo-incubator: New Status in Python client library for Sahara: New Status in python-swiftclient: New Bug description: In ironic currently we use optparse.So we can move optparse to argparse because optparse is deprecated since python version2.7. Related link:- https://docs.python.org/2/library/optparse.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1553030/+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 1553030] Re: Change optparse to argparse, optparse is Deprecated since pyhton version 2.7
** No longer affects: python-ironicclient ** No longer affects: python-congressclient -- 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/1553030 Title: Change optparse to argparse, optparse is Deprecated since pyhton version 2.7 Status in Glance: New Status in Manila: New Status in OpenStack Compute (nova): New Status in oslo-incubator: New Status in Python client library for Sahara: New Status in python-swiftclient: New Bug description: In ironic currently we use optparse.So we can move optparse to argparse because optparse is deprecated since python version2.7. Related link:- https://docs.python.org/2/library/optparse.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1553030/+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 1548633] [NEW] One of the Network node out of five is over utilized (has more dhcp namespaces) than the others.
Public bug reported: I have 5 Network nodes (NN's) on my setup each with 32 GB RAM. All have same configuration (Created from the same ubuntu template). I am running a scale scenario under which I am creating 4K networks each with one subnet using rally with 100 concurrency. Ideally all the network namespaces should have been equally divided among all the 5 NN’s but one NN is over utilized which in turn creates resource crunch and future requests start failing on it. The number of namespace on the faulty NN is 1175 while other NN's have 650 to 750 namespaces. I ran the scenario twice and both the times the result was same. Please note if I create networks one by one without any concurrency the namespace distribution is even and the problem is not seen. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1548633 Title: One of the Network node out of five is over utilized (has more dhcp namespaces) than the others. Status in neutron: New Bug description: I have 5 Network nodes (NN's) on my setup each with 32 GB RAM. All have same configuration (Created from the same ubuntu template). I am running a scale scenario under which I am creating 4K networks each with one subnet using rally with 100 concurrency. Ideally all the network namespaces should have been equally divided among all the 5 NN’s but one NN is over utilized which in turn creates resource crunch and future requests start failing on it. The number of namespace on the faulty NN is 1175 while other NN's have 650 to 750 namespaces. I ran the scenario twice and both the times the result was same. Please note if I create networks one by one without any concurrency the namespace distribution is even and the problem is not seen. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1548633/+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 1489059] Re: "db type could not be determined" running py34
** Also affects: python-ironicclient (Ubuntu) Importance: Undecided Status: New ** Changed in: python-ironicclient (Ubuntu) Assignee: (unassigned) => Vishal kumar mahajan (mahajan-vishal-mca) ** Also affects: python-saharaclient (Ubuntu) Importance: Undecided Status: New ** Changed in: python-saharaclient (Ubuntu) Assignee: (unassigned) => Vishal kumar mahajan (mahajan-vishal-mca) -- 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/1489059 Title: "db type could not be determined" running py34 Status in Aodh: Fix Released Status in Barbican: Fix Released Status in Bareon: Fix Released Status in cloudkitty: Fix Committed Status in Fuel for OpenStack: In Progress Status in Glance: Fix Committed Status in glance_store: Fix Committed Status in hacking: Fix Released Status in heat: Fix Released Status in Ironic: Fix Released Status in ironic-lib: Fix Committed Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Released Status in kolla: Fix Released Status in Manila: Fix Released Status in Murano: Fix Committed Status in networking-midonet: Fix Released Status in networking-ofagent: New Status in neutron: Fix Released Status in python-glanceclient: Fix Released Status in python-keystoneclient: Fix Released Status in python-muranoclient: Fix Released Status in python-solumclient: Fix Released Status in python-swiftclient: In Progress Status in Rally: Fix Released Status in Sahara: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in senlin: Fix Released Status in tap-as-a-service: Fix Released Status in tempest: Fix Released Status in zaqar: Fix Released Status in python-ironicclient package in Ubuntu: New Status in python-saharaclient package in Ubuntu: New Bug description: When running tox for the first time, the py34 execution fails with an error saying "db type could not be determined". This issue is know to be caused when the run of py27 preceeds py34 and can be solved erasing the .testrepository and running "tox -e py34" first of all. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1489059/+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 1489059] Re: "db type could not be determined" running py34
** No longer affects: python-saharaclient (Ubuntu) ** Changed in: python-ironicclient (Ubuntu) Status: New => Fix Committed -- 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/1489059 Title: "db type could not be determined" running py34 Status in Aodh: Fix Released Status in Barbican: Fix Released Status in Bareon: Fix Released Status in cloudkitty: Fix Committed Status in Fuel for OpenStack: In Progress Status in Glance: Fix Committed Status in glance_store: Fix Committed Status in hacking: Fix Released Status in heat: Fix Released Status in Ironic: Fix Released Status in ironic-lib: Fix Committed Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: Fix Released Status in kolla: Fix Released Status in Manila: Fix Released Status in Murano: Fix Committed Status in networking-midonet: Fix Released Status in networking-ofagent: New Status in neutron: Fix Released Status in python-glanceclient: Fix Released Status in python-keystoneclient: Fix Released Status in python-muranoclient: Fix Released Status in python-solumclient: Fix Released Status in python-swiftclient: In Progress Status in Rally: Fix Released Status in Sahara: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in senlin: Fix Released Status in tap-as-a-service: Fix Released Status in tempest: Fix Released Status in zaqar: Fix Released Status in python-ironicclient package in Ubuntu: Fix Committed Bug description: When running tox for the first time, the py34 execution fails with an error saying "db type could not be determined". This issue is know to be caused when the run of py27 preceeds py34 and can be solved erasing the .testrepository and running "tox -e py34" first of all. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1489059/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** No longer affects: python-gnocchiclient (Ubuntu) -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: Fix Committed Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: Fix Committed Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in ooi: In Progress Status in os-client-config: Fix Released Status in python-barbicanclient: In Progress Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: In Progress Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in refstack: In Progress Status in Sahara: Fix Released Status in Solum: In Progress Status in Stackalytics: In Progress Status in tempest: Fix Released Status in Trove: Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: python-gnocchiclient (Ubuntu) Importance: Undecided Status: New ** Changed in: python-gnocchiclient (Ubuntu) Assignee: (unassigned) => Vishal kumar mahajan (mahajan-vishal-mca) -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: Fix Committed Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: In Progress Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in ooi: In Progress Status in os-client-config: Fix Released Status in python-barbicanclient: In Progress Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: In Progress Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in refstack: In Progress Status in Sahara: Fix Released Status in Solum: In Progress Status in Stackalytics: In Progress Status in tempest: Fix Released Status in Trove: Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Status in python-gnocchiclient package in Ubuntu: New Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: python-tuskarclient (Ubuntu) Importance: Undecided Status: New ** Changed in: python-tuskarclient (Ubuntu) Assignee: (unassigned) => Vishal kumar mahajan (mahajan-vishal-mca) -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: Fix Committed Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: Fix Committed Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in ooi: In Progress Status in os-client-config: Fix Released Status in python-barbicanclient: In Progress Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: In Progress Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in refstack: In Progress Status in Sahara: Fix Released Status in Solum: In Progress Status in Stackalytics: In Progress Status in tempest: Fix Released Status in Trove: Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Status in python-tuskarclient package in Ubuntu: New Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: congress Importance: Undecided Status: New ** Changed in: congress Assignee: (unassigned) => Vishal kumar mahajan (mahajan-vishal-mca) -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: Fix Committed Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: New Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in ooi: In Progress Status in os-client-config: Fix Released Status in python-barbicanclient: In Progress Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: In Progress Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in refstack: In Progress Status in Sahara: Fix Released Status in Solum: In Progress Status in Stackalytics: In Progress Status in tempest: Fix Released Status in Trove: Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: kolla-mesos Importance: Undecided Status: New ** Changed in: kolla-mesos Assignee: (unassigned) => Vishal kumar mahajan (mahajan-vishal-mca) ** Changed in: kolla-mesos Status: New => Fix Released -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: In Progress Status in Blazar: In Progress Status in Cinder: Fix Released Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: In Progress Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in ooi: In Progress Status in os-client-config: Fix Released Status in python-barbicanclient: In Progress Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: In Progress Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in refstack: In Progress Status in Sahara: Fix Released Status in Solum: In Progress Status in Stackalytics: In Progress Status in tempest: Fix Released Status in Trove: Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Also affects: python-swiftclient Importance: Undecided Status: New ** Changed in: python-swiftclient Assignee: (unassigned) => Vishal kumar mahajan (mahajan-vishal-mca) ** Changed in: python-swiftclient Status: New => In Progress -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: In Progress Status in Blazar: In Progress Status in Cinder: Fix Released Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: In Progress Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in ooi: In Progress Status in os-client-config: Fix Released Status in python-barbicanclient: In Progress Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: In Progress Status in python-swiftclient: In Progress Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in refstack: In Progress Status in Sahara: Fix Released Status in Solum: In Progress Status in Stackalytics: In Progress Status in tempest: Fix Released Status in Trove: Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
** Changed in: python-swiftclient Status: In Progress => Fix Released -- 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/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in bifrost: In Progress Status in Blazar: In Progress Status in Cinder: Fix Released Status in dox: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: In Progress Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in ooi: In Progress Status in os-client-config: Fix Released Status in python-barbicanclient: In Progress Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: In Progress Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in refstack: In Progress Status in Sahara: Fix Released Status in Solum: In Progress Status in Stackalytics: In Progress Status in tempest: Fix Released Status in Trove: Fix Released Status in tuskar: Fix Released Status in zaqar: Fix Released Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+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 1406784] Re: Can't create volume from non-raw image
** Project changed: nova = openstack-manuals -- 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/1406784 Title: Can't create volume from non-raw image Status in Cinder: Invalid Status in OpenStack Manuals: Confirmed Bug description: 1. Create an image using a non-raw image (qcow2 or vmdk is ok) 2. Copy the image to a volume, and failed. Log: 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last): 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 133, in _dispatch_and_reply 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher incoming.message)) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 176, in _dispatch 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher return self._do_dispatch(endpoint, method, ctxt, args) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 122, in _do_dispatch 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher result = getattr(endpoint, method)(ctxt, **new_args) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 363, in create_volume 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher _run_flow() 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 356, in _run_flow 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher flow_engine.run() 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/taskflow/utils/lock_utils.py, line 53, in wrapper 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher return f(*args, **kwargs) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/taskflow/engines/action_engine/engine.py, line 111, in run 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher self._run() 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/taskflow/engines/action_engine/engine.py, line 121, in _run 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher self._revert(misc.Failure()) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/taskflow/engines/action_engine/engine.py, line 78, in _revert 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher misc.Failure.reraise_if_any(failures.values()) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/taskflow/utils/misc.py, line 558, in reraise_if_any 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher failures[0].reraise() 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/taskflow/utils/misc.py, line 565, in reraise 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher six.reraise(*self._exc_info) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/taskflow/engines/action_engine/executor.py, line 36, in _execute_task 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher result = task.execute(**arguments) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/cinder/volume/flows/manager/create_volume.py, line 594, in execute 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher **volume_spec) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/cinder/volume/flows/manager/create_volume.py, line 556, in _create_from_image 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher image_id, image_location, image_service) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher File /usr/lib/python2.7/dist-packages/cinder/volume/flows/manager/create_volume.py, line 463, in _copy_image_to_volume 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher raise exception.ImageUnacceptable(ex) 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher ImageUnacceptable: Image 92fad7ae-6439-4c69-bdf4-4c6cc5759225 is unacceptable: qemu-img is not installed and image is of type vmdk. Only RAW images can be used if qemu-img is not installed. 2014-12-31 07:06:09.299 2159 TRACE oslo.messaging.rpc.dispatcher
[Yahoo-eng-team] [Bug 1312023] Re: ovs_lib: apply order for deferred flows problematic for ovs-firewall-driver
** Changed in: neutron Status: New = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1312023 Title: ovs_lib: apply order for deferred flows problematic for ovs-firewall- driver Status in OpenStack Neutron (virtual network service): Fix Released Bug description: ovs_lib.py provides defer_apply_on/off methods to bulk apply flow changes on a bridge. Currently the order in which flows get applied is add, mod, del. This causes problems for ovs-firewall-driver. update_port_filter() deletes all existing flows on a port and then adds new flows. But because of fixed order of deferred flows the addition of new flows is done first and then cleanup deleting all flows. This results in a scenario where update_port_filter ends up wiping out all flows. This is a big issue for ovs-firewall-driver. There should be a means to tweak the order in which flows will be applied when turning deferred_apply_on. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1312023/+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 1371082] Re: nova-scheduler high cpu usage
*** This bug is a duplicate of bug 1371084 ***
https://bugs.launchpad.net/bugs/1371084
** Project changed: cinder = nova
** Tags added: nova-scheduler
--
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/1371082
Title:
nova-scheduler high cpu usage
Status in OpenStack Compute (Nova):
New
Bug description:
For no particular reason nova-scheduler cpu utilization can jump to
100%. I was unable to find any pattern and reason why this is
happening. We've small cluster 1 cloud controller and 7 node
controllers. Except high cpu usage nothing bad happens, we're able to
create/delete instances, after nova-scheduler restart everything goes
back to normal state.
I was able to strace 2 processes while nova-scheduler was using 100%
cpu.
1st process is in loop and it prints:
122014-09-16 00:02:21.501 5668 WARNING nova.openstack.common.loopingcall
[-] task run outlasted interval by 12.322771 sec\0
2nd processes is in loop as well and it's repeating:
epoll_ctl(6, EPOLL_CTL_ADD, 3, {EPOLLOUT|EPOLLERR|EPOLLHUP, {u32=3,
u64=40095890530107395}}) = 0
epoll_wait(6, {{EPOLLOUT, {u32=3, u64=40095890530107395}}}, 1023, 878) = 1
epoll_ctl(6, EPOLL_CTL_DEL, 3,
{EPOLLRDNORM|EPOLLRDBAND|EPOLLWRNORM|EPOLLMSG|EPOLLHUP|0x2485d020, {u32=32708,
u64=23083065509183428}}) = 0
sendto(3, 142014-09-16 00:44:19.272 5673 INFO
oslo.messaging._drivers.impl_rabbit [-] Connecting to AMQP server on
10.3.128.254:5672\0, 125, 0, NULL, 0) = -1 ENOTCONN (Transport endpoint is not
connected)
Other processes doesn't have any issues with AMQP server just only
nova-scheduler.
We're using Debian, kernel 3.14-1-amd64, nova-scheduler 2014.1.2-1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1371082/+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
