juju local bootstrap from tip

[John Meinel]

Right, I think it has to *know* about the target, which is obviously an
issue here. But we still do *heavily* encourage (probably just outright
require) cloud-archive:tools for running Juju agents on Precise.

John
=:->


On Mon, Sep 1, 2014 at 10:46 AM, Andrew Wilkins <
andrew.wilkins at canonical.com> wrote:

> On Mon, Sep 1, 2014 at 2:04 PM, John Meinel <john at arbash-meinel.com>
> wrote:
>
>> I thought --target-release was supposed to just change the priorities and
>> prefer a target, not require it.
>> We need it because we add cloud-archive:tools but we explicitly pin it to
>> lower priority because we don't want to mess up charms that we are
>> installing.
>>
>
> Sorry, I should have included the error message.
>
> andrew at precise:~$ sudo apt-get --option=Dpkg::Options::=--force-confold
> --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install
> --target-release precise-updates/cloud-tools mongodb-server
> Reading package lists...
> E: The value 'precise-updates/cloud-tools' is invalid for
> APT::Default-Release as such a release is not available in the sources
>
> (if I "apt-add-repository cloud-archive:tools", it's happy)
>
> John
>> =:->
>>
>>
>> On Mon, Sep 1, 2014 at 9:57 AM, Andrew Wilkins <
>> andrew.wilkins at canonical.com> wrote:
>>
>>> On Mon, Sep 1, 2014 at 1:50 PM, John Meinel <john at arbash-meinel.com>
>>> wrote:
>>>
>>>> The version of mongodb in Precise is too old (2.2.4?),
>>>>
>>>
>>> Ah, so it is. The entry in apt-cache I was looking at has "main" in it,
>>> but it's actually from the juju/stable PPA.
>>>
>>>
>>>> we require a version at least 2.4.6 (which is in cloud-archive:tools
>>>> and is what we use when bootstrapping Precise instances in the cloud).
>>>> It is recommended that if you are running local on Precise that you
>>>> should have cloud-archive:tools in your apt list.
>>>>
>>>
>>> The problem is, code-wise it's currently a requirement. Should we drop
>>> --target-release for local? I'm not apt-savvy enough to know what the right
>>> thing to do here is.
>>>
>>>
>>>> John
>>>> =:->
>>>>
>>>>
>>>> On Mon, Sep 1, 2014 at 9:16 AM, Andrew Wilkins <
>>>> andrew.wilkins at canonical.com> wrote:
>>>>
>>>>> On Mon, Sep 1, 2014 at 12:53 PM, Andrew Wilkins <
>>>>> andrew.wilkins at canonical.com> wrote:
>>>>>
>>>>>> Works fine on my trusty laptop, but I'm also getting a new error when
>>>>>> I try bootstrapping on precise:
>>>>>>
>>>>>> 2014-09-01 04:51:27 INFO juju.utils.apt apt.go:132 Running: [apt-get
>>>>>> --option=Dpkg::Options::=--force-confold
>>>>>> --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install
>>>>>> --target-release precise-updates/cloud-tools mongodb-server]
>>>>>> 2014-09-01 04:51:37 ERROR juju.utils.apt apt.go:166 apt-get command
>>>>>> failed: unexpected error type *errors.errorString
>>>>>> args: []string{"apt-get", "--option=Dpkg::Options::=--force-confold",
>>>>>> "--option=Dpkg::options::=--force-unsafe-io", "--assume-yes", "--quiet",
>>>>>> "install", "--target-release", "precise-updates/cloud-tools",
>>>>>> "mongodb-server"}
>>>>>>
>>>>>> 2014-09-01 04:51:37 ERROR juju.cmd supercommand.go:323 cannot install
>>>>>> mongod: apt-get failed: unexpected error type *errors.errorString
>>>>>> Bootstrap failed, destroying environment
>>>>>>
>>>>>> I'm looking into it at the moment.
>>>>>>
>>>>>
>>>>> So that error message was unhelpful, and I'll fix that, but the
>>>>> underlying issue is that the agent is expecting to install mongodb-server
>>>>> from cloud-archive:tools, and the Makefile does not add that repo. I'm not
>>>>> sure it *should* add it either. Is there something wrong with the one in
>>>>> main? After all, that's where the juju-local package's dependency was
>>>>> resolved.
>>>>>
>>>>> Cheers,
>>>>>> Andrew
>>>>>>
>>>>>>
>>>>>> On Sat, Aug 30, 2014 at 8:19 PM, Matthew Williams <
>>>>>> matthew.williams at canonical.com> wrote:
>>>>>>
>>>>>>> Hi Folks,
>>>>>>>
>>>>>>> I thought I'd try looking into the lxc failing to creates machines
>>>>>>> bug: https://bugs.launchpad.net/juju-core/+bug/1363143
>>>>>>>
>>>>>>> If I wanted to do a local deploy using tip I thought it would be as
>>>>>>> simple as doing make install then juju bootstrap is that correct? It
>>>>>>> doesn't seem to work for me, are there any steps I'm missing
>>>>>>>
>>>>>>> Just to be annoying - I've just shutdown my precise vm so I can't
>>>>>>> paste the errors I get here. I'll follow up with pastes next week
>>>>>>>
>>>>>>> Matty
>>>>>>>
>>>>>>> --
>>>>>>> Juju-dev mailing list
>>>>>>> Juju-dev at lists.ubuntu.com
>>>>>>> Modify settings or unsubscribe at:
>>>>>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Juju-dev mailing list
>>>>> Juju-dev at lists.ubuntu.com
>>>>> Modify settings or unsubscribe at:
>>>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140901/92de0dfc/attachment-0001.html>