Spec mismatch - new java ver in the repo

[Cory Johns]

(Adding bigdata mailing list.)

So, we are doing full Java version spec matching because we had a case
where a package release update to Java (1.7.0_73 to 1.7.0_80 or something)
caused some brokenness in the charms (due to causing `jps` to work
differently, due to permissions settings).  However, during install we're
still only pinning Java by the major version.

I think it's probably generally safe to spec match only on the Java version
(1.7.0, in this case) and ignore the release version, but I'd like some
community input on this.  Are we likely to see enough differences between
Java package releases that could cause the two sides to work but negatively
influence the results?

If we're ok with ignoring the package release version, then I say we modify
the spec matching logic to remove that part.

On Wed, Oct 28, 2015 at 4:33 AM, Andrew Mcleod <andrew.mcleod at canonical.com>
wrote:

> deployed a big data bundle this morning, then tried adding more compute
> slaves (within like 2 minutes):
>
> unit-compute-slave-9[3864]: 2015-10-28 08:21:03 INFO
> unit.compute-slave/9.nodemanager-relation-joined logger.go:40 ValueError:
> Spec mismatch with related unit yarn-master/0: u'{"java": "1.7.0_79",
> "vendor": "apache", "hadoop": "2.4.1", "arch": "x86_64"}' != '{"java":
> "1.7.0_85", "vendor": "apache", "hadoop": "2.4.1", "arch": "x86_64"}'
>
> Yay! Spec matching works!
>
> ....turns out they updated the release of java in the repo between my
> deployment and add-units.
>
> should the installer script stick to minor releases?
> 7u79-2.5.6-0ubuntu1.14.04.1 is still in the repo
>
> How are people in the wild expected to deal with this kind of situation?
> Upgrade java on existing instances?
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/bigdata/attachments/20151028/77bbb611/attachment.html>