Activity log for bug #1486553

Date Who What changed Old value New value Message
2015-08-19 12:49:27 Данило Шеган bug added bug
2015-08-19 15:36:54 Dimiter Naydenov juju-core: status New Triaged
2015-08-19 15:37:03 Dimiter Naydenov juju-core: importance Undecided High
2015-08-19 15:37:08 Dimiter Naydenov juju-core: milestone 1.26.0
2015-08-26 00:50:05 Andreas Hasenack tags cisco landscape
2015-08-26 00:50:18 Andreas Hasenack bug added subscriber Landscape
2015-08-27 07:36:17 Dimiter Naydenov juju-core: milestone 1.26.0
2015-08-27 14:43:23 Curtis Hovey juju-core: milestone 1.26.0
2015-09-01 18:24:56 Nate Finch juju-core: assignee Nate Finch (natefinch)
2015-09-02 20:51:39 Nate Finch juju-core: status Triaged In Progress
2015-09-02 21:07:01 Andreas Hasenack description We've recently started seeing "i/o timeout errors" when issuing serviceDeploy API calls from Landscape: Aug 7 20:45:06 job-handler-1 INFO Traceback (failure with no frames): <class 'canonical.juju.errors.RequestError'>: cannot add service "mongodb": read tcp 127.0.0.1:37017: i/o timeout ... Aug 7 20:45:06 job-handler-1 INFO Traceback (failure with no frames): <class 'canonical.juju.errors.RequestError'>: cannot add service "hacluster-mysql": read tcp 192.168.216.21:37017: i/o timeout ... On retry, we hit the "service already exists" error, so the service has actually been deployed. However, recently, we've also hit a case where service was only partially deployed: Aug 17 16:22:18 job-handler-1 INFO Traceback (failure with no frames): <class 'canonical.juju.errors.RequestError'>: cannot add service "ceph-radosgw": read tcp 127.0.0.1:37017: i/o timeout We emit a service deploy call together with the full service configuration, but no service configuration was done in this case. It seems as if service deploy and configuration are not atomic: we'd expect the call to either fail (so we don't hit service-already-exists error later) or to succeed *fully* (including configuration) even if it fails to report back to the client due to network issues. See bug 1482791 for reference. We've recently started seeing "i/o timeout errors" when issuing serviceDeploy API calls from Landscape: EDIT ########## To clarify: landscape ---------> |17070:state server -> mongo:37017| The timeout is happening inside the juju state server box, between the api and mongo. It's NOT happening between landscape and juju. It's inside juju. ########## Aug 7 20:45:06 job-handler-1 INFO Traceback (failure with no frames): <class 'canonical.juju.errors.RequestError'>: cannot add service "mongodb": read tcp 127.0.0.1:37017: i/o timeout ... Aug 7 20:45:06 job-handler-1 INFO Traceback (failure with no frames): <class 'canonical.juju.errors.RequestError'>: cannot add service "hacluster-mysql": read tcp 192.168.216.21:37017: i/o timeout ... On retry, we hit the "service already exists" error, so the service has actually been deployed. However, recently, we've also hit a case where service was only partially deployed: Aug 17 16:22:18 job-handler-1 INFO Traceback (failure with no frames): <class 'canonical.juju.errors.RequestError'>: cannot add service "ceph-radosgw": read tcp 127.0.0.1:37017: i/o timeout We emit a service deploy call together with the full service configuration, but no service configuration was done in this case. It seems as if service deploy and configuration are not atomic: we'd expect the call to either fail (so we don't hit service-already-exists error later) or to succeed *fully* (including configuration) even if it fails to report back to the client due to network issues. See bug 1482791 for reference.
2015-09-03 14:36:09 Katherine Cox-Buday nominated for series juju-core/1.25
2015-09-03 14:36:09 Katherine Cox-Buday bug task added juju-core/1.25
2015-09-03 14:37:58 Katherine Cox-Buday juju-core/1.25: milestone 1.25-beta1
2015-09-03 14:40:54 Katherine Cox-Buday juju-core/1.25: importance Undecided High
2015-09-03 14:41:09 Katherine Cox-Buday juju-core/1.25: assignee Nate Finch (natefinch)
2015-09-03 14:41:18 Katherine Cox-Buday juju-core/1.25: status New In Progress
2015-09-03 14:41:24 Katherine Cox-Buday juju-core: status In Progress Triaged
2015-09-03 14:41:28 Katherine Cox-Buday juju-core: assignee Nate Finch (natefinch)
2015-09-06 22:32:02 Menno Finlay-Smits bug added subscriber Menno Smits
2015-09-11 16:04:31 Nate Finch juju-core: assignee Nate Finch (natefinch)
2015-09-11 16:04:35 Nate Finch juju-core: status Triaged In Progress
2015-09-11 18:13:47 Katherine Cox-Buday nominated for series juju-core/1.24
2015-09-11 18:13:47 Katherine Cox-Buday bug task added juju-core/1.24
2015-09-11 18:13:58 Katherine Cox-Buday juju-core/1.24: milestone 1.24.6
2015-09-11 18:14:03 Katherine Cox-Buday juju-core/1.24: importance Undecided Critical
2015-09-11 18:14:28 Katherine Cox-Buday juju-core/1.24: assignee Nate Finch (natefinch)
2015-09-11 18:17:18 Katherine Cox-Buday juju-core/1.24: status New In Progress
2015-09-11 20:22:53 Katherine Cox-Buday juju-core/1.24: status In Progress Fix Committed
2015-09-17 00:11:10 Curtis Hovey juju-core/1.24: status Fix Committed Fix Released
2015-09-21 15:37:55 Nate Finch juju-core/1.25: status In Progress Fix Committed
2015-09-24 22:53:44 Curtis Hovey juju-core/1.25: status Fix Committed Fix Released
2015-10-02 03:48:11 David Britton tags cisco landscape cisco kanban-cross-team landscape
2015-10-02 03:49:37 David Britton tags cisco kanban-cross-team landscape cisco landscape
2015-12-07 04:27:47 Cheryl Jennings juju-core: milestone 1.26.0 2.0-alpha1
2016-01-12 03:27:23 Nate Finch juju-core: status In Progress Fix Committed
2016-01-20 16:31:29 Curtis Hovey juju-core: status Fix Committed Fix Released
2016-08-23 01:23:21 Canonical Juju QA Bot affects juju-core juju
2016-08-23 01:23:21 Canonical Juju QA Bot juju: milestone 2.0-alpha1
2016-08-23 01:23:25 Canonical Juju QA Bot juju: milestone 2.0-alpha1
2016-08-23 13:26:28 Canonical Juju QA Bot juju-core: importance Undecided High
2016-08-23 13:26:28 Canonical Juju QA Bot juju-core: status New Fix Released
2016-08-23 13:26:28 Canonical Juju QA Bot juju-core: assignee Nate Finch (natefinch)