SOLVED

Redirection bugfix deployment

Brass Contributor

It is now October 2nd. Can we get a confirmation that the bugfix has been deployed to our tenant? The release logs have not been updated yet.

 

https://learn.microsoft.com/en-us/stream/streamnew/migration-tool-release-logs#under-investigation-t... 

24 Replies

Interested in this also. Due to issues seen previously with MS roll outs, we need to complete some testing before we do any new migrations. We already have circa 400 containers that wont have any redirects!! 

@BenWilliamsUK received the following reply from MS support:

"According to engineering this has been fixed and the team entered the monitoring phase. Documentation should be updated soon."

 

I've retriggered my migrations to see if the fix works. I think it will still take 1-2 days before you know if it's successful or not.

Cheers for the reply! I'll try get some test migrations in later today/tomorrow
Our redirects stopped working recently, and if they are not migrated classic video links don't work either. Is this being fixed? If not I have to go in and redirect every single course
UPDATE! They are working in browsers except Firefox unless you do a private window, so the re migration may have worked for the one course. I am waiting to hear on the other.
best response confirmed by IgnacioDavila (Microsoft)
Microsoft Verified Best Answer
Solution
Hello everyone,

The fix is currently being rolled out to all geographical regions, with the process already completed for most of them. It is expected to be fully completed by tomorrow. We are actively monitoring the regions where the fix has already been deployed. We plan to put an official update by 5th Oct, 2023 in the documentation.

Regards
Nandit Jain

I don't know about your tenant, but I'm able to confirm that the re-migrations and new migrations that I made yesterday (October 2, 2023) are redirecting already (October 3, 2023).

After remigrating the redirects have started working here as well since yesterday.
Have you remigrated all your containers or just the ones prior to the 15th August?
All of them were migrated the first time before 15 august, so its the same set for us.
Thanks! That's helpful!
This is still an issue. Did a M365 group container migration on 03 Oct and waited more than 48 hours. Still the redirection not happening . Also, the video is still present in classic stream portal.

MS mentioned in the Community support call yesterday that the old migrations (from after Aug 15) are all in a big queue waiting to be processed. New migrations also come first before the old ones, so due to people still migrating your old migration will not be updated. They wanted everyone to wait with remigration, but perhaps if you migrate again the fix will be applied faster.

@JWiersem1925 sorry, did MS ask people to hold off on remigrating the containers that were done before Aug 15th 2023? There is so much confusion around Stream migration as a result of MS renegading on commitments made earlier. I am not sure if I should have migrated our containers so early.

No, we have not asked users to hold off. You can do fresh as well as remigrations now.
FYI: I noticed that redirection does NOT work after the first migration even after October. Only after re-migrating the containers a week later, the redirection starts working a day later.
I migrated some test videos on 17th October, and they are still visible in Stream (Classic) and no redirect as of now 24th October. This bug is definitely not fixed as seen a number of people still having the issue.

Until our videos start redirecting, we can't test the move/rename post migration to ensure that doesn't break the redirection. This is really holding us back on starting our overall migration (thousands of videos).

@gjen020 I have the same issue...

1 best response

Accepted Solutions
best response confirmed by IgnacioDavila (Microsoft)
Microsoft Verified Best Answer
Solution
Hello everyone,

The fix is currently being rolled out to all geographical regions, with the process already completed for most of them. It is expected to be fully completed by tomorrow. We are actively monitoring the regions where the fix has already been deployed. We plan to put an official update by 5th Oct, 2023 in the documentation.

Regards
Nandit Jain

View solution in original post