When I run this against a blank model, the bundle deployment continues onward. The step that is just after the timeout outputs:
DEBUG juju.cmd.juju.application bundle.go:273 model: &bundlechanges.Model{ Applications: { }, Machines: { }, Relations: nil, ConstraintsEqual: func(string, string) bool {...}, Sequence: {}, sequence: {}, MachineMap: {}, logger: nil, }
then it continues on to resolve charm URLs as the next step.
perhaps the bundlechanges.Model is bombing out during generation by the server causing connection abort.
When I run this against a blank model, the bundle deployment continues onward. The step that is just after the timeout outputs:
DEBUG juju.cmd. juju.applicatio n bundle.go:273 model: &bundlechanges. Model{ Equal: func(string, string) bool {...},
Applications: {
},
Machines: {
},
Relations: nil,
Constraints
Sequence: {},
sequence: {},
MachineMap: {},
logger: nil,
}
then it continues on to resolve charm URLs as the next step.
perhaps the bundlechanges.Model is bombing out during generation by the server causing connection abort.