Comment 7 for bug 1745951

Hi John,

I think you're right. As soon as I add the agent-version-flag, it disappears, but crashes later on.

Kevin

> Am 29.01.2018 um 12:15 schrieb John A Meinel <email address hidden>:
>
> I'm not sure why exactly this is happening. Some things that seem odd from
> your logs:
> Looking for packaged Juju agent version <nil> for amd64
>
> Why would we be looking for a "<nil>" version agent? I would have expected
> that we would be looking at the clients Version information which is
> clearly:
> 10:38:06 INFO juju.cmd supercommand.go:56 running juju [2.3.1 gc go1.9.2]
>
> Going further, the error you are seeing is from this code:
> func (cfg *InstanceConfig) SetTools(toolsList coretools.List) error {
> if len(toolsList) == 0 {
> return errors.New("need at least 1 agent binary")
> }
> var tools *coretools.Tools
> for _, listed := range toolsList {
> if listed == nil {
> return errors.New("nil entry in agent binaries list")
> }
> info := *listed
> info.URL = ""
> if tools == nil {
> tools = &info
> continue
> }
> if !reflect.DeepEqual(info, *tools) {
> return errors.Errorf("agent binary info mismatch (%v, %v)",
> *tools, info)
> }
> }
> cfg.tools = copyToolsList(toolsList)
> return nil
> }
> Which if I read it correctly, is essentially saying the version of every
> entry in the list should match.
> I have the feeling the issue goes back to that original "nil" might be part
> of the problem.
>
>
> On Mon, Jan 29, 2018 at 2:26 PM, Kevin Wennemuth <<email address hidden>
>> wrote:
>
>> This also happens on juju 2.3.1
>>
>> --
>> You received this bug notification because you are subscribed to juju.
>> Matching subscriptions: juju bugs
>> https://bugs.launchpad.net/bugs/1745951
>>
>> Title:
>> cannot start bootstrap instance: agent binary info mismatch
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/juju/+bug/1745951/+subscriptions
>>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745951
>
> Title:
> cannot start bootstrap instance: agent binary info mismatch
>
> Status in juju:
> New
>
> Bug description:
> juju bootstrap --auto-upgrade --config=./lab.yaml vsphere juju
> Creating Juju controller "juju" on vsphere/esx.power.lab
> Looking for packaged Juju agent version <nil> for amd64
> Launching controller instance(s) on vsphere/esx.power.lab...
> ERROR failed to bootstrap model: cannot start bootstrap instance: agent binary info mismatch ({2.3.0-xenial-amd64 0dbc7bafc0bb9b6d62846d617591755e50547f13e16881d6571d39b31b20335a 28011270}, {2.3.1-xenial-amd64 72bed4104b050a63f1d026a889d8fc9bdfb13f9b04b47ef3b762967774e1a187 28017324})
>
>
> lab.yml
> -----------
> ---
> primary-network: "VM Network"
> external-network: "VM Network"
> datastore: ds00
>
> any hints on this?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1745951/+subscriptions