| 2014-10-28 16:08:51 |
Curtis Hovey |
description |
recent changes to metadata generate-tools breaks the behaviour of 1.15.0..1.20.x. The new behaviour is to claim the agents are in a directory named after the purpose (released, devel, proposed, with the default being released) instead of "releases". Since 1.20.x and older required private clouds and anyone with special streams to create a dir structure of
<tools-metadata-root>/releases/
<tools-metadata-root>/streams/v1
this tree would be uploaded to the stream location.
The new behaviour is to list a location that does not exist on disk. instead of "releases", the com file (product file) says "released".
Anyone getting a new juju overnight will have broken streams |
recent changes to metadata generate-tools breaks the behaviour of 1.15.0..1.20.x. The new behaviour is to claim the agents are in a directory named after the purpose (released, devel, proposed, with the default being released) instead of "releases". Since 1.20.x and older require anyone with private streams to create a dir structure of
<tools-metadata-root>/releases/
<tools-metadata-root>/streams/v1
this tree would be uploaded to the stream location.
The new behaviour is to list a location that does not exist on disk. instead of "releases", the com file (product file) says "released". No agents are uploaded to the
location listed in the product file....boot straps fail.
Anyone getting a new juju overnight will have broken streams. Consider that machines in
an enterprises will update is a rolling fashion.
In summary, "releases/" must be used be default when the purpose is NOT explicitly passed. When we say we are using agents in dir "released" or dir "devel" the paths in the product file should list said dirs.
I do not see any new options to explicitly state which dir to get the agents from. It is not possible to specify the dir that has the agents. |
|
