New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ncm-systemd: alias sys-device-pci doesn't match expected pattern (EL9) #1677
Comments
I just installed another server with a different hardware model and I didn't see the problem initially but it appeared after adding a couple of RPMs related to NFS client. Not sure whether it is related or just that it appeared after the initial configuration/ncm-systemd run... The HW is also a server from Dell, not the same model but the same generation, so an HW-related issue cannot be excluded... |
@jouvin is there a way for you to find out when this unit was discovered/added? maybe journalctl will tell. if you run it a second time, is the error gone? |
@stdweird no, it's the opposite. During first run the problem is not there but after that it appears and never disappears. I reinstalled my test box to better assess when it happens and this time it happened at the very first run of
|
ok, my next guess is that the device uses some utf8 chars in the device name, and the regex doesn't match it because it's not properly dealing with utf8. can you locate the file |
@stdweird unfortunately it doesn't help. But I think you are right: the name contains some hexadecimal characters that may be a unicode one. Doing
According to https://www.compart.com/en/unicode/U+02D1, it may be a "half triangular colon"... |
@jouvin hmm, next try: replace the |
@jouvin or do a |
ok, next guess: ithas nothing to do with utf8 there is a method in Unit.pm called _handle_bug_wrong_escaped_unit. it does somethign similar and i think it needs to be extended with support for
so in that method add last line
|
@stdweird still not working unfortunately: no message about the wrong escaping found in |
@stdweird I have been busy deploying our first EL9 systems and had no time to troubleshhot more this problem and come with a fix... I can only say that I started to deploy servers from a different vendor (HP) where the problem doesn't appear... Seems somewhat HW-related... |
@jouvin i just tried to setup idrac with virtual media attached. i see bunch of devices pop up in dmesg, but nothing going wrong in systemd units. |
@stdweird here it is: |
can you also do
and paste that here. in the |
@stdweird here it is:
|
|
e.g. > systemd-escape 'abc/123'
abc-123
> systemd-escape 'abc:123'
abc:123
> systemd-escape 'abc-123'
abc\x2d123
> systemd-escape 'abc#123'
abc\x23123
> systemd-escape 'abc?123'
abc\x3f123
> systemd-escape 'abc^123'
abc\x5e123 |
Why we don't use |
for reference, we also get a similar error while configuring qemu-guest-agent in systemd:
|
not sure this is the same.
this smells like another escaping bug, you clearly see here that the backslash from i also spotted another bug: the regex of teh list-units parser needs the extra
(that is with partial fix) |
I'm trying to install an EL9 server (Alma 9.3) and when running
ncm-systemd
, I get the following errors:When looking at the details in
component/systemd.log
, I find:Environement used:
ncm-systemd-23.6.0-1.noarch
)The text was updated successfully, but these errors were encountered: