On Wed, 2017-05-31 at 10:54 +0200, Jakub Hrozek wrote:
On Wed, May 31, 2017 at 10:09:26AM +0200, Lukas Slebodnik wrote:
> On (31/05/17 08:19), Lachlan Musicman wrote:
> > Hi all,
> > I noticed a while ago that 1.15.3 was versioned in the repo but I've not
> > seen anything released? I'm mostly looking on the COPR
> > (
> > )
> Version is immediately increased in git to simplify life for developers.
> 1.15.3 is still a devel version and not official.
> BTW 1.15.2 is in copr for some time
> > This is purely selfish - I love all that you do, and I'm aware that there
> > has been some fairly comprehensive infrastructural change.
> > I'm just waiting on that one fix and have no roadmap visibility :)
> Which fix do you mean?
I suspect it's #3382 -- this bug hit quite a few people, do you think
it's a good idea to regenerate the copr with 1.15.2 and this fix?
on the other hand, 1.15.3 is not far away (promise :-))
Could you deal with(Quoting earlier mail below) before 1.15.3 too? Fix could be as simple
as reverting just KRB5KRB_AP_ERR_TKT_EXPIRED, works fine here.
> We map expired ticket(KRB5KRB_AP_ERR_TKT_EXPIRED) to network error
> (ERR_NETWORK_IO) since 1.14.2
> It might be a reasonable with first kinit. Because new ticket should be valid.
> But we should treat it differently for renewing ticket.
Ahh, nice. I wonder though if there could be a short wait for the network to come on?
Usually the unlock window is presented shortly before network is on so when fast unlock
sssd will be offline and no new ticket which causes some grief for users.
> Thank you very much for bug report.
> And sorry that it took me so long to find a bug.
NP, glad you found something. Please send patch my way, I will test it directly.
ATM I do not have a higher priority tasks. And I am not sure when someone
from developers will have a time to fix it.
The fastest workaround should be to revert the patch