On 06/08/2017 10:16 AM, Emilien Macchi wrote:
On Thu, Jun 8, 2017 at 1:47 PM, Sofer Athlan-Guyot wrote:
Hi,
Alex Schultz writes:
On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot wrote:
Hi,
Emilien Macchi writes:
On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot wrote:
Hi,
I d
On Thu, Jun 8, 2017 at 1:47 PM, Sofer Athlan-Guyot wrote:
> Hi,
>
> Alex Schultz writes:
>
>> On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot
>> wrote:
>>> Hi,
>>>
>>> Emilien Macchi writes:
>>>
On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot
wrote:
> Hi,
>
> I d
Hi,
Alex Schultz writes:
> On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot
> wrote:
>> Hi,
>>
>> Emilien Macchi writes:
>>
>>> On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot
>>> wrote:
Hi,
I don't think we have such a job in place. Basically that would check
tha
On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot wrote:
> Hi,
>
> Emilien Macchi writes:
>
>> On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot
>> wrote:
>>> Hi,
>>>
>>> I don't think we have such a job in place. Basically that would check
>>> that re-running the "openstack deploy ..." com
On Wed, Jun 7, 2017 at 1:20 PM, Sofer Athlan-Guyot wrote:
> Hi,
>
> Emilien Macchi writes:
>
>> On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot
>> wrote:
>>> Hi,
>>>
>>> I don't think we have such a job in place. Basically that would check
>>> that re-running the "openstack deploy ..." com
Hi,
Emilien Macchi writes:
> On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot
> wrote:
>> Hi,
>>
>> I don't think we have such a job in place. Basically that would check
>> that re-running the "openstack deploy ..." command won't do anything.
>>
>> We had such an error by the past[1], but
On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot wrote:
> Hi,
>
> I don't think we have such a job in place. Basically that would check
> that re-running the "openstack deploy ..." command won't do anything.
>
> We had such an error by the past[1], but I'm not sure this has been
> captured by
