On Sun, Mar 19, 2017 at 10:33 AM, Eyal Edri wrote:
>
>
> On Sun, Mar 19, 2017 at 10:30 AM, Oved Ourfali
> wrote:
>
>> As Piotr mentioned, the job is using 1.3.8 however 1.3.9 was released.
>>
>
> Thanks,
> We will look into the logs and find out what caused it to use 1.3.8 and
> report here
On Sun, Mar 19, 2017 at 10:30 AM, Oved Ourfali wrote:
> As Piotr mentioned, the job is using 1.3.8 however 1.3.9 was released.
>
Thanks,
We will look into the logs and find out what caused it to use 1.3.8 and
report here on the results, can't be sure yet if its a bug in the job or
anything e
As Piotr mentioned, the job is using 1.3.8 however 1.3.9 was released.
On Sun, Mar 19, 2017 at 10:27 AM, Barak Korren wrote:
>
>
> בתאריך 17 במרץ 2017 02:32 PM, "Piotr Kliczewski" <
> piotr.kliczew...@gmail.com> כתב:
>
>
> The change was merged 2 weeks ago. How can we make sure not to waste
בתאריך 17 במרץ 2017 02:32 PM, "Piotr Kliczewski" <
piotr.kliczew...@gmail.com> כתב:
The change was merged 2 weeks ago. How can we make sure not to waste
people time next time to analyze the issue?
"Merged" is hardly "released".
As long as a fix does not make it to a release, users can still c
On Fri, Mar 17, 2017 at 8:24 AM, Barak Korren wrote:
> On 16 March 2017 at 18:33, Piotr Kliczewski
> wrote:
>> + infra
>>
>> On Thu, Mar 16, 2017 at 5:32 PM, Piotr Kliczewski
>> wrote:
>>> I checked the logs and I checked that the job somehow used older
>>> version without the fix:
>>>
>>> 2017
On 16 March 2017 at 18:33, Piotr Kliczewski wrote:
> + infra
>
> On Thu, Mar 16, 2017 at 5:32 PM, Piotr Kliczewski
> wrote:
>> I checked the logs and I checked that the job somehow used older
>> version without the fix:
>>
>> 2017-03-16 14:16:07,212::INFO::repoman.common.stores.RPM::Adding
>> pac
Just had this failure again[1], relevant log[2].
I still feel there's an issue here:
{"jsonrpc": "2.0", "id": "aa241c36-d61d-4f9f-9baf-040b00638d00", "result":
[{"username": "Unknown", "displayInfo": [{"tlsPort": "-1", "ipAddress":
"192.168.201.4", "type": "vnc", "port": "5900"}, {"tlsPort": "5901
This bug [1] is already fixed but not yet backported to 4.1.
I want to make sure that there is no regressions on master.
Hopefully I will push it on Monday.
Thanks,
Piotr
[1] https://bugzilla.redhat.com/1425725
On Fri, Mar 3, 2017 at 8:53 AM, Pavel Zhukov wrote:
>
> Hi,
>
> This is one-time
