delayed VBR Console refresh

[chris.childerhose]

Not a problem hopefully it helps.

[mcz]

ok, so short update from my side: We tried to collect another logbundle and restarted some services / killed some processes. Looks like the issue was resolved since then, I have never seen it happen again. Can anybody else here try to do the same / request the fix to make sure that it's not a coincidence on my side? Thanks!

[jround]

I'm used to the F5 refresh but have started to notice since our V12 upgrade if I kick a job off from Jobs > Backup then press F5 to refresh the screen it goes completely blank as if it is trying to refresh but gets stuck until I exit the console and go back in

[HannesK]

Can anybody else here try to do the same / request the fix to make sure that it's not a coincidence on my side?

I did not see the issue again. But to be fair, I was on vacation for week and sometimes the issue takes some time to appear.

it goes completely blank as if it is trying to refresh but gets stuck until I exit the console and go back in

I have never seen that and recommend to check with support.

[NickKulkarni]

@jround
You have hit on one of the reasons I delay rolling out the next version of anything until the version after that is in testing.

Used to have a lecturer at the Open University who was fairly senior IT at a Telecoms provider. She always said: if you want to be a test pilot for Bill Gates you can crash and burn like the rest of them. We don't version update until we have to and usually stay with the earliest version still supported. That way we know where the bugs are and hopefully most have been patched.

Sadly the F5 refresh being needed was a bug in V10 if I recall correctly. It was promised as a fix for V11 and it wasn't and now it looks as if V12 may have broken it further.

[mcz]

OK, I don't know what the current status of this issue is, but the original fix included a modified procedure for the sql server database. Meanwhile, I've switched to postgres and I do see the same issue again. It looks to me that it's working in general, but after having the console open for some days, you see old jobs that are finished a while ago.

Could it be some kind of cache issue? I don't think it's on the database side allthough I'm just guessing

[HannesK]

Hello,
I don't see the issue on Postgres. After a few seconds, the console is up-to-date (in most cases it is up-to-date immediately, but sometimes I need to wait a few seconds).

To investigate, I can only suggest to open a support case and post the case number so that we can look at it.

Best regards
Hannes

[chris.childerhose]

That is interesting Postgres does not show the same behaviour. We are moving to Postgres across the board for VBR/VEM/VCC, so we will see if this issue resolves itself. Thanks for the update, Hannes.

[Gostev]

Pretty sure it's not a question of Postgres vs. Microsoft SQL, but is rather due to Hannes using 12.1 which was specifically polished in this department.

[mcz]

Correct, since 12.1 I haven't seen the bug anymore. Good job guys!

[chris.childerhose]

I am not seeing it either now that I have some 12.1 servers deployed, so it is irrelevant to the DB type. It's nice to see this one fixed.

[bct44]

I can say since v12.1 even it was partially resolve in v12, my team and me will no longer face this issue. Thanks for the improvements, it makes live easier for sysadmin.

[JRRW]

My F5 muscle memory will be so confused when i don't have to reach up with my small carny hands and slam the button whenever i click into that screen, oh no!