[Yahoo-eng-team] [Bug 1333528] Re: Horizon doesn't allow access to dashboard
This is duplicate of bug: https://bugs.launchpad.net/horizon/+bug/1331406 ** 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/1333528 Title: Horizon doesn't allow access to dashboard Status in OpenStack Dashboard (Horizon): Invalid Bug description: After devstack install of openstack on baremetal of laptop, Horizon doesn't allow access to dashboard and keeps the credentials area clean even after entering the correct username and password. On entering wrong credentials it notifies of the error but on entering correct details it doesn't do anything. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333528/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333557] [NEW] nova v2 'os-hosts' api doesn't support specify “service” as a query parameter
Public bug reported: nova v2 'os-hosts' api doesn't support specify “service” as a query parameter which is supported in v3 api. ** Affects: nova Importance: Undecided Assignee: Yaguang Tang (heut2008) Status: New ** Changed in: nova Assignee: (unassigned) = Yaguang Tang (heut2008) -- 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/1333557 Title: nova v2 'os-hosts' api doesn't support specify “service” as a query parameter Status in OpenStack Compute (Nova): New Bug description: nova v2 'os-hosts' api doesn't support specify “service” as a query parameter which is supported in v3 api. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1333557/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1234418] Re: nova resize return 202 and host left in ERROR state
The resize call is asynchronous - eg the API returns the 202 to the client possibly before the actual resize attempt is made. 202 just means that the request has been accepted, not that it has been accepted. In order to determine if the resize has succeded you need to poll ** Changed in: nova Status: New = Invalid -- 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/1234418 Title: nova resize return 202 and host left in ERROR state Status in OpenStack Compute (Nova): Invalid Bug description: The nova resize return 202, but leave the host in ERROR state. The new size is within the quota. Steps to reproduce: 1. create a node with m1.tiny flavor using nova boot. 2. wait for the state to change as ACTIVE 3. resize the node to m1.small flavor. Obtained result: The resize is successful. 202 code is returned. The state is set as ERROR. This cause the following tempest tests fail. The tests attempt to resize the host beyond the quota and expect OverLimit exception. Since the API return 202 status, the tests fail. test_resize_server_using_overlimit_ram test_resize_server_using_overlimit_vcpus Refer to the debug output for details: http://pastebin.com/XD3ZbEL5 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1234418/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1281014] Re: unfriendly user experience if no valid host selected in nova scheduler
The resize call (and many others) are asynchronous. 202 just means that the request has been accepted, not that it has succeeded. The API returns to the client before the resize is attempted - it doesn't know if it is going to succeed or not. In order to determine if the resize succeeded you need to poll - either through the instance actions interface or with the upcoming tasks api ** Changed in: nova Status: In Progress = Invalid -- 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/1281014 Title: unfriendly user experience if no valid host selected in nova scheduler Status in OpenStack Compute (Nova): Invalid Bug description: nova version: 2.15.0 If no enough resource available on any computer node, command like 'nova resize instancevm 100' will exit silently with no enough error or warning message. Users can be confused, not knowing what's wrong and what to do next. Although, there is warning message in /var/log/conductor.log as follows, not much user can find it easily: 2014-02-17 03:43:29.000 6320 WARNING nova.scheduler.utils [req-c0d5f130-c5a9-41b7-8fe4-4d08be4cc774 9ed1534f040c43e98293f6bc6b632e96 bd5848810607480d968b6d1ca9a36637] Failed to compute_task_migrate_server: No valid host was found. Traceback (most recent call last): File /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/common.py, line 420, in catch_client_exception return func(*args, **kwargs) File /usr/lib/python2.6/site-packages/nova/scheduler/manager.py, line 298, in select_destinations filter_properties) File /usr/lib/python2.6/site-packages/nova/scheduler/filter_scheduler.py, line 148, in select_destinations raise exception.NoValidHost(reason='') NoValidHost: No valid host was found. It's better to report some error or warning message if such situation happens. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1281014/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333571] [NEW] Quota update should add check to avoid update projects tenant_id or user_id
Public bug reported: For now the nova quota-update will not give any constraints for the values provided(user_id, tenant_id) when updates. Actually if user 'nova quota-update service --ram=9' and it will get successfully. But it could give user some confusion that quota-show --tenant tenant-name is different with quota-show --tenant tenant- uuid. It is suggested that checks can be added to only allow the uuid-hex format tenant-id or user-id to get quota updated. [root@openstack-zz ~]# keystone tenant-list|grep -i service | 6194feba2f7d4ba38871cbae316c0dc5 | ServicesAdminNegativeV3Test-1222585335 | True | | 342e8af8e9e14d5cb432c2b4caea31a2 | ServicesAdminNegativeV3Test-26338885 | True | | 9abbd7d89f724425878dfedca3e62d73 | ServicesAdminNegativeV3Test-828904988 | True | | 9648314c9e72430586297ec98d92ef8e | ServicesAdminV3Test-1556513182 | True | | 134ba2bec4e8412688868d879cb05399 | ServicesAdminV3Test-1805549103 | True | | ca5f77e01d4f45739e67abfbfd478ec9 | ServicesAdminV3Test-567239400 | True | | 02bbd8a72c7a4615866077132011c963 | service | True | [root@openstack-zz ~]# nova quota-update service --ram 94000 [root@openstack-zz ~]# nova quota-show --tenant service +-+---+ | Quota | Limit | +-+---+ | instances | 10| | cores | 20| | ram | 94000 | | floating_ips| 10| | fixed_ips | -1| | metadata_items | 128 | | injected_files | 5 | | injected_file_content_bytes | 10240 | | injected_file_path_bytes| 255 | | key_pairs | 100 | | security_groups | 10| | security_group_rules| 20| +-+---+ [root@openstack-zz ~]# nova quota-show --tenant 02bbd8a72c7a4615866077132011c963 +-++ | Quota | Limit | +-++ | instances | 10 | | cores | 20 | | ram | 10 | | floating_ips| 10 | | fixed_ips | -1 | | metadata_items | 128| | injected_files | 5 | | injected_file_content_bytes | 10240 | | injected_file_path_bytes| 255| | key_pairs | 100| | security_groups | 10 | | security_group_rules| 20 | +-++ ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1333571 Title: Quota update should add check to avoid update projects tenant_id or user_id Status in OpenStack Compute (Nova): New Bug description: For now the nova quota-update will not give any constraints for the values provided(user_id, tenant_id) when updates. Actually if user 'nova quota-update service --ram=9' and it will get successfully. But it could give user some confusion that quota- show --tenant tenant-name is different with quota-show --tenant tenant-uuid. It is suggested that checks can be added to only allow the uuid-hex format tenant-id or user-id to get quota updated. [root@openstack-zz ~]# keystone tenant-list|grep -i service | 6194feba2f7d4ba38871cbae316c0dc5 | ServicesAdminNegativeV3Test-1222585335 | True | | 342e8af8e9e14d5cb432c2b4caea31a2 | ServicesAdminNegativeV3Test-26338885 | True | | 9abbd7d89f724425878dfedca3e62d73 | ServicesAdminNegativeV3Test-828904988 | True | | 9648314c9e72430586297ec98d92ef8e | ServicesAdminV3Test-1556513182 | True | | 134ba2bec4e8412688868d879cb05399 | ServicesAdminV3Test-1805549103 | True | | ca5f77e01d4f45739e67abfbfd478ec9 | ServicesAdminV3Test-567239400 | True | | 02bbd8a72c7a4615866077132011c963 | service | True | [root@openstack-zz ~]# nova quota-update service --ram 94000 [root@openstack-zz ~]# nova quota-show --tenant service +-+---+ | Quota | Limit | +-+---+ | instances | 10| | cores | 20| | ram | 94000 | | floating_ips| 10| | fixed_ips | -1| | metadata_items | 128 | | injected_files | 5 | | injected_file_content_bytes | 10240 | | injected_file_path_bytes| 255 |
[Yahoo-eng-team] [Bug 1283214] Re: Need documentation of fix to bug 1203680
I don't see how this is a Nova bug? ** Changed in: nova Status: New = Invalid -- 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/1283214 Title: Need documentation of fix to bug 1203680 Status in devstack - openstack dev environments: New Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Compute (Nova): Invalid Bug description: The fix to https://bugs.launchpad.net/devstack/+bug/1203680 is useless unless people know to set the new variable when doing a DevStack install. The DevStack documentation should be updated to mention this, as should the various places that describe how to do unit testing. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1283214/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333528] Re: Horizon doesn't allow access to dashboard
*** This bug is a duplicate of bug 1331406 *** https://bugs.launchpad.net/bugs/1331406 ** Tags removed: low-hanging-fruit ** This bug has been marked a duplicate of bug 1331406 can not login to Dashboard on devstack -- 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/1333528 Title: Horizon doesn't allow access to dashboard Status in OpenStack Dashboard (Horizon): Invalid Bug description: After devstack install of openstack on baremetal of laptop, Horizon doesn't allow access to dashboard and keeps the credentials area clean even after entering the correct username and password. On entering wrong credentials it notifies of the error but on entering correct details it doesn't do anything. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333528/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333583] [NEW] hypervisors list by server do not reflect offline servers
Public bug reported: The list in dashboard/admin/hypervisors/ do not reflect the fact that some servers might be offline. The list shows the last information from all the servers in that list and if the servers went down, the list still shows data. I would have liked to see here some sort of indication, for instance an empty row, a row highlighted in red, a new column saying last update time (all of the aove?) ** 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/1333583 Title: hypervisors list by server do not reflect offline servers Status in OpenStack Dashboard (Horizon): New Bug description: The list in dashboard/admin/hypervisors/ do not reflect the fact that some servers might be offline. The list shows the last information from all the servers in that list and if the servers went down, the list still shows data. I would have liked to see here some sort of indication, for instance an empty row, a row highlighted in red, a new column saying last update time (all of the aove?) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333583/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333587] [NEW] VMware: ExtendVirtualDisk_Task fails due to locked file
Public bug reported: Extending a disk during spawn races, which can result in failure. It is possible to hit this bug by launching a large number of instances of an image which isn't already cached, simultaneously. Some of them will race to extend the cached image, ultimately resulting in an error such as: 2014-06-17 10:49:26.006 9177 WARNING nova.virt.vmwareapi.driver [-] Task [ExtendVirtualDisk_Task] value = task-12073 _type = Task } status: error Unable to access file [datastore1] 172.16.0.13_base/326153d2-1226-415a-a194-2ca47ac3c48b/326153d2-1226-415a-a194-2ca47ac3c48b.1.vmdk since it is locked ** Affects: nova Importance: Undecided Status: New ** Tags: vmware -- 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/1333587 Title: VMware: ExtendVirtualDisk_Task fails due to locked file Status in OpenStack Compute (Nova): New Bug description: Extending a disk during spawn races, which can result in failure. It is possible to hit this bug by launching a large number of instances of an image which isn't already cached, simultaneously. Some of them will race to extend the cached image, ultimately resulting in an error such as: 2014-06-17 10:49:26.006 9177 WARNING nova.virt.vmwareapi.driver [-] Task [ExtendVirtualDisk_Task] value = task-12073 _type = Task } status: error Unable to access file [datastore1] 172.16.0.13_base/326153d2-1226-415a-a194-2ca47ac3c48b/326153d2-1226-415a-a194-2ca47ac3c48b.1.vmdk since it is locked To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1333587/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333616] [NEW] Duplicate entries for the same Heat Stack on Horizon
Public bug reported: Created a single sample Wordpress Heat stack through CLI and Horizon show multiple entries of the same stack. Screenshot attached. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: Duplicate_Stack.png https://bugs.launchpad.net/bugs/1333616/+attachment/4138023/+files/Duplicate_Stack.png -- 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/1333616 Title: Duplicate entries for the same Heat Stack on Horizon Status in OpenStack Dashboard (Horizon): New Bug description: Created a single sample Wordpress Heat stack through CLI and Horizon show multiple entries of the same stack. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333616/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1329426] Re: Cisco n1kv neutron plugin typo in get_profile_binding
** Also affects: neutron/icehouse Importance: Undecided Status: New ** Changed in: neutron/icehouse Importance: Undecided = Medium ** Changed in: neutron/icehouse Status: New = In Progress ** Changed in: neutron/icehouse Assignee: (unassigned) = Ihar Hrachyshka (ihar-hrachyshka) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1329426 Title: Cisco n1kv neutron plugin typo in get_profile_binding Status in OpenStack Neutron (virtual network service): Fix Committed Status in neutron icehouse series: In Progress Bug description: Need to fix typo where raise keyword is missing in get_profile_binding To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1329426/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333643] [NEW] log file is not limited
Public bug reported: horizon.log can grow quite considerably and currently there is no way to limit it from the configuration. This should be limited for size and probably date as well. ** Affects: horizon Importance: Undecided Status: 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/1333643 Title: log file is not limited Status in OpenStack Dashboard (Horizon): Invalid Bug description: horizon.log can grow quite considerably and currently there is no way to limit it from the configuration. This should be limited for size and probably date as well. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333643/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333643] Re: log file is not limited
Thank you for reporting this bug. I'd argue, this is something, which should be solved by distributions. ** 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/1333643 Title: log file is not limited Status in OpenStack Dashboard (Horizon): Invalid Bug description: horizon.log can grow quite considerably and currently there is no way to limit it from the configuration. This should be limited for size and probably date as well. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333643/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333410] Re: Several nova unit tests failing related to IPs - sqla 0.9.5
** Also affects: neutron Importance: Undecided Status: New ** Summary changed: - Several nova unit tests failing related to IPs - sqla 0.9.5 + sqla 0.9.5 breaks the world -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1333410 Title: sqla 0.9.5 breaks the world Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): Confirmed Bug description: There are several different tests failing here: http://logs.openstack.org/79/101579/4/check/gate-nova- python26/990cd05/console.html Checking on the ec2 failure shows it started on 6/23: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRkFJTDogbm92YS50ZXN0cy5hcGkuZWMyLnRlc3RfY2xvdWQuQ2xvdWRUZXN0Q2FzZS50ZXN0X2Fzc29jaWF0ZV9kaXNhc3NvY2lhdGVfYWRkcmVzc1wiIEFORCB0YWdzOlwiY29uc29sZVwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDAzNTU0ODE0OTQ2fQ== I'm guessing this is the change that caused the problem: https://github.com/openstack/nova/commit/077e3c770ebeebd037ce882863a6b5dcefd644cf To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1333410/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333654] [NEW] Timeout waiting for vif plugging callback for instance
Public bug reported: The neutron full job is exhibiting a rather high number of cases where network-vif-plugged timeout are reported. http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIlRpbWVvdXQgd2FpdGluZyBmb3IgdmlmIHBsdWdnaW5nIGNhbGxiYWNrIGZvciBpbnN0YW5jZVwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiIxNzI4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDAzNjA5MTk0NDg4LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiJ9 95.78% of this kind of messages appear for the neutron full job. However, only a fraction of those cause build failures, but that's because the way the tests are executed. This error is currently being masked by another bug as tempest tries to get the console log of a VM in error state: https://bugs.launchpad.net/tempest/+bug/1332414 This bug will target both neutron and nova pending a better triage. Fixing this is of paramount importance to get the full job running. Note: This is different from https://bugs.launchpad.net/nova/+bug/1321872 and https://bugs.launchpad.net/nova/+bug/1329546 ** Affects: neutron Importance: High Assignee: Salvatore Orlando (salvatore-orlando) Status: New ** Affects: nova Importance: Undecided Status: New ** Tags: neutron-full-job ** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Importance: Undecided = High ** Changed in: neutron Assignee: (unassigned) = Salvatore Orlando (salvatore-orlando) ** Changed in: neutron Milestone: None = juno-2 -- 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/1333654 Title: Timeout waiting for vif plugging callback for instance Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Bug description: The neutron full job is exhibiting a rather high number of cases where network-vif-plugged timeout are reported. http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIlRpbWVvdXQgd2FpdGluZyBmb3IgdmlmIHBsdWdnaW5nIGNhbGxiYWNrIGZvciBpbnN0YW5jZVwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiIxNzI4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDAzNjA5MTk0NDg4LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiJ9 95.78% of this kind of messages appear for the neutron full job. However, only a fraction of those cause build failures, but that's because the way the tests are executed. This error is currently being masked by another bug as tempest tries to get the console log of a VM in error state: https://bugs.launchpad.net/tempest/+bug/1332414 This bug will target both neutron and nova pending a better triage. Fixing this is of paramount importance to get the full job running. Note: This is different from https://bugs.launchpad.net/nova/+bug/1321872 and https://bugs.launchpad.net/nova/+bug/1329546 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1333654/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1271706] Re: Misleading warning about MySQL TRADITIONAL mode not being set
** Also affects: fuel Importance: Undecided Status: New ** Changed in: fuel Status: New = Confirmed ** Changed in: fuel Importance: Undecided = Medium ** Changed in: fuel Milestone: None = 5.1 -- 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/1271706 Title: Misleading warning about MySQL TRADITIONAL mode not being set Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Fuel: OpenStack installer that works: Confirmed Status in Orchestration API (Heat): New Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Compute (Nova): New Status in Oslo - a Library of Common OpenStack Code: Fix Released Bug description: common.db.sqlalchemy.session logs a scary warning if create_engine is not being called with mysql_traditional_mode set to True: WARNING keystone.openstack.common.db.sqlalchemy.session [-] This application has not enabled MySQL traditional mode, which means silent data corruption may occur. Please encourage the application developers to enable this mode. That warning is problematic for several reasons: (1) It suggests the wrong mode. Arguably TRADITIONAL is better than the default, but STRICT_ALL_TABLES would actually be more useful. (2) The user has no way to fix the warning. (3) The warning does not take into account that a global sql-mode may in fact have been set via the server-side MySQL configuration, in which case the session *may* in fact be using TRADITIONAL mode all along, despite the warning saying otherwise. This makes (2) even worse. My suggested approach would be: - Remove the warning. - Make the SQL mode a config option. Patches forthcoming. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1271706/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333712] [NEW] NotImplemented _for_groups functions on LDAP
Public bug reported: These functions are not implemented on assignment LDAP backend: - get_roles_for_groups - list_projects_for_groups - list_domains_for_groups ** Affects: keystone Importance: Undecided Assignee: Marcos Lobo (marcos-fermin-lobo) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1333712 Title: NotImplemented _for_groups functions on LDAP Status in OpenStack Identity (Keystone): In Progress Bug description: These functions are not implemented on assignment LDAP backend: - get_roles_for_groups - list_projects_for_groups - list_domains_for_groups To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1333712/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333739] [NEW] Panels within a PanelGroup display in random order
Public bug reported:
I have created a PanelGroup (In the Project dashboard) with the code
below...
class DataProcessingPanels(horizon.PanelGroup):
name = _(Data Processing)
slug = data_processing
panels = ('data_processing.plugins',
'data_processing.data_image_registry',
'data_processing.nodegroup_templates',
'data_processing.cluster_templates',
'data_processing.clusters',
'data_processing.data_sources',
'data_processing.job_binaries',
'data_processing.jobs',
'data_processing.job_executions', )
When I run horizon and look at the UI, I notice that each time I run, the
panels appear in a different order. I am guessing that it might be due to the
fact that my panels are not directly in the project directory, but rather in
a data_processing subdirectory, but I have not confirmed that yet.
Side note: This might be loosely related to
https://bugs.launchpad.net/horizon/+bug/1329050
This bug shows up in the following patch:
https://review.openstack.org/#/c/89846/ (In order to be able to see
the DataProcessing PanelGroup, you would need a stack with the Sahara
(data_processing) service enabled.
** 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/1333739
Title:
Panels within a PanelGroup display in random order
Status in OpenStack Dashboard (Horizon):
New
Bug description:
I have created a PanelGroup (In the Project dashboard) with the code
below...
class DataProcessingPanels(horizon.PanelGroup):
name = _(Data Processing)
slug = data_processing
panels = ('data_processing.plugins',
'data_processing.data_image_registry',
'data_processing.nodegroup_templates',
'data_processing.cluster_templates',
'data_processing.clusters',
'data_processing.data_sources',
'data_processing.job_binaries',
'data_processing.jobs',
'data_processing.job_executions', )
When I run horizon and look at the UI, I notice that each time I run, the
panels appear in a different order. I am guessing that it might be due to the
fact that my panels are not directly in the project directory, but rather in
a data_processing subdirectory, but I have not confirmed that yet.
Side note: This might be loosely related to
https://bugs.launchpad.net/horizon/+bug/1329050
This bug shows up in the following patch:
https://review.openstack.org/#/c/89846/ (In order to be able to see
the DataProcessing PanelGroup, you would need a stack with the Sahara
(data_processing) service enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1333739/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333742] [NEW] Timeout while attaching cinder volumes in proxy configuration
Public bug reported: Hey, I am seeing a problem when attaching multiple volumes to a host. My setup: Between the cinder client and cinder-api process there is a proxy. If the request for detachment does not return any value for more than a minute the proxy will time out the connection. What I am missing is the difference between a dead process and a process which is working, especially if the work can need longer then a special time. Is there a possibility to have more communication/information between the cinder-api and the cinder client, such as: Request to attach - Still attaching - (every 10 seconds) Attached- BR Nikolas PS: Can you tell me which entity in the cinder api is exactly receiving the http request? I have found the entity where cinder client starts the http request. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1333742 Title: Timeout while attaching cinder volumes in proxy configuration Status in OpenStack Compute (Nova): New Bug description: Hey, I am seeing a problem when attaching multiple volumes to a host. My setup: Between the cinder client and cinder-api process there is a proxy. If the request for detachment does not return any value for more than a minute the proxy will time out the connection. What I am missing is the difference between a dead process and a process which is working, especially if the work can need longer then a special time. Is there a possibility to have more communication/information between the cinder-api and the cinder client, such as: Request to attach - Still attaching - (every 10 seconds) Attached - BR Nikolas PS: Can you tell me which entity in the cinder api is exactly receiving the http request? I have found the entity where cinder client starts the http request. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1333742/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1292105] Re: ovs tunnel state not syncing (failure pinging overcloud instance)
** Changed in: tripleo Status: Fix Committed = 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/1292105 Title: ovs tunnel state not syncing (failure pinging overcloud instance) Status in OpenStack Neutron (virtual network service): Fix Committed Status in tripleo - openstack on openstack: Fix Released Bug description: I saw this in a recent CI overcloud run: http://logs.openstack.org/66/74866/8/check-tripleo/check-tripleo- overcloud-precise/aa490f1/console.html 2014-03-12 20:01:46.509 | Timing out after 300 seconds: 2014-03-12 20:01:46.509 | COMMAND=ping -c 1 192.0.2.46 2014-03-12 20:01:46.509 | OUTPUT=PING 192.0.2.46 (192.0.2.46) 56(84) bytes of data. 2014-03-12 20:01:46.509 | From 192.0.2.46 icmp_seq=1 Destination Host Unreachable It appears as though everything ran fine up until it tried to ping the booted overcloud instance. I'm fairly certain it has nothing to do with my change, so I wanted to open a bug to track it in case anyone else runs into a similar problem. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1292105/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333746] [NEW] novncproxy crash at start
Public bug reported: Hi everyone, since the last upgrade you have done on icehouse, novncproxy won't start. This is the Trace I get : Traceback (most recent call last): File /usr/bin/nova-novncproxy, line 10, in module sys.exit(main()) File /usr/lib/python2.7/dist-packages/nova/cmd/novncproxy.py, line 87, in main wrap_cmd=None) File /usr/lib/python2.7/dist-packages/nova/console/websocketproxy.py, line 38, in __init__ ssl_target=None, *args, **kwargs) File /usr/lib/python2.7/dist-packages/websockify/websocketproxy.py, line 231, in __init__ websocket.WebSocketServer.__init__(self, RequestHandlerClass, *args, **kwargs) TypeError: __init__() got an unexpected keyword argument 'no_parent' it seems there is a conflict with websockify. I'm running on debian wheezy amd64. If you need more information, please ask. regards, Axel Vanzaghi ** Affects: nova Importance: Undecided Status: New ** Tags: novnc proxy websockify -- 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/1333746 Title: novncproxy crash at start Status in OpenStack Compute (Nova): New Bug description: Hi everyone, since the last upgrade you have done on icehouse, novncproxy won't start. This is the Trace I get : Traceback (most recent call last): File /usr/bin/nova-novncproxy, line 10, in module sys.exit(main()) File /usr/lib/python2.7/dist-packages/nova/cmd/novncproxy.py, line 87, in main wrap_cmd=None) File /usr/lib/python2.7/dist-packages/nova/console/websocketproxy.py, line 38, in __init__ ssl_target=None, *args, **kwargs) File /usr/lib/python2.7/dist-packages/websockify/websocketproxy.py, line 231, in __init__ websocket.WebSocketServer.__init__(self, RequestHandlerClass, *args, **kwargs) TypeError: __init__() got an unexpected keyword argument 'no_parent' it seems there is a conflict with websockify. I'm running on debian wheezy amd64. If you need more information, please ask. regards, Axel Vanzaghi To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1333746/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333774] [NEW] Integration tests should allow for only running a subset
Public bug reported: At the moment you can only run all the integration tests. It should be possible to offer the same option than the unit tests, to only run a subset. http://docs.openstack.org/developer/horizon/ref/run_tests.html#running-a -subset-of-tests ** Affects: horizon Importance: Wishlist Assignee: Julie Pichon (jpichon) 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/1333774 Title: Integration tests should allow for only running a subset Status in OpenStack Dashboard (Horizon): In Progress Bug description: At the moment you can only run all the integration tests. It should be possible to offer the same option than the unit tests, to only run a subset. http://docs.openstack.org/developer/horizon/ref/run_tests.html#running-a -subset-of-tests To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333774/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333486] Re: Create Volume Snapshot incorrect infographic
** 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/1333486 Title: Create Volume Snapshot incorrect infographic Status in OpenStack Dashboard (Horizon): Invalid Bug description: Go to Project Volumes and click on 'Create Snapshot' from a volume you have. The infographic says Number of Volumes (2) -- 10. However, I have changed by Volume Snapshots quota (from Admin Projects Modify Quota tab). This graph is taking the *Volume* quota information instead of the *Volume Snapshot* quota information. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333486/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333827] [NEW] Libvirt-LXC can leave image mounted to host
Public bug reported: If an error occurs creating a Libvirt+LXC domain, the code can leave the guest FS mounted to host preventing the `lvremove` of a delete from working. The core problem here is that any code between `setup_container` and `teardown_container` needs be within a `try/finally` block, so that on error, we unmount the image from the host. While we're at it, we can also cleanup the exception handling by reducing the 3 independent exception handlers into a single one, which is then followed by the `finally` clause. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1333827 Title: Libvirt-LXC can leave image mounted to host Status in OpenStack Compute (Nova): New Bug description: If an error occurs creating a Libvirt+LXC domain, the code can leave the guest FS mounted to host preventing the `lvremove` of a delete from working. The core problem here is that any code between `setup_container` and `teardown_container` needs be within a `try/finally` block, so that on error, we unmount the image from the host. While we're at it, we can also cleanup the exception handling by reducing the 3 independent exception handlers into a single one, which is then followed by the `finally` clause. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1333827/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1332660] Re: Update statistics from computes if RBD ephemeral is used
Patch for 5.x (Icehouse) based on https://github.com/angdraug/nova/tree
/rbd-ephemeral-clone-stable-icehouse
** Patch added:
0001-Use-Ceph-cluster-stats-to-report-disk-info-on-RBD-icehouse.patch
https://bugs.launchpad.net/fuel/+bug/1332660/+attachment/4138381/+files/0001-Use-Ceph-cluster-stats-to-report-disk-info-on-RBD-icehouse.patch
** Also affects: fuel/4.1.x
Importance: Undecided
Status: New
** Also affects: fuel/5.0.x
Importance: Undecided
Status: New
** Changed in: fuel/4.1.x
Status: New = In Progress
** Changed in: fuel/5.0.x
Status: New = In Progress
** Changed in: fuel/4.1.x
Importance: Undecided = High
** Changed in: fuel/5.0.x
Importance: Undecided = High
** Changed in: fuel/4.1.x
Milestone: None = 4.1.2
** Changed in: fuel/5.0.x
Milestone: None = 5.0.1
** Changed in: fuel
Assignee: Dmitry Borodaenko (dborodaenko) = MOS Nova (mos-nova)
** Changed in: fuel/4.1.x
Assignee: (unassigned) = MOS Nova (mos-nova)
** Changed in: fuel/5.0.x
Assignee: (unassigned) = MOS Nova (mos-nova)
** Also affects: mos
Importance: Undecided
Status: New
** Changed in: mos
Status: New = In Progress
** Changed in: mos
Importance: Undecided = High
** Changed in: mos
Assignee: (unassigned) = MOS Nova (mos-nova)
** Changed in: mos
Milestone: None = 5.1
** Also affects: mos/5.0.x
Importance: Undecided
Status: New
** Changed in: mos/5.0.x
Status: New = In Progress
** Changed in: mos/5.0.x
Importance: Undecided = High
** Changed in: mos/5.0.x
Assignee: (unassigned) = MOS Nova (mos-nova)
** Changed in: mos/5.0.x
Milestone: None = 5.0.1
--
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/1332660
Title:
Update statistics from computes if RBD ephemeral is used
Status in Fuel: OpenStack installer that works:
In Progress
Status in Fuel for OpenStack 4.1.x series:
In Progress
Status in Fuel for OpenStack 5.0.x series:
In Progress
Status in Mirantis OpenStack:
In Progress
Status in Mirantis OpenStack 5.0.x series:
In Progress
Status in OpenStack Compute (Nova):
In Progress
Bug description:
If we use RBD as the backend for ephemeral drives, compute nodes still
calculate their available disk size looking back to the local disks.
This is the path how they do it:
* nova/compute/manager.py
def update_available_resource(self, context):
See driver.get_available_resource()
Periodic process that keeps that the compute host's understanding of
resource availability and usage in sync with the underlying
hypervisor.
:param context: security context
new_resource_tracker_dict = {}
nodenames = set(self.driver.get_available_nodes())
for nodename in nodenames:
rt = self._get_resource_tracker(nodename)
rt.update_available_resource(context)
new_resource_tracker_dict[nodename] = rt
def _get_resource_tracker(self, nodename):
rt = self._resource_tracker_dict.get(nodename)
if not rt:
if not self.driver.node_is_available(nodename):
raise exception.NovaException(
_(%s is not a valid node managed by this
compute host.) % nodename)
rt = resource_tracker.ResourceTracker(self.host,
self.driver,
nodename)
self._resource_tracker_dict[nodename] = rt
return rt
* nova/compute/resource_tracker.py
def update_available_resource(self, context):
Override in-memory calculations of compute node resource usage
based
on data audited from the hypervisor layer.
Add in resource claims in progress to account for operations that have
declared a need for resources, but not necessarily retrieved them from
the hypervisor layer yet.
LOG.audit(_(Auditing locally available compute resources))
resources = self.driver.get_available_resource(self.nodename)
* nova/virt/libvirt/driver.py
def get_local_gb_info():
Get local storage info of the compute node in GB.
:returns: A dict containing:
:total: How big the overall usable filesystem is (in gigabytes)
:free: How much space is free (in gigabytes)
:used: How much space is used (in gigabytes)
if CONF.libvirt_images_type == 'lvm':
info = libvirt_utils.get_volume_group_info(
CONF.libvirt_images_volume_group)
else:
info = libvirt_utils.get_fs_info(CONF.instances_path)
for (k, v) in
[Yahoo-eng-team] [Bug 1259011] Re: Certificates cannot be retrieved from the V3 API
** Also affects: keystonemiddleware Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1259011 Title: Certificates cannot be retrieved from the V3 API Status in OpenStack Identity (Keystone): Fix Released Status in OpenStack Identity (Keystone) Middleware: New Status in OpenStack API documentation site: Fix Released Status in Python client library for Keystone: New Bug description: Auth_token middleware relies upon the V2 api to provide the certificates that are required to validate PKI tokens because this information is not provided by the V3 API. Longer term i think we should be encouraging deployers to handle their own certificate distribution as fetching the certificates from the same source that is issuing tokens is not secure, however for the mean time we need some way of providing these certificates to token validators. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1259011/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1317302] Re: pki_setup shouldn't be required to check revocations
** Also affects: keystonemiddleware Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1317302 Title: pki_setup shouldn't be required to check revocations Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Identity (Keystone) Middleware: New Status in Python client library for Keystone: In Progress Bug description: With the fix for bug 1312858 , auth_token can validate UUID tokens or hashed PKI tokens against the revocation list. But in order to use this in a setting where only UUID tokens are being used, the server still needs to have pki_setup run. We should be able to check UUID tokens against the revocation list even when pki_setup hasn't been done. The reason pki_setup has to be done is that the revocation list is signed using CMS. The auth_token middleware only accepts the signed format for the revocation list. The proposed solution is to change the auth_token middleware to also accept a revocation list that's not signed. If it's not signed, then the PKI certificates aren't required. The keystone server will be changed to allow configuring it such that the revocation list will be sent as an unencrypted JSON object that the auth_token middleware can now accept. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1317302/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333920] [NEW] sshd can start before cloud-init injects keys
Public bug reported: Description of problem: When using automated scripts for deployment, many wait for sshd to come up, then ssh in. Since cloud-init and sshd are started in parallel, this creates a race condition for cloud-init to add ssh keys before sshd starts or the user can't login and the automated scripts can fail. Specifically, this is happening to me using test-kitchen with the kitchen-openstack plugin, which uses Fog. It calls wait_for and watches for sshd to come up. It catches sshd before cloud-init finishes installing keys, and fails to ssh. Reproducing: Attempt to ssh in before cloud-init finishes but after sshd is up and running. Steps to Reproduce: 1. Pull in Fedora Cloud image for OpenStack 2. Configure test kitchen to use Fedora 3. Run test-kitchen tests Actual results: ssh fails, which causes test-kitchen or other automated scripts to fail. Expected results: ssh should succeed. This is specifically affecting me on Fedora-20, but can potentially affect any distribution using systemd. ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1333920 Title: sshd can start before cloud-init injects keys Status in Init scripts for use on cloud images: New Bug description: Description of problem: When using automated scripts for deployment, many wait for sshd to come up, then ssh in. Since cloud-init and sshd are started in parallel, this creates a race condition for cloud-init to add ssh keys before sshd starts or the user can't login and the automated scripts can fail. Specifically, this is happening to me using test-kitchen with the kitchen-openstack plugin, which uses Fog. It calls wait_for and watches for sshd to come up. It catches sshd before cloud-init finishes installing keys, and fails to ssh. Reproducing: Attempt to ssh in before cloud-init finishes but after sshd is up and running. Steps to Reproduce: 1. Pull in Fedora Cloud image for OpenStack 2. Configure test kitchen to use Fedora 3. Run test-kitchen tests Actual results: ssh fails, which causes test-kitchen or other automated scripts to fail. Expected results: ssh should succeed. This is specifically affecting me on Fedora-20, but can potentially affect any distribution using systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1333920/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333927] [NEW] list of timezones is not localized
Public bug reported: On the Settings-User Settings panel the list of timezones is not translated. Region/Country names are always shown in English. ** 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/1333927 Title: list of timezones is not localized Status in OpenStack Dashboard (Horizon): New Bug description: On the Settings-User Settings panel the list of timezones is not translated. Region/Country names are always shown in English. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1333927/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1333971] [NEW] Block device usage is overly restrictive
Public bug reported: Version in use: Havana, but I believe the issue exists in IceHouse As per https://www.mail-archive.com/openstack- d...@lists.openstack.org/msg25179.html, I'd like to be able to specify multiple --image options (or rather the equivalent --block-device options). Further, I'd like to be able to specify a --image other than the first as the initial boot disk. The documentation for the nova boot command makes no reference to the number of --image/--block-device options being limited to 1, and indeed describes a --boot-index option to allow a non-first disk to be booted. However, using multiple options simply does not work. What seems to happen is that the last option specified is used. I suggest the following implementation: - an arbitrary number of --block-device (or equivalent --image, --sawp, --ephemeral or --block-device-mapping) options be allowed. - any --block-device of type image be allowed to take a boot-index option. The boot-index option(s) must start at 0, and must not exceed the number of block-devices of type images. Duplicate values are not allowed. - if no --block-device has a boot-index option, then the first such option shall default to --boot-index=0. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1333971 Title: Block device usage is overly restrictive Status in OpenStack Compute (Nova): New Bug description: Version in use: Havana, but I believe the issue exists in IceHouse As per https://www.mail-archive.com/openstack- d...@lists.openstack.org/msg25179.html, I'd like to be able to specify multiple --image options (or rather the equivalent --block-device options). Further, I'd like to be able to specify a --image other than the first as the initial boot disk. The documentation for the nova boot command makes no reference to the number of --image/--block-device options being limited to 1, and indeed describes a --boot-index option to allow a non-first disk to be booted. However, using multiple options simply does not work. What seems to happen is that the last option specified is used. I suggest the following implementation: - an arbitrary number of --block-device (or equivalent --image, --sawp, --ephemeral or --block-device-mapping) options be allowed. - any --block-device of type image be allowed to take a boot-index option. The boot-index option(s) must start at 0, and must not exceed the number of block-devices of type images. Duplicate values are not allowed. - if no --block-device has a boot-index option, then the first such option shall default to --boot-index=0. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1333971/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1334000] [NEW] Better exception handling in nuage plugin
Public bug reported: There are cases within the current nuage plugin code where upon exceptions the right error msgs are not reported back. While Nuage backend supports and supplies these errors correctly, plugin needs to proxy them back to users in a clean fashion. ** Affects: neutron Importance: Undecided Status: New ** Tags: nuage ** Tags added: nuage -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1334000 Title: Better exception handling in nuage plugin Status in OpenStack Neutron (virtual network service): New Bug description: There are cases within the current nuage plugin code where upon exceptions the right error msgs are not reported back. While Nuage backend supports and supplies these errors correctly, plugin needs to proxy them back to users in a clean fashion. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1334000/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1334024] [NEW] Nova rescue fails for libvirt driver with config drive
Public bug reported:
I am using config drive to boot VMs. In icehouse, I observed that nova
rescue fails and leaves the VM in SHUTOFF state.
Short error log:
/home/y/var/nova/instances/270e299b-90b2-46d5-bf9a-e7f6efe3742e/disk.config.rescue':
No such file or directory
Difference in Havana and Icehouse code path:
# Havana
# Config drive
if configdrive.required_by(instance):
LOG.info(_('Using config drive'), instance=instance)
extra_md = {}
if admin_pass:
extra_md['admin_pass'] = admin_pass
for f in ('user_name', 'project_name'):
if hasattr(context, f):
extra_md[f] = getattr(context, f, None)
inst_md = instance_metadata.InstanceMetadata(instance,
content=files, extra_md=extra_md, network_info=network_info)
with configdrive.ConfigDriveBuilder(instance_md=inst_md) as cdb:
configdrive_path = basepath(fname='disk.config')
LOG.info(_('Creating config drive at %(path)s'),
{'path': configdrive_path}, instance=instance)
def basepath(fname='', suffix=suffix): Adds suffix .rescue to
disk.config.
return os.path.join(libvirt_utils.get_instance_path(instance),
fname + suffix)
# Icehouse:
# Config drive
if configdrive.required_by(instance):
LOG.info(_('Using config drive'), instance=instance)
extra_md = {}
if admin_pass:
extra_md['admin_pass'] = admin_pass
for f in ('user_name', 'project_name'):
if hasattr(context, f):
extra_md[f] = getattr(context, f, None)
inst_md = instance_metadata.InstanceMetadata(instance,
content=files, extra_md=extra_md, network_info=network_info)
with configdrive.ConfigDriveBuilder(instance_md=inst_md) as cdb:
configdrive_path = self._get_disk_config_path(instance)
LOG.info(_('Creating config drive at %(path)s'),
{'path': configdrive_path}, instance=instance)
@staticmethod
def _get_disk_config_path(instance):
return os.path.join(libvirt_utils.get_instance_path(instance),
'disk.config')
The suffix .rescue is missed here and hence, original disk.config is
overwritten.
Following change fixed the issue for me:
configdrive_path = self._get_disk_config_path(instance, suffix)
@staticmethod
def _get_disk_config_path(instance, suffix=''):
return os.path.join(libvirt_utils.get_instance_path(instance),
'disk.config' + suffix)
Complete Error log:
{extra: {project_name: admin, timestamp: 2014-06-20T23:00:50.269421,
auth_token: 17fcde000c3040f9981e1804cdaf94fe, remote_address:
10.220.4.45, quota_class: null, is_admin: true, user:
dfac8c9e704a4312b0447b26b57a12da, service_catalog: [], tenant:
13b05759646b41c9a51660a1e653b146, user_id:
dfac8c9e704a4312b0447b26b57a12da, roles: [admin], project:
nova.compute.manager, instance: [instance:
270e299b-90b2-46d5-bf9a-e7f6efe3742e] , version: unknown, read_deleted:
no, request_id: req-a7f12cd9-dd23-48fa-9479-ab4e7825ae1e,
instance_lock_checked: false, project_id:
13b05759646b41c9a51660a1e653b146, user_name: spandhe}, thread_name:
GreenThread-31, process_name: MainProcess, name:
nova.compute.manager, thread: 82908816, created: 1403305252.7287409,
process: 26178, relative_created: 114349619.65203285, args: [],
traceback: [Traceback (most recent call last):, File
\/usr/lib/python2.6/site-packages/nova/compute/manager.py\, line 2983, in
rescue_instance, rescue_image_meta, admin_password), File
\/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py\, line 2205, in
rescue, self._create_domain(xml), File
\/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py\, line 3562, in
_create_domain, domain.XMLDesc(0)), File
\/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py\, line
68, in __exit__, six.reraise(self.type_, self.value, self.tb), File
\/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py\, line 3557, in
_create_domain, domain.createWithFlags(launch_flags), File
\/usr/lib/python2.6/site-packages/eventlet/tpool.py\, line 179, in doit,
result = proxy_call(self._autowrap, f, *args, **kwargs), File
\/usr/lib/python2.6/site-packages/eventlet/tpool.py\, line 139, in
proxy_call, rv = execute(f,*args,**kwargs), File
\/usr/lib/python2.6/site-packages/eventlet/tpool.py\, line 77, in tworker,
rv = meth(*args,**kwargs), File
\/usr/lib64/python2.6/site-packages/libvirt.py\, line 708, in
createWithFlags, if ret == -1: raise libvirtError
('virDomainCreateWithFlags() failed', dom=self), libvirtError: cannot open
file
'/home/y/var/nova/instances/270e299b-90b2-46d5-bf9a-e7f6efe3742e/disk.config.rescue':
No such
[Yahoo-eng-team] [Bug 1334031] [NEW] some security rule template names should be translated
Public bug reported: In Projects-Access Security-Security Groups-Manage Rules-Manage Rules-Add rule Security group rule templates with the word ALL should be translated, and probably don't need to be all caps. ** Affects: horizon Importance: Undecided Assignee: Doug Fish (drfish) 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/1334031 Title: some security rule template names should be translated Status in OpenStack Dashboard (Horizon): New Bug description: In Projects-Access Security-Security Groups-Manage Rules-Manage Rules-Add rule Security group rule templates with the word ALL should be translated, and probably don't need to be all caps. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1334031/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1334071] [NEW] capitalize compute service state
Public bug reported: Project System Info Compute Services tab State column should be capitalized for consistency. up = Up ** 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/1334071 Title: capitalize compute service state Status in OpenStack Dashboard (Horizon): New Bug description: Project System Info Compute Services tab State column should be capitalized for consistency. up = Up To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1334071/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1334075] [NEW] horizon doesn't support specify availability-zone when booting a instance
Public bug reported: availability-zone can be specified when using python-novaclient, it would be better to support it through horizon UI when booting an instance. ** Affects: horizon Importance: Undecided Status: New ** Description changed: - availability-zone can be specified when using python-novaclient, it be - better to support it through horizon UI when booting an instance. + availability-zone can be specified when using python-novaclient, it + would be better to support it through horizon UI when booting an + instance. -- 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/1334075 Title: horizon doesn't support specify availability-zone when booting a instance Status in OpenStack Dashboard (Horizon): New Bug description: availability-zone can be specified when using python-novaclient, it would be better to support it through horizon UI when booting an instance. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1334075/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1334075] Re: horizon doesn't support specify availability-zone when booting a instance
This functionality exists in the launch instance workflow. It defaults to any. ** 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/1334075 Title: horizon doesn't support specify availability-zone when booting a instance Status in OpenStack Dashboard (Horizon): Invalid Bug description: availability-zone can be specified when using python-novaclient, it would be better to support it through horizon UI when booting an instance. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1334075/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1266620] Re: bad english in string: Disabled reason contains invalid characters or is too long
** Changed in: openstack-i18n 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/1266620 Title: bad english in string: Disabled reason contains invalid characters or is too long Status in OpenStack Compute (Nova): Fix Released Status in OpenStack I18n L10n: Fix Released Bug description: This string: Disabled reason contains invalid characters or is too long found in nova/api/openstack/compute/contrib/services.py:177, nova/api/openstack/compute/plugins/v3/services.py:159 should be fixed. From the spanish translation team: Se recomienda que esta cadena sea reestructurada en su versión original, particularmente Disabled reason. Essentially, the string isn't the best English and should be re-written so it can be translated properly - particularly the use of Disabled reason. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1266620/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1224329] Re: I18n: strings in some table columns (e.g., Status, Task, Powerstate) are not translated
** Changed in: openstack-i18n 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/1224329 Title: I18n: strings in some table columns (e.g., Status, Task, Powerstate) are not translated Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack I18n L10n: Fix Released Bug description: There are many tables in Horizon. I noticed some columns are untranslated. For example, in the table of instances, strings in the column of Status, Task, and Power State are not translated. In the table of volumes, strings in the column of Status are not translated. In the table of images, strings in the column of Type, Status, Public, and Protected are not translated. Some of these strings are getting from database as code, for example Type and Status. Some of these strings are Yes and No. I think they should also be enabled i18n too. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1224329/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1334103] [NEW] when click a panel, other panels are expanded and collapsed
Public bug reported: In stable/icehouse: Steps to reproduce: 1. login as admin 2. Click Project Dashboard 3. Click Compute panel group to expand 4. Click Overview panel You will see that all other panel groups of the Project Dashboard are expandend and collapsed. Same situation occurs when clicking other panel. That is, when clicking a panel, all other panel groups of the clicked panel's parent dashboard are expanded and collapsed. ** 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/1334103 Title: when click a panel, other panels are expanded and collapsed Status in OpenStack Dashboard (Horizon): New Bug description: In stable/icehouse: Steps to reproduce: 1. login as admin 2. Click Project Dashboard 3. Click Compute panel group to expand 4. Click Overview panel You will see that all other panel groups of the Project Dashboard are expandend and collapsed. Same situation occurs when clicking other panel. That is, when clicking a panel, all other panel groups of the clicked panel's parent dashboard are expanded and collapsed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1334103/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1317838] Re: unable to evacuate on shared storage
For evacuate, the --on-shared-storage means whether the server files are located on shared storage, i.e. the /var/lib/nova/instances files as explained in this doc: http://docs.openstack.org/openstack- ops/content/compute_nodes.html#off_compute_node_storage If you're using cinder, that's a service to provide block storage to users via volumes described here: http://docs.openstack.org/openstack- ops/content/storage_decision.html#block_storage If you have a suggestion about how the documentation could be made clearer, please reply to this bug. ** Changed in: nova Status: New = Invalid -- 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/1317838 Title: unable to evacuate on shared storage Status in OpenStack Compute (Nova): Invalid Bug description: debian testing 3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux libvirt 1.2.4 nova-compute 2014.1-4 shared storage on cinder with ceph Basicly, when I'm running nova evacuate instance id host id --on- shared-storage program exits with code 0. You can find all attached command and log output in gist - https://gist.github.com/szymonpk/de6380ac24caba8792b1. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1317838/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
