[Yahoo-eng-team] [Bug 1809779] Re: keystone-manage should catch unexpected exception
** Changed in: keystone Status: In Progress => Invalid -- 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/1809779 Title: keystone-manage should catch unexpected exception Status in OpenStack Identity (keystone): Invalid Bug description: keystone-manage command of db_sync (and also other commands) currently does not catch any exception at cmd_class.main(). It makes operator very confusing when db_sync is failed since it does not emit any message at all. I think at the end of the main() in keystone/cmd/cli.py, we have to catch Exception for any exceptional cases. For my case, it causes I don't have pymysql package using mysql+pymysql for db connection. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1809779/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1810342] Re: API unexpected exception message
** Changed in: nova Status: In Progress => Opinion ** Changed in: nova Importance: Undecided => Wishlist -- 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/1810342 Title: API unexpected exception message Status in OpenStack Compute (nova): Opinion Bug description: The "API unexpected exception" message tells the user to open a bug in launchpad and attach the log file if possible. Usually an user doesn't have access to API logs and doesn't know about the nuts and bolts of OpenStack. This error message has been confusing some of our users because asks them to not contact the cloud provider support but instead a website that they don't know. I would prefer to have only a simple error message like "API unexpected exception" or instead, a configurable message where the cloud provider can point their users to the correct support page. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1810342/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1810349] [NEW] agent gw ports created on non dvr destination hosts
Public bug reported: When a VM is migrated between nodes, and due to the l3 dvr scheduler, floatingip agent gateway ports are created in non-DVR cases. The 'dvr_handle_new_service_port' method in the 'l3_dvrscheduler_db' module calls 'check_for_fip_and_create_agent_gw_port_on_host_if_not_exist' method in 'l3_dvr_db' module and an agent gateway port is created for the agent at the destination host with or without a DVR enabled router on the destination host. This is an optimization for cases with a DVR enabled router on the destination host since the agent would do it instead. For cases where the router is not DVR enabled, the unused gateway port will have nothing to delete it even if all the router attachments to the external network are deleted. The proposed fix creates the agent gw port only if the FIP associated to the VM port is being serviced by a DVR enabled router. ** 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/1810349 Title: agent gw ports created on non dvr destination hosts Status in neutron: New Bug description: When a VM is migrated between nodes, and due to the l3 dvr scheduler, floatingip agent gateway ports are created in non-DVR cases. The 'dvr_handle_new_service_port' method in the 'l3_dvrscheduler_db' module calls 'check_for_fip_and_create_agent_gw_port_on_host_if_not_exist' method in 'l3_dvr_db' module and an agent gateway port is created for the agent at the destination host with or without a DVR enabled router on the destination host. This is an optimization for cases with a DVR enabled router on the destination host since the agent would do it instead. For cases where the router is not DVR enabled, the unused gateway port will have nothing to delete it even if all the router attachments to the external network are deleted. The proposed fix creates the agent gw port only if the FIP associated to the VM port is being serviced by a DVR enabled router. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1810349/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1810342] [NEW] API unexpected exception message
Public bug reported: The "API unexpected exception" message tells the user to open a bug in launchpad and attach the log file if possible. Usually an user doesn't have access to API logs and doesn't know about the nuts and bolts of OpenStack. This error message has been confusing some of our users because asks them to not contact the cloud provider support but instead a website that they don't know. I would prefer to have only a simple error message like "API unexpected exception" or instead, a configurable message where the cloud provider can point their users to the correct support page. ** Affects: nova Importance: Undecided Assignee: Belmiro Moreira (moreira-belmiro-email-lists) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Belmiro Moreira (moreira-belmiro-email-lists) ** Description changed: - The "API unexpected exception" message tells the user to open a bug in launchpad - and attach the log file if possible. - Usually an user doesn't have access to API logs and doesn't know about the nuts - and bolts of OpenStack. - This error message has been confusing some of our users because asks them to not - contact the cloud provider support but instead a website that they don't know. + The "API unexpected exception" message tells the user to open a bug in launchpad and attach the log file if possible. + Usually an user doesn't have access to API logs and doesn't know about the nuts and bolts of OpenStack. + This error message has been confusing some of our users because asks them to not contact the cloud provider support but instead a website that they don't know. - I would prefer to have only a simple error message like "API unexpected exception" - or instead, a configurable message where the cloud provider can point their users - to the correct support page. + I would prefer to have only a simple error message like "API unexpected + exception" or instead, a configurable message where the cloud provider + can point their users to the correct support page. -- 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/1810342 Title: API unexpected exception message Status in OpenStack Compute (nova): In Progress Bug description: The "API unexpected exception" message tells the user to open a bug in launchpad and attach the log file if possible. Usually an user doesn't have access to API logs and doesn't know about the nuts and bolts of OpenStack. This error message has been confusing some of our users because asks them to not contact the cloud provider support but instead a website that they don't know. I would prefer to have only a simple error message like "API unexpected exception" or instead, a configurable message where the cloud provider can point their users to the correct support page. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1810342/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1810340] [NEW] Repetitive info messages from nova-compute
Public bug reported: There are 2 repetitive info messages from nova-compute: INFO nova.compute.resource_tracker Final resource view: INFO nova.virt.libvirt.driver Libvirt baseline CPU By default they are logged every minute. In my view they should be "debug" messages. In large infrastructures that store log files for analytics they use significant storage space without bringing reasonable value. ** Affects: nova Importance: Undecided Assignee: Belmiro Moreira (moreira-belmiro-email-lists) Status: In Progress ** Changed in: nova Assignee: (unassigned) => Belmiro Moreira (moreira-belmiro-email-lists) -- 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/1810340 Title: Repetitive info messages from nova-compute Status in OpenStack Compute (nova): In Progress Bug description: There are 2 repetitive info messages from nova-compute: INFO nova.compute.resource_tracker Final resource view: INFO nova.virt.libvirt.driver Libvirt baseline CPU By default they are logged every minute. In my view they should be "debug" messages. In large infrastructures that store log files for analytics they use significant storage space without bringing reasonable value. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1810340/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1810314] [NEW] neutron objects base get_values() fails with KeyError
Public bug reported: As of December 20 2018 the python unit test jobs for the tricircle project have been failing [1]. After going through the tricircle/neutron commits since that date, it seems some changes went into neutron that caused the breakage. If I run tricircle python 3.5 unit test with neutron commit 55c5139d79ef09869eea1201c736eee8de3ec651 (the last commit on neutron from Dec 19, 2018) the unit tests all pass. If I run the same UTs with neutron (latest) master they fail with the same errors found in the results of [2]. While this is just a guess, I suspect that maybe neutron changes that landed on Dec 20 related to "Convert Subnet to OVO in ipam_pluggable_backend.py" [3] introduced the breakage. In any case, something landed in neutron around Dec 20, 2018 that has broken tricircle. [1] http://zuul.openstack.org/builds?branch=master&project=openstack%2Ftricircle&job_name=openstack-tox-py35 [2] https://review.openstack.org/#/c/627888/ [3] https://review.openstack.org/#/c/610184/ ** Affects: neutron Importance: Undecided Status: New ** Affects: tricircle Importance: Undecided Status: New ** Also affects: tricircle 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/1810314 Title: neutron objects base get_values() fails with KeyError Status in neutron: New Status in Tricircle: New Bug description: As of December 20 2018 the python unit test jobs for the tricircle project have been failing [1]. After going through the tricircle/neutron commits since that date, it seems some changes went into neutron that caused the breakage. If I run tricircle python 3.5 unit test with neutron commit 55c5139d79ef09869eea1201c736eee8de3ec651 (the last commit on neutron from Dec 19, 2018) the unit tests all pass. If I run the same UTs with neutron (latest) master they fail with the same errors found in the results of [2]. While this is just a guess, I suspect that maybe neutron changes that landed on Dec 20 related to "Convert Subnet to OVO in ipam_pluggable_backend.py" [3] introduced the breakage. In any case, something landed in neutron around Dec 20, 2018 that has broken tricircle. [1] http://zuul.openstack.org/builds?branch=master&project=openstack%2Ftricircle&job_name=openstack-tox-py35 [2] https://review.openstack.org/#/c/627888/ [3] https://review.openstack.org/#/c/610184/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1810314/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1810309] [NEW] Edit project validates quota against resources used in current project instead of edited project
Public bug reported: This is a followup to https://bugs.launchpad.net/horizon/+bug/1713724, which fixed the issue for Nova ressources, but there is still a similar issue for volumes. Steps to reproduce (via Horizon, of course): 1. Create new project, new user with admin credentials, set new project as primary for new user: https://pasteboard.co/HTvmbcG.jpg 2. Login as new user. Populate new (primary) project with few instances and volumes: https://pasteboard.co/HTvnD0i.jpg 3. Create test project with default quotas. 4. Try to modify test project quotas, setting 'volumes', 'gigabytes' values lower then your primary project current usage: https://pasteboard.co/HTvqFR5.jpg 5. Login as other user with admin credentials, but with blank primary_project field. Try to modify test project quotas the way above. It will be OK. ** 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/1810309 Title: Edit project validates quota against resources used in current project instead of edited project Status in OpenStack Dashboard (Horizon): New Bug description: This is a followup to https://bugs.launchpad.net/horizon/+bug/1713724, which fixed the issue for Nova ressources, but there is still a similar issue for volumes. Steps to reproduce (via Horizon, of course): 1. Create new project, new user with admin credentials, set new project as primary for new user: https://pasteboard.co/HTvmbcG.jpg 2. Login as new user. Populate new (primary) project with few instances and volumes: https://pasteboard.co/HTvnD0i.jpg 3. Create test project with default quotas. 4. Try to modify test project quotas, setting 'volumes', 'gigabytes' values lower then your primary project current usage: https://pasteboard.co/HTvqFR5.jpg 5. Login as other user with admin credentials, but with blank primary_project field. Try to modify test project quotas the way above. It will be OK. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1810309/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1809454] Re: [SRU] nova rbd auth fallback uses cinder user with libvirt secret
** Changed in: nova/rocky
Status: Triaged => Fix Released
** Changed in: nova/rocky
Assignee: (unassigned) => Corey Bryant (corey.bryant)
** Changed in: nova/queens
Status: Triaged => In Progress
** Changed in: nova/queens
Assignee: (unassigned) => Corey Bryant (corey.bryant)
--
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/1809454
Title:
[SRU] nova rbd auth fallback uses cinder user with libvirt secret
Status in Ubuntu Cloud Archive:
Triaged
Status in Ubuntu Cloud Archive ocata series:
Triaged
Status in Ubuntu Cloud Archive pike series:
Triaged
Status in Ubuntu Cloud Archive queens series:
Triaged
Status in Ubuntu Cloud Archive rocky series:
Fix Committed
Status in Ubuntu Cloud Archive stein series:
Triaged
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) ocata series:
Triaged
Status in OpenStack Compute (nova) pike series:
Triaged
Status in OpenStack Compute (nova) queens series:
In Progress
Status in OpenStack Compute (nova) rocky series:
Fix Released
Status in nova package in Ubuntu:
Triaged
Status in nova source package in Bionic:
Triaged
Status in nova source package in Cosmic:
Triaged
Status in nova source package in Disco:
Triaged
Bug description:
[Impact]
From David Ames (thedac), originally posted to
https://bugs.launchpad.net/charm-nova-compute/+bug/1671422/comments/25:
Updating this bug. We may decide to move this elsewhere it at some
point.
We have a deployment that was upgraded through to pike at which point
it was noticed that nova instances with ceph backed volumes would not
start.
The cinder key was manually added to the nova-compute nodes in /etc/ceph and
with:
sudo virsh secret-define --file /tmp/cinder.secret
However, this did not resolve the problem. It appeared libvirt was
trying to use a mixed pair of usernames and keys. It was using the
cinder username but the nova-compute key.
Looking at nova's code it falls back to nova.conf when it does not have a
secret_uuid from cinder but it was not setting the username correctly.
https://github.com/openstack/nova/blob/stable/pike/nova/virt/libvirt/volume/net.py#L74
The following seems to mitigate this as a temporary fix on nova-
compute until we can come up with a complete plan:
https://pastebin.ubuntu.com/p/tGm7C7fpXT/
diff --git a/nova/virt/libvirt/volume/net.py b/nova/virt/libvirt/volume/net.py
index cec43ce93b..8b0148df0b 100644
--- a/nova/virt/libvirt/volume/net.py
+++ b/nova/virt/libvirt/volume/net.py
@@ -71,6 +71,7 @@ class
LibvirtNetVolumeDriver(libvirt_volume.LibvirtBaseVolumeDriver):
else:
LOG.debug('Falling back to Nova configuration for RBD auth '
'secret_uuid value.')
+ conf.auth_username = CONF.libvirt.rbd_user
conf.auth_secret_uuid = CONF.libvirt.rbd_secret_uuid
# secret_type is always hard-coded to 'ceph' in cinder
conf.auth_secret_type = netdisk_properties['secret_type']
Apply to /usr/lib/python2.7/dist-
packages/nova/virt/libvirt/volume/net.py
We still need a migration plan to get from the topology with nova-
compute directly related to ceph to the topology with cinder-ceph
related to nova-compute using ceph-access which would populate
cinder's secret_uuid.
It is possible we will need to carry the patch for existing instances.
It may be worth getting that upstream as master has the same problem.
[Test Case]
Upgrade a juju-deployed cloud with ceph backend for nova and cinder from
pre-ocata to ocata or above. Ensure that nova instances with ceph backed
volumes successfully start.
[Regression Potential]
The fix is minimal and will not be fixed in Ubuntu until it has been approved
upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1809454/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1810302] [NEW] Search input box disappears when select is made
Public bug reported: Hi, I have an issue to report - when I go to any summary page in Horizon web interface and I want to select from drop-down menu of "table_search" this whole form specified by class "table_actions clearfix" disappears when I click on already selected value from that drop box. I assume that this is not correct behavior. I have tried different browsers and client machines. Horizon version = 11.0.4 Best regards, LWQ ** 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/1810302 Title: Search input box disappears when select is made Status in OpenStack Dashboard (Horizon): New Bug description: Hi, I have an issue to report - when I go to any summary page in Horizon web interface and I want to select from drop-down menu of "table_search" this whole form specified by class "table_actions clearfix" disappears when I click on already selected value from that drop box. I assume that this is not correct behavior. I have tried different browsers and client machines. Horizon version = 11.0.4 Best regards, LWQ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1810302/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
