limitations in account handling

Nikos Mavrogiannopoulos nmav at redhat.com
Wed Jan 7 08:01:05 UTC 2015


On Tue, 2015-01-06 at 11:04 -0700, Stephen John Smoogen wrote:



>         > > Today:
>         > > [nmavrogi at dhcp-2-127 ocserv]$ git push
>         > > Counting objects: 4, done.
>         > > Delta compression using up to 4 threads.
>         > > Compressing objects: 100% (4/4), done.
>         > > Writing objects: 100% (4/4), 515 bytes | 0 bytes/s, done.
>         > > Total 4 (delta 3), reused 0 (delta 0)
>         > ok. I dug into logs and found one strange issue. When you
>         change your
>         > ssh key there should be a message emitted that it was
>         changed, but in
>         > your case the message didn't say anything about the ssh key,
>         it was
>         > empty.
>         > When you changed your ssh key did you do anything else in
>         the account
>         > system interface? Or just logged in, edit account, upload
>         new key?
>         
>         Correct.
>         
>         > There's a bug here, just not sure how to isolate it. ;)
>         
>         I think I did the same few weeks ago and had the same result.
>         I could
>         only commit the next day. Let me know if you want me to
>         re-upload the
>         key (I'm off in a while so I'll not commit until tomorrow).
>         
>         
> 
> 
> What is a timeframe UTC we can work with you on this?

I typically work from 7.00 to 15.00 UTC. If still needed, I could update
the key at around 15.00.






More information about the websites mailing list