[Yahoo-eng-team] [Bug 1274661] Re: Alt-shift does not change keyboard layout to Hungarian from English
** Project changed: horizon => unity ** Changed in: unity Status: Invalid => 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/1274661 Title: Alt-shift does not change keyboard layout to Hungarian from English Status in Unity: New Bug description: Alt-shift does not change keyboard layout to Hungarian from English. Pressing these keys does nothing. Clicking on the keyboard layout icon on the trey in Unity does nothing. It opens, EN is visible, even if I click on it, HU will be visible again. After a 4-5 minutes it is possible to use Alt-Shift to change to Hungarian. Ubuntu 13.10. Firefox 26.0 Unity: Architecture: amd64 Version: 7.1.2+13.10.20131014.1-0ubuntu1 Same bug is for PCBSD 10.0 release version Sometimes if Hungarian succeed, on many webpages (i.e jobportals) using some special keys by AltGr will mark the full line and delete it, because it is marked, pressing a key will delete the marked characters. After a while it is ok again without pressing anything. Sometimes it opens the run console at the top when using Firefox. Waits a while and then closes it again like if it would be locked. Looks like that a puffer takes typed characters but in some cases it is not flushed for some seconds... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1274661/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1257517] Re: Incorrect tenant id returned to neutron when deleting a subnet
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1257517 Title: Incorrect tenant id returned to neutron when deleting a subnet Status in OpenStack Neutron (virtual network service): Expired Bug description: Create a new user through Horizon, create a network and subnet in it. Launch instances on the network created. Now, when you try to delete the subnet (after deleting VMs), a different tenant-id is returned. You can see from logs that a subnet with wrong tenant-id gets deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1257517/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1192786] Re: WARNING [QUANTUM.DB.AGENTSCHEDULERS_DB] FAIL SCHEDULING NETWORK
** Also affects: neutron/havana
Importance: Undecided
Status: New
** Changed in: neutron/havana
Assignee: (unassigned) => Francois Deppierraz (francois-ctrlaltdel)
** Changed in: neutron/havana
Importance: Undecided => Medium
** Changed in: neutron/havana
Status: New => In Progress
** Tags removed: havana-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1192786
Title:
WARNING [QUANTUM.DB.AGENTSCHEDULERS_DB] FAIL SCHEDULING NETWORK
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in neutron havana series:
In Progress
Bug description:
when i boot a new instance, i got a error message, and Everything is
running normal but the error is still present
2013-06-20 02:41:39 WARNING [quantum.db.agentschedulers_db] Fail
scheduling network {'status': u'ACTIVE', 'subnets':
[u'9a1c3be6-4678-4cf7-85e8-494b49fa40b7'], 'name': u'vlan3001',
'provider:physical_network': u'physnet1', 'admin_state_up': True,
'tenant_id': u'71eedd4d59384d13b7c80cdfb4999bf0',
'provider:network_type': u'vlan', 'router:external': False, 'shared':
True, 'id': u'8717d0e0-d17e-4262-ab3e-2a423d71bae4',
'provider:segmentation_id': 3001L} 2013-06-20 02:41:40 WARNING
[quantum.db.agentschedulers_db] Fail scheduling network {'status':
u'ACTIVE', 'subnets': [u'5c8ac388-972d-4599-a0f9-ad4cc7fa720f'],
'name': u'vlan3501', 'provider:physical_network': u'physnet2',
'admin_state_up': True, 'tenant_id':
u'71eedd4d59384d13b7c80cdfb4999bf0', 'provider:network_type': u'vlan',
'router:external': False, 'shared': True, 'id': u'5b18231f-8a3a-4c5a-
b6a8-a4773f45c695', 'provider:segmentation_id': 3501L}
if i check agent-list, the Open vSwitch agent on compute is up and
down every several seconds.
date;quantum agent-list <<<
Thu Jun 20 02:40:02 UTC 2013
+--++-+---++
| id | agent_type | host | alive | admin_state_up |
+--++-+---++
| 31e422a4-833c-47fd-8be2-aa71471999a0 | L3 agent | h172-16-0-2 | :-)
| True | | 4a26d0b7-23aa-4b84-96e2-295bd9aff9db | DHCP agent |
h172-16-0-2 | :-) | True | | 67f74ab1-f5b1-4944-8acf-f4b9eefa88ac |
Open vSwitch agent | h172-16-0-2 | :-) | True | | 99c9f8a2-587f-42ec-
ac51-cc2bdc6cad5a | Open vSwitch agent | h172-16-0-3 | xxx | True |
+--++-+---++
date;quantum agent-list <<<
Thu Jun 20 02:40:04 UTC 2013
+--++-+---++
| id | agent_type | host | alive | admin_state_up |
+--++-+---++
| 31e422a4-833c-47fd-8be2-aa71471999a0 | L3 agent | h172-16-0-2 | :-)
| True | | 4a26d0b7-23aa-4b84-96e2-295bd9aff9db | DHCP agent |
h172-16-0-2 | :-) | True | | 67f74ab1-f5b1-4944-8acf-f4b9eefa88ac |
Open vSwitch agent | h172-16-0-2 | :-) | True | | 99c9f8a2-587f-42ec-
ac51-cc2bdc6cad5a | Open vSwitch agent | h172-16-0-3 | :-) | True |
+--++-+---++
date;quantum agent-list <<<
Thu Jun 20 02:40:09 UTC 2013
+--++-+---++
| id | agent_type | host | alive | admin_state_up |
+--++-+---++
| 31e422a4-833c-47fd-8be2-aa71471999a0 | L3 agent | h172-16-0-2 | :-)
| True | | 4a26d0b7-23aa-4b84-96e2-295bd9aff9db | DHCP agent |
h172-16-0-2 | :-) | True | | 67f74ab1-f5b1-4944-8acf-f4b9eefa88ac |
Open vSwitch agent | h172-16-0-2 | :-) | True | | 99c9f8a2-587f-42ec-
ac51-cc2bdc6cad5a | Open vSwitch agent | h172-16-0-3 | xxx | True |
+--++-+---++
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1192786/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1192381] Re: dhcp dnsmasq lost port in host config file
** Also affects: neutron/havana Importance: Undecided Status: New ** Changed in: neutron/havana Importance: Undecided => Critical ** Changed in: neutron/havana Status: New => In Progress ** Changed in: neutron/havana Assignee: (unassigned) => Maru Newby (maru) ** Tags removed: havana-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1192381 Title: dhcp dnsmasq lost port in host config file Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron havana series: In Progress Bug description: Version: Stable/Grizzly In sometimes, If start up 5 vm, and each one has 2 nics, some of their nics could got a IP address from dhcp-agent. Run dhclient or ipconfig /renew couldn't work around. And I found there's no related port MAC in their dnsmasq config file => host, that caused this issue. And the work around method is delete the VM, create again. Or, kill all of the dnsmasq processes and dhcp-agent, then start them again. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1192381/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275352] [NEW] test_migration_utils runs sqlite tests even if no sqlite configured
Public bug reported:
There are several jobs that only run if you have sqlite configured in
nova.tests.db.test_migration_utils but there are two which will run and
fail if you don't have sqlite configured:
==
ERROR:
nova.tests.db.test_migration_utils.TestMigrationUtils.test_check_shadow_table_with_unsupported_type
--
_StringException: pythonlogging:'': {{{INFO [nova.tests.db.test_migrations]
Creating DB2 schema nova.novatstu}}}
Traceback (most recent call last):
File "/root/nova-es/nova/tests/db/test_migration_utils.py", line 391, in
test_check_shadow_table_with_unsupported_type
engine = self.engines['sqlite']
KeyError: 'sqlite'
==
ERROR:
nova.tests.db.test_migration_utils.TestMigrationUtils.test_util_drop_unique_constraint_with_not_supported_sqlite_type
--
_StringException: pythonlogging:'': {{{INFO [nova.tests.db.test_migrations]
Creating DB2 schema nova.novatstu}}}
Traceback (most recent call last):
File "/root/nova-es/nova/tests/db/test_migration_utils.py", line 215, in
test_util_drop_unique_constraint_with_not_supported_sqlite_type
for i in xrange(0, len(values)):
UnboundLocalError: local variable 'values' referenced before assignment
Those should be skipped if sqlite isn't configured like the other
sqlite-specific tests.
** Affects: nova
Importance: Undecided
Assignee: Matt Riedemann (mriedem)
Status: In Progress
** Tags: db testing
** Changed in: nova
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1275352
Title:
test_migration_utils runs sqlite tests even if no sqlite configured
Status in OpenStack Compute (Nova):
In Progress
Bug description:
There are several jobs that only run if you have sqlite configured in
nova.tests.db.test_migration_utils but there are two which will run
and fail if you don't have sqlite configured:
==
ERROR:
nova.tests.db.test_migration_utils.TestMigrationUtils.test_check_shadow_table_with_unsupported_type
--
_StringException: pythonlogging:'': {{{INFO [nova.tests.db.test_migrations]
Creating DB2 schema nova.novatstu}}}
Traceback (most recent call last):
File "/root/nova-es/nova/tests/db/test_migration_utils.py", line 391, in
test_check_shadow_table_with_unsupported_type
engine = self.engines['sqlite']
KeyError: 'sqlite'
==
ERROR:
nova.tests.db.test_migration_utils.TestMigrationUtils.test_util_drop_unique_constraint_with_not_supported_sqlite_type
--
_StringException: pythonlogging:'': {{{INFO [nova.tests.db.test_migrations]
Creating DB2 schema nova.novatstu}}}
Traceback (most recent call last):
File "/root/nova-es/nova/tests/db/test_migration_utils.py", line 215, in
test_util_drop_unique_constraint_with_not_supported_sqlite_type
for i in xrange(0, len(values)):
UnboundLocalError: local variable 'values' referenced before assignment
Those should be skipped if sqlite isn't configured like the other
sqlite-specific tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1275352/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275311] [NEW] Libvirt BIOS bootmenu should be enabled
Public bug reported: We currently do not enable the "bootmenu" option within Libvirt. It would be beneficial to do so, to allow for some more flexibility when installing a new OS from ISO. Having the bootmenu available would allow for the following: 1. Upload ISO image to Glance. 2. Upload "empty" RAW image to Glance. 3. Create a new Cinder volume, populating it with the ISO from #1. 4. Create a new instance, using the empty RAW from #2. 5. Attach the CInder volume from #3. At this point, the instance has 2 disks attached: the root disk (vda) and volume (vdb). In this case, we want to boot vdb, so that we can utilize the ISO to install an OS on vda. There is currently no way to do this, short of passing block-device-mapping, which is not the same end result. Enabling the bootmenu would prompt the user to hit F12 and select the desired boot device (vdb in this case). This is an extremely simple change which provides a non-external option for creating Nova compatible images. ** Affects: nova Importance: Undecided Assignee: Rafi Khardalian (rkhardalian) Status: New ** Changed in: nova Assignee: (unassigned) => Rafi Khardalian (rkhardalian) -- 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/1275311 Title: Libvirt BIOS bootmenu should be enabled Status in OpenStack Compute (Nova): New Bug description: We currently do not enable the "bootmenu" option within Libvirt. It would be beneficial to do so, to allow for some more flexibility when installing a new OS from ISO. Having the bootmenu available would allow for the following: 1. Upload ISO image to Glance. 2. Upload "empty" RAW image to Glance. 3. Create a new Cinder volume, populating it with the ISO from #1. 4. Create a new instance, using the empty RAW from #2. 5. Attach the CInder volume from #3. At this point, the instance has 2 disks attached: the root disk (vda) and volume (vdb). In this case, we want to boot vdb, so that we can utilize the ISO to install an OS on vda. There is currently no way to do this, short of passing block-device-mapping, which is not the same end result. Enabling the bootmenu would prompt the user to hit F12 and select the desired boot device (vdb in this case). This is an extremely simple change which provides a non-external option for creating Nova compatible images. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275311/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275301] [NEW] Error during file injection if libguestfs is installed
Public bug reported:
Since devstack patch 43d95084376913 landed, which installed and enabled
libguestfs on Ubuntu, several tempest tests in the ironic and neutron
pipelines have been failing with "Error mounting
/opt/stack/data/nova/instances/{UUID}/disk with libguestfs". This seems
to be happening because Nova is trying to use file injection with
libguestfs instead of nbd now.
Traceback:
http://paste.openstack.org/show/62297/
Code:
https://git.openstack.org/cgit/openstack/nova/tree/nova/virt/libvirt/driver.py#n2564
Links to a few failures:
http://logs.openstack.org/96/66796/10/check/check-tempest-dsvm-ironic-nv/88c3fff/logs/screen-n-cpu.txt.gz?level=TRACE
http://logs.openstack.org/98/69798/2/check/check-tempest-dsvm-ironic-nv/103f6d8/logs/screen-n-cpu.txt.gz?level=TRACE
** Affects: nova
Importance: Undecided
Status: New
** Summary changed:
- Error mounting libguestfs
+ Error during file injection if libguestfs is installed
--
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/1275301
Title:
Error during file injection if libguestfs is installed
Status in OpenStack Compute (Nova):
New
Bug description:
Since devstack patch 43d95084376913 landed, which installed and
enabled libguestfs on Ubuntu, several tempest tests in the ironic and
neutron pipelines have been failing with "Error mounting
/opt/stack/data/nova/instances/{UUID}/disk with libguestfs". This
seems to be happening because Nova is trying to use file injection
with libguestfs instead of nbd now.
Traceback:
http://paste.openstack.org/show/62297/
Code:
https://git.openstack.org/cgit/openstack/nova/tree/nova/virt/libvirt/driver.py#n2564
Links to a few failures:
http://logs.openstack.org/96/66796/10/check/check-tempest-dsvm-ironic-nv/88c3fff/logs/screen-n-cpu.txt.gz?level=TRACE
http://logs.openstack.org/98/69798/2/check/check-tempest-dsvm-ironic-nv/103f6d8/logs/screen-n-cpu.txt.gz?level=TRACE
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1275301/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1274661] Re: Alt-shift does not change keyboard layout to Hungarian from English
Probably a mistargeted project - this has nothing to do with Horizon. ** 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/1274661 Title: Alt-shift does not change keyboard layout to Hungarian from English Status in OpenStack Dashboard (Horizon): Invalid Bug description: Alt-shift does not change keyboard layout to Hungarian from English. Pressing these keys does nothing. Clicking on the keyboard layout icon on the trey in Unity does nothing. It opens, EN is visible, even if I click on it, HU will be visible again. After a 4-5 minutes it is possible to use Alt-Shift to change to Hungarian. Ubuntu 13.10. Firefox 26.0 Unity: Architecture: amd64 Version: 7.1.2+13.10.20131014.1-0ubuntu1 Same bug is for PCBSD 10.0 release version Sometimes if Hungarian succeed, on many webpages (i.e jobportals) using some special keys by AltGr will mark the full line and delete it, because it is marked, pressing a key will delete the marked characters. After a while it is ok again without pressing anything. Sometimes it opens the run console at the top when using Firefox. Waits a while and then closes it again like if it would be locked. Looks like that a puffer takes typed characters but in some cases it is not flushed for some seconds... To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1274661/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275267] [NEW] GuestFS fails to mount image for data injection
Public bug reported: A GuestFS error is causing injection to fail. This result in a warning for metadata injection but results in a spawn error for key injection. This is logged with debug level: Exception AttributeError: "GuestFS instance has no attribute '_o'" in > ignored febootstrap-supermin-helper: ext2: parent directory not found: /lib: File not found by ext2_lookup And causes this error: http://paste.openstack.org/show/62293/ Full logs available here: http://logs.openstack.org/58/63558/8/check /check-tempest-dsvm-neutron-pg/108e4ca/logs Interestingly, it seems guestfs was not actually used when the relevant patches went throught the gate checks: https://review.openstack.org/#/c/70237/ https://review.openstack.org/#/c/70354/ This was expected for patch #70354 but sounds strange for patch #70237 Finally, The traceback seeems different from that of bug 1221985 ** 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/1275267 Title: GuestFS fails to mount image for data injection Status in OpenStack Compute (Nova): New Bug description: A GuestFS error is causing injection to fail. This result in a warning for metadata injection but results in a spawn error for key injection. This is logged with debug level: Exception AttributeError: "GuestFS instance has no attribute '_o'" in > ignored febootstrap-supermin-helper: ext2: parent directory not found: /lib: File not found by ext2_lookup And causes this error: http://paste.openstack.org/show/62293/ Full logs available here: http://logs.openstack.org/58/63558/8/check /check-tempest-dsvm-neutron-pg/108e4ca/logs Interestingly, it seems guestfs was not actually used when the relevant patches went throught the gate checks: https://review.openstack.org/#/c/70237/ https://review.openstack.org/#/c/70354/ This was expected for patch #70354 but sounds strange for patch #70237 Finally, The traceback seeems different from that of bug 1221985 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275267/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1275256] [NEW] failed to reach SHELVED_OFFLOADED status during dsvm postgres gate
Public bug reported: I added 2 log messages to glance and then my gate broke. It looks like it got stuck in "SHELVED" and failed to reach "SHELVED_OFFLOADED", although I lack the knowledge to know what this really means. I'm not even sure if this bug belongs in nova or elsewhere. http://logs.openstack.org/89/68189/9/gate/gate-tempest-dsvm-postgres- full/ff84764/console.html Traceback (most recent call last): 2014-02-01 09:59:15.116 | File "tempest/api/compute/v3/servers/test_servers_negative.py", line 403, in test_shelve_shelved_server 2014-02-01 09:59:15.116 | extra_timeout=offload_time) 2014-02-01 09:59:15.116 | File "tempest/services/compute/v3/json/servers_client.py", line 169, in wait_for_server_status 2014-02-01 09:59:15.116 | raise_on_error=raise_on_error) 2014-02-01 09:59:15.116 | File "tempest/common/waiters.py", line 89, in wait_for_server_status 2014-02-01 09:59:15.116 | raise exceptions.TimeoutException(message) 2014-02-01 09:59:15.116 | TimeoutException: Request timed out 2014-02-01 09:59:15.116 | Details: Server d193bafb-11cf-4592-8be7-174d2f94a68d failed to reach SHELVED_OFFLOADED status and task state "None" within the required time (196 s). Current status: SHELVED. Current task state: None. 2014-02-01 09:59:15.116 | ** 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/1275256 Title: failed to reach SHELVED_OFFLOADED status during dsvm postgres gate Status in OpenStack Compute (Nova): New Bug description: I added 2 log messages to glance and then my gate broke. It looks like it got stuck in "SHELVED" and failed to reach "SHELVED_OFFLOADED", although I lack the knowledge to know what this really means. I'm not even sure if this bug belongs in nova or elsewhere. http://logs.openstack.org/89/68189/9/gate/gate-tempest-dsvm-postgres- full/ff84764/console.html Traceback (most recent call last): 2014-02-01 09:59:15.116 | File "tempest/api/compute/v3/servers/test_servers_negative.py", line 403, in test_shelve_shelved_server 2014-02-01 09:59:15.116 | extra_timeout=offload_time) 2014-02-01 09:59:15.116 | File "tempest/services/compute/v3/json/servers_client.py", line 169, in wait_for_server_status 2014-02-01 09:59:15.116 | raise_on_error=raise_on_error) 2014-02-01 09:59:15.116 | File "tempest/common/waiters.py", line 89, in wait_for_server_status 2014-02-01 09:59:15.116 | raise exceptions.TimeoutException(message) 2014-02-01 09:59:15.116 | TimeoutException: Request timed out 2014-02-01 09:59:15.116 | Details: Server d193bafb-11cf-4592-8be7-174d2f94a68d failed to reach SHELVED_OFFLOADED status and task state "None" within the required time (196 s). Current status: SHELVED. Current task state: None. 2014-02-01 09:59:15.116 | To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1275256/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
