Series Mismatch between charm and sentry subordinate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Amulet |
Fix Released
|
Low
|
Unassigned |
Bug Description
Running a farely bare-bones amulet deployment:
d.add('
d.add('
d.add('mysql', 'cs:trusty/mysql')
d.configure(
d.relate(
It appears that amulet is deploying Precise sentry subordinates instead of matching the series to trusty.
2014-07-09 14:54:33 Adding relation hive-metastore:
2014-07-09 14:54:33 Adding relation hive-server:
2014-07-09 14:54:34 Adding relation mysql:juju-info <-> mysql-sentry:
Traceback (most recent call last):
File "/usr/bin/
load_
File "/usr/lib/
run()
File "/usr/lib/
importer.
File "/usr/lib/
rels_created = self.add_
File "/usr/lib/
self.
File "/usr/lib/
return self.client.
File "/usr/lib/
'Endpoints': [endpoint_a, endpoint_b]
File "/usr/lib/
raise EnvError(result)
jujuclient.
{ u'Error': u'cannot add relation "mysql-
u'RequestId': 3,
u'Response': { }}
>
Traceback (most recent call last):
File "./00-deploy", line 18, in <module>
d.setup(
File "/usr/lib/
self.juju_env], cwd=self.
File "/usr/lib/
raise CalledProcessEr
subprocess.
Changed in amulet: | |
importance: | Undecided → Low |
status: | New → Triaged |
milestone: | none → 1.5.1 |
Fixed as of v1.8, where sentries are no longer implemented as subordinates.