This only affects 1.17.2 and 1.17.3 interaction, so we can just close
it.
There was a change introduced in 1.17.2 to add an image-stream config
attribute, which was previously specific to the Azure provider. The
config default (omit) was invalid, though, causing the bug lp:1277636.
We fixed this
** Changed in: juju-core (Ubuntu)
Status: New = Triaged
** Changed in: juju-core (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
How is this a regression in juju-core when the issue seems to be the
slower updating of streams.canonical.com after the release? This is
bound to happen at any time we do a release and update streams.c.c some
time after.
--
You received this bug notification because you are a member of Ubuntu
I don't think this has anything todo with streams.canonical.com; juju-
tools and product-streams are provided in the keystone catalog for the
openstack deployment where I see this issue so streams.canonical.com
should not come into it?
--
You received this bug notification because you are a
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1284127
Title:
juju deploy fails against juju-core 1.17.3 environment with
** Summary changed:
- juju deploy fails with juju-core 1.17.3 (openstack/simplestreams)
+ juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
streams.canonical.com is out of date. I think updating it will reduce
this issue to High. Juju CI is broken with the testing of version 1.17.4
because the tools-metadata-url is not honored for aws deployments.
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
