Re: CPR/liveupdate: test results using prior bug fix

2024-05-17 Thread Michael Galaxy
OK, acknowledged. Thanks, All. - Michael On 5/16/24 13:07, Steven Sistare wrote: On 5/16/2024 1:24 PM, Michael Galaxy wrote: On 5/14/24 08:54, Michael Tokarev wrote: On 5/14/24 16:39, Michael Galaxy wrote: Steve, OK, so it does not look like this bugfix you wrote was included in 8.2.4 (whi

Re: CPR/liveupdate: test results using prior bug fix

2024-05-16 Thread Steven Sistare
On 5/16/2024 1:24 PM, Michael Galaxy wrote: On 5/14/24 08:54, Michael Tokarev wrote: On 5/14/24 16:39, Michael Galaxy wrote: Steve, OK, so it does not look like this bugfix you wrote was included in 8.2.4 (which was released yesterday). Unfortunately, that means that anyone using CPR in that

Re: CPR/liveupdate: test results using prior bug fix

2024-05-16 Thread Michael Galaxy
On 5/14/24 08:54, Michael Tokarev wrote: On 5/14/24 16:39, Michael Galaxy wrote: Steve, OK, so it does not look like this bugfix you wrote was included in 8.2.4 (which was released yesterday). Unfortunately, that means that anyone using CPR in that release will still (eventually) encounter

Re: CPR/liveupdate: test results using prior bug fix

2024-05-15 Thread Steven Sistare
On 5/14/2024 11:33 AM, Michael Tokarev wrote: 14.05.2024 16:54, Michael Tokarev пишет: On 5/14/24 16:39, Michael Galaxy wrote: Steve, OK, so it does not look like this bugfix you wrote was included in 8.2.4 (which was released yesterday). Unfortunately, that means that anyone using CPR in th

Re: CPR/liveupdate: test results using prior bug fix

2024-05-14 Thread Michael Tokarev
14.05.2024 16:54, Michael Tokarev пишет: On 5/14/24 16:39, Michael Galaxy wrote: Steve, OK, so it does not look like this bugfix you wrote was included in 8.2.4 (which was released yesterday). Unfortunately, that means that anyone using CPR in that release will still (eventually) encounter the

Re: CPR/liveupdate: test results using prior bug fix

2024-05-14 Thread Michael Tokarev
On 5/14/24 16:39, Michael Galaxy wrote: Steve, OK, so it does not look like this bugfix you wrote was included in 8.2.4 (which was released yesterday). Unfortunately, that means that anyone using CPR in that release will still (eventually) encounter the bug like I did. 8.2.4 is basically a

Re: CPR/liveupdate: test results using prior bug fix

2024-05-14 Thread Michael Galaxy
Steve, OK, so it does not look like this bugfix you wrote was included in 8.2.4 (which was released yesterday). Unfortunately, that means that anyone using CPR in that release will still (eventually) encounter the bug like I did. I would recommend that y'all consider cherry-picking, perhaps,

Re: CPR/liveupdate: test results using prior bug fix

2024-05-13 Thread Michael Galaxy
Hi Steve, Thanks for the response. It looks like literally *just today* 8.2.4 was released. I'll go check it out. - Michael On 5/13/24 15:10, Steven Sistare wrote: Hi Michael,   No surprise here, I did see some of the same failure messages and they prompted me to submit the fix.  They are a

Re: CPR/liveupdate: test results using prior bug fix

2024-05-13 Thread Steven Sistare
Hi Michael, No surprise here, I did see some of the same failure messages and they prompted me to submit the fix. They are all symptoms of "the possibility of ram and device state being out of sync" as mentioned in the commit. I am not familiar with the process for maintaining old releases for

CPR/liveupdate: test results using prior bug fix

2024-05-13 Thread Michael Galaxy
Hi Steve, We found that this specific change in particular ("migration: stop vm for cpr") fixes a bug that we've identified in testing back-to-back live updates in a lab environment. More specifically, *without* this change (which is not available in 8.2.2, but *is* available in 9.0.0) cause