Support for Ubuntu 22.04 LTS #1458
Comments
|
Ubuntu 22.04 LTS has the same behavior as described in #1451 |
|
I just started playing with 22.04 LTS. My installer complains with the following: $ sudo sh onboard_agent.sh -w workspace -s key Extracting OMS agent install bundle... $ sudo /opt/microsoft/omsagent/bin/troubleshooter OMS agent shell bundle exiting with status code 55 I'll have to spin up a new VM with 20.x but this is what I'm running into. I tried to manually install the oms.deb file and it gave a similar error. There is no OpenSSL 1.x package for Ubuntu 22.x that I can find. |
|
The issue as i see it here appears to be in the OMI sub-component - theres a related issue open for it and this potentially impacts the ingest of logs into Microsoft Sentinel as a result |
|
facing this issue as well, subscribing. |
|
Ubuntu 22.04.1 release, which marks the "de facto" stable release of Jammy, is scheduled for August 11th. ([https://wiki.ubuntu.com/Releases]). From this date on, do-release-upgrade utility will upgrade any existing 20.04 systems to 22.04, which in turn will break every OMS Agent functionality on Ubuntu, because the installer doesn't know 22.04, and because it requires OpenSSL 1.1. There is a reason the default OpenSSL release on 22.04 is 3.x; there are known vulnerabilities on 1.1 for ages now, even Microsoft Defender for Cloud warns about it. |
|
Meanwhile I've noticed that the OMS agent is in a deprecation path and will be retired on august 2024. The current recommendation from MS is to migrate to the Azure Monitor Agent, which I'm starting to explore. This may mean that support for newer Linux distribution versions in the OMS / Log Analytics Agent may stop altogether. |
Just tripped on it myself, after posting the comment. For those in need, here is the documentation link to install the AMA Extension. |
|
It is now September 8th 2022. Any updates on this? There is already a point release, Ubuntu 22.04.1, which is when most seriously consider using the newer version (myself included), but we really want this functionality before we start rolling out new or upgrading existing servers. |
|
@watsonb from the previous comment I concluded that since it's on a deprecation path, most likely there won't be an update |
|
There better be an update, considering that the AMA agent is currently
incapable of collecting log files correctly (in Linux at least).
…On Thu, 8 Sep 2022 at 21:57, Andrew Savinykh ***@***.***> wrote:
@watsonb <https://github.com/watsonb> from the previous comment I
concluded that since it's on a deprecation path, most likely there won't be
an update
—
Reply to this email directly, view it on GitHub
<#1458 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASPGAB6YLNY4URJLCLPVA3V5JHMLANCNFSM5WBETE6A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Is there an open issue or known issue note somewhere that confirms this? |
|
I don’t know about that. My remark is purely based on me trialing the AMA
agent on different flavors of Linux VM’s in Azure, and finding a big
blocker: the Computer column is not created in a custom log table, so
there’s no column identifying which VM the log came from. Not even
_ResourceId. Support replicated and confirmed this.
Mind that the log file collection feature is still in preview. That said, I
was also told that the computer name will eventually be “appended” to the
RawData value, and when that happens you will need to use a KQL transform
to extract it. That was disappointing :\
…On Thu, 8 Sep 2022 at 22:40, Sandor Zeestraten ***@***.***> wrote:
There better be an update, considering that the AMA agent is currently
incapable of collecting log files correctly (in Linux at least).
Is there an open issue or known issue note somewhere that confirms this?
—
Reply to this email directly, view it on GitHub
<#1458 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASPGABPSGIESFSJEY4PQFLV5JMOLANCNFSM5WBETE6A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
AMA still can't be used everywhere. When using "Auto provisioning for Microsoft Defender for Cloud", the Log Analytics Agent is the only way forward for Enterprises. |
|
Also ran into the issue of OMS not installing on Ubuntu 22.04 LTS. When contacting Microsoft about it, they stated there were no plans to port the OMS agent to Ubuntu 22.04 LTS and pointed us to AMA. When asked about the GA of several services that are currently only in public preview for AMA, no ETA could be given. Disappointing. |
|
Very disappointing indeed. Pushing customers to a solution without feature
parity and still with functionality blockers is not the way to support
clients.
…On Thu, 29 Sep 2022 at 11:35, René Dvt ***@***.***> wrote:
Also ran into the issue of OMS not installing on Ubuntu 22.04 LTS. When
contacting Microsoft about it, they stated there were no plans to port the
OMS agent to Ubuntu 22.04 LTS and pointed us to AMA.
When asked about the GA of several services that are currently only in
public preview for AMA, no ETA could be given. Disappointing.
—
Reply to this email directly, view it on GitHub
<#1458 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASPGABIGIX74CR2EAY5H7DWAVWH7ANCNFSM5WBETE6A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
They were aiming for feature parity by March 2022. Obviously missed that. |
|
Now, leave a record: System Log |
|
Any updates here? any timeline? |
AMA supports Ubuntu 22.04 (since around October 2022) so that may remove one of the blockers to moving away from OMS. |
|
It's my understanding that AMA support for on-premises Linux servers is limited to those with Azure Arc, it would be easier to just migrate over to Telegraf with it's |
|
so according to microsoft/omi#715 - there is now an OpenSSL 3 supported version of OMI and an updated DEB in the MS repo - https://packages.microsoft.com/ubuntu/22.04/prod/pool/main/o/omi/ quick download and dpkg and it appears this issue now moves on.... looks like there is an updated deb for that also https://packages.microsoft.com/ubuntu/22.04/prod/pool/main/s/scx/ with that also updated the error is now: |
|
I see from your output that it is still trying to install omi 1.6.8. 1.7.0 is the version that now supports openssl 3.0. See https://github.com/Microsoft/omi/releases. I was able to install omi 1.7.0 on a RHEL 9 box fine with the MS package at https://packages.microsoft.com/rhel/9/prod/Packages/o/omi-1.7.0-0.ssl_300.ulinux.x64.rpm. In looking at the deb URL above - https://packages.microsoft.com/ubuntu/22.04/prod/pool/main/o/omi/ - it appears that omi 1.7.0 is also there. The next question is, when will omi 1.7.0 be packaged with OMS-Agent-for-Linux? |
|
yes the installer was still attempting to install the older version but skipping due to presence of newer version manually installed. basically all the dependant programs are updated and no longer a blocker, the new error is about the omsagent itself not supporting OpenSSL3 |
|
The supposed transition for AMA doesn't make sense with all the holes it is leaving in the existing OMS agent functionality. We use Update Automation; Update Management Center is the V2 release but it's still in "Preview" so not using it on our prod systems. With OMI not supporting 22.04 the suggestion is to install AMA but AMA only supports Update Management V2 which is a PREVIEW project. |
just adding a bump to confirm that OMS-Agent still doesn't work or install correctly on Ubuntu 22 even when manually installing the 1.7 packages of omi and scx since the script does not actually install the latest versions. it's amazing that this issue has been open this long and that they've managed to update the dependencies to support SSL3 in response to fixing this issue while not actually solving the problem itself. at this point i'm wondering if this is intentional in order to "encourage" folks to migrate to the new solution. the test should be can i run onboard_agent.sh and enroll a device to a log analytics workspace on ubuntu 22. if that errors out for any reason, dependency or inside OMS agent itself the issue itself is clearly not fixed. can we get any kind of feedback if Microsoft is aware of the issue and what the plan is to try to potentially resolve it? |
|
same on Debian12 ──╼ #bash omsagent-1.16.0-0.universal.x64.sh --install -w xxxxx -s "xxxxxxx" $ sudo /opt/microsoft/omsagent/bin/troubleshooter OMS agent shell bundle exiting with status code 55 |
|
Hello, we have same issue on 22.04. Any updates/plans? ----- Upgrading package omsagent to version (omsagent-1.16.0-0.universal.x64) ----- |
|
+1 |
|
Curious why AMA can't be used instead of OMS. Assume everyone has seen this, there is now less than 12 months before OMS is officially retired. |
|
@PCNZ Aparently Microsoft is still working on AMA Autoprovisioning. There was something in Preview for AMA Autoprovisioning with a Policy, but that has been (or will next month) be deprectated. Aparently some new AMA Autoprovisioning (for SQL only?) will be availabile in December 2023. Today, AMA is not on-par with OMS/MMA. |
|
We're talking for over an year here about the most used linux distribution, accounting for over 1/3 of market linux share, with several customers using it in production environments. It's been almost 18 MONTHS since it's latest LTS version is released, and nonetheless, we can't use OMS (and shouldn't, because OpenSSL 1 is notoriously unsafe and will trigger warnings on Azure Defender for Cloud to add insult to injury) and even though we can use AMA, no Guest Level Diagnostics because, you know, it doesn't support 22.04. How are we supposed to recommend Azure Defender and/or Sentinel to our customers with this glaring gap on the very data they rely upon to actually do what they're supposed to? It's not SysOps nitpicking or bleeding edge adoption stubborness we're talking here. It's a serious, major flaw on both product strategy and value to customers. Can we please get ANY kind of official position regarding this? We really don't want to admit to customers they're better of with Datadog or New Relic if they plan on keep using Ubuntu. |
|
Thats my issue with it as well. |
|
So my big remaining use case here as i have been on the OMS to AMA migration journey is actually ironically - Azure Stack Hub We cannot install the Arc Agent there (because it looks like azure, breaths like azure, and rejects the install like azure) or get a standalone version of AMA that can point to azure public cloud - so i am stuck with OMS until a suitable replacement that can support this scenario is available I'm now going to start escalating this from my MSFT account management team because after 18 months of a stable LTS Ubuntu release and still 1 year more of supposed support this is kind of ridiculous now |
|
Anthony, I am the Product Manager for the AMA agent from Microsoft. I agree the implementation on Azure Stack Hub has been bumpy. I am working with that team over the next few months to resolve this issue. |
|
Bumping this for a timeline. This is the latest version of Ubuntu and as of Oct 24 there is still no resolution as I can tell. |
@gzerphey I still see PRs into main for the "VM Extension Repo" (shows Ubuntu 22 as of 2 weeks ago) or the "OMS Agent Build Repo" (Even yesterday. Aparently the OMS-Build-Repo is needed for testing/publishing). So I have high hopes that someone is actually working on a release. |
AMA provisioning via a DCR associated with an Azure Policy is a valid method - these policies should do the job for that. The policies don't seem to be in preview anymore? The main issue I'm seeing is with Microsoft Sentinel integrations which only work with OMS. |
Nevermind, I am confusing oms agent with ama agent |
|
I think we have Ubuntu 22 (and more) as a Release now: And there is even a patch: Maybe the extensions in Azure still need to be updated so it's not automatically installed/updated yet. |
|
manual install/upgrade now works for me |
|
Thank you for your submission. As previously announced, the Log Analytics agent has been deprecated and has no support as of August 31, 2024. If you use the Log Analytics agent to ingest data to Azure Monitor, migrate now to the new Azure Monitor agent. As part of repo archival, open issues and pull requests will be closed. |
While at it maybe you could a lend us a hand over here so it becomes close to reality faster? |
and others
Hello Team,
Currently there is no support for Ubuntu 22.04 LTS.
I want to raise this issue so we can track the status better.
Please be advised that Canonical already has a Azure Marketplace Image for Ubuntu 22.04 LTS available, and when logging in through SSH they actively promote release upgrades from earlier versions through the MOTD.
Thanks for all the hard work, keep it up!
The text was updated successfully, but these errors were encountered: