Linux Container Migration: Let's Consolidate the Chaos

Kinetic ERP
44

Heads Up:

Announcement: Scheduled Hotfix for Kinetic Public Cloud Pilot and Additional Environments – February 24

Following the migration of customer Pilot and Additional environments to Linux on January 29 and February 5, Epicor has identified several impactful issues and developed corresponding fixes. These updates address items related to SQL Server Reporting Services (SSRS) and Linux file paths, along with additional corrections.

For a detailed list of resolved problem reports (PRBs), please review the Hotfix Release Notes available in:

  • [Kinetic Release Notes]
  • [EpicWeb Kinetic Downloads]

Epicor will apply this hotfix to all Kinetic Public Cloud Pilot and Additional environments on Tuesday, February 24, at 7:00 p.m. local data center time to Wednesday, February 25, at 7:00 a.m. local data center time.

Exceptions
The hotfix will not be automatically applied to:

  • Customers using the Cloud Management Portal and elected to self-manage updates for production which includes all environments.
  • Pilot or Additional environments that have already been updated to 2025.2.11 or 2025.2.12.

If your organization falls into one of these groups and requires assistance, please submit a request through EpicCare.

To receive updates related to this maintenance activity, subscribe at status.epicor.com.

If you have questions, contact EpicCare for assistance.

Additional Information
For background materials, technical notes, and preparation guidance, please refer to the Linux Containers FAQ on EpicWeb.

Thank you for your continued partnership as we invest in delivering a more secure and resilient cloud platform.

4 Likes
45

I got the email on this hotfix but I didn’t get any maintenance started/stopped emails. Did anyone else get the maintenance start/stop emails? Did they do the maintenance? I’m not seeing it in the status page but as my wife will attest to, I occasionally can’t see things right in front of my face.

Edit: It was completed and right in front of my face!

image
image662×362 26.3 KB

2 Likes
46

I didn’t get any emails so not sure if my environment was updated but I am still getting errors related to the file share issue.

2 Likes
47

I got the Scheduled Maintenance Completed email at exactly 7am CST this morning.

My Bartender reports are still broken but I believe this error is new:

image
image1693×539 38.3 KB

hard to say the hotfix meets expectations if we don’t know what to expect.

  1. or whether this was supposed to be fixed in Feb 24 hotfix
2 Likes
48

This is from my ticket with support on this issue. I do wish they made some kind of announcement to all Epicor users for this instead of saying it only on tickets.

I just wanted to let you know that going forward, environments hosted on Linux will be able to write to the Azure File Share drive only using the path: /epi/fs…

The UNC path will no longer work.

1 Like
49

Not suprised but that conflicts with their earlier statements saying the path change work around was temporary.

I’m still confused why we are blindsided by the bartender path not working. AFAIK, changing these paths was never mentioned as a customer responsibility for linux compat.

2 Likes
50

The only place I have seen this update is on the ticket I had created or on the epiusers forums.

2 Likes
51

no no no no no cmon

The solution is

wait for live to break

change every path in the system

1 Like
52

NOT AVAILABLE

1 Like
53

Check the CMP we’re up to Hotfix I now while we were on G before.

image
image343×277 5.81 KB

54

Agreed and EpicWeb list description is all we have as if you click on details you get an error (UPDATE: These appear to work now). Plus how is a customer to know which hot fix is which since they use a variety of version numbers and letters compared to the CMP

image
image1635×1120 71.5 KB

1 Like
55

That’s the impression I was under as well…while we were still trying to make our Linux Pilot setup function, the workaround we tried was (as an example) was /epi/fs/Pilot/EDI/in and that went OK.

However, at that point we were also seeing a lot of variations in our error logs.
/usr/local/app/\XXXXXX.file.core.windows.net\XXXXXX\Pilot\EDI\IN\852/852.log
/epi/fs/XXXXXX/Pilot/EDI/IN/tmp/compatibility
/epi/storage/epicordata/XXXXXX/Companies/ZZZZZ01/EDIReports/\XXXXXX.file.core.windows.net\XXXXXX\Pilot\EDI\Outbound

Also had a problem with Positive Pay
/usr/local/app/companies/ZZZZZ01/EI/PositivePay_XYZ/PositivePay_XYZ.cs

We got Pilot restored to Windows and we’re able to test again. We ended up postponing to 3/20 with the rest of the Flex2 group.

1 Like
56

image
image312×139 2.58 KB

Thanks @Randy we are on i as well (lol seems like a lot of hotfixes)

Did this resolve your file share issues or were you not having them, hard to keep track.

1 Like
57

Now in the FAQ indicating it is not temporary Known issues

3 Likes
58

Our issue was resolved via code tweaks I showed here Linux Containers for Cloud - #94 by Randy

Where? No hotfix notes are available via Kinetic Release Notes. Which can’t be directly linked you have to use in-app Help. Nor do hotfixes on EpicWeb contain release notes within them.

image
image627×720 56.4 KB

1 Like
59

Yeah I am having a hard time finding the release notes for this hotfix.

1 Like
60

Did anyone notice if the MES link is working again after the Hotfix? I tested the old MES link format and it appears to work, but I am a newbie and maybe I’m missing something.

61

Yes, there’s been so many hotfixes since the linux deployment I lost track of which one was specific to fixing the MES link, but it was one of those that got rolled up into this one… lol

1 Like
62

Yeah, Hotfix G fixed it we got it when we get to HF H and I also includes it.

Edit: Fixed the hotfixes

1 Like
63

We’re calling it the hotfix to go in and fix the hotfix that went in to fix the hotfix.

3 Likes