Bug 2057184 - cgroupify: Error moving pid into new cgroup (11)
Summary: cgroupify: Error moving pid into new cgroup (11)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: uresourced
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Benjamin Berg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedFreezeException
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-22 21:49 UTC by Chris Murphy
Modified: 2022-03-26 15:04 UTC (History)
3 users (show)

Fixed In Version: uresourced-0.5.1-1.fc36
Clone Of:
Environment:
Last Closed: 2022-03-26 15:04:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab benzea uresourced issues 4 0 None closed cgroupify: Error moving pid into new cgroup (11) 2022-02-22 21:50:02 UTC

Description Chris Murphy 2022-02-22 21:49:50 UTC
I see the following in the journal:

[  715.273982] cgroupify[3753]: Error getting unit object path for app-glib-firefox-3750.scope: Unit app-glib-firefox-3750.scope not loaded.
[  715.285917] cgroupify[3754]: Error moving pid 3750 into new cgroup (11)

kernel-5.17.0-0.rc4.96.fc36.x86_64+debug
systemd-250.3-4.fc36.x86_64
uresourced-0.4.1-1.fc36.x86_64


Upstream bug report has the details.

Comment 1 Fedora Blocker Bugs Application 2022-02-22 21:54:24 UTC
Proposed as a Freeze Exception for 36-beta by Fedora user chrismurphy using the blocker tracking app because:

 This should be fixed in uresourced-0.5.0-1.fc36 and is considered a desired and safe fix. it just missed freeze. I'll give it a go today and report back.

Comment 2 Benjamin Berg 2022-02-23 09:14:24 UTC
Not quite, 0.5.0 is already in Fedora. I just missed the fix when rolling that release, and then it was too late to make it before the freeze. So, it'll be included in a new 0.5.1 upstream release.

Comment 3 Fedora Update System 2022-02-28 18:24:22 UTC
FEDORA-2022-f49cfedb78 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f49cfedb78

Comment 4 Geoffrey Marr 2022-02-28 21:08:33 UTC
Discussed during the 2022-02-28 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as we're not entirely sure how serious of a problem this is, and hence whether it's worth a freeze exception. We'll ask the maintainer for his opinion in the bug report and discuss this again next week or in the ticket.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-28/f36-blocker-review.2022-02-28-17.00.txt

Comment 5 Fedora Update System 2022-03-01 16:31:40 UTC
FEDORA-2022-f49cfedb78 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-f49cfedb78`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f49cfedb78

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Geoffrey Marr 2022-03-07 22:33:27 UTC
Discussed during the 2022-03-07 blocker review meeting: [0]

The decision to classify this bug as a "RejectedFreezeException (Beta)" was made as per feedback from the maintainer, this is not a major bug and it's fine to fix it with an update.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-07/f36-blocker-review.2022-03-07-17.01.txt

Comment 7 Fedora Update System 2022-03-26 15:04:54 UTC
FEDORA-2022-f49cfedb78 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.