FEDORA-2021-83d1d8ec8a created by nathans 3 months ago for Fedora 34
obsolete

Update to latest PCP sources.

This update has been submitted for testing by nathans.

3 months ago

This update's test gating status has been changed to 'ignored'.

3 months ago

This update's test gating status has been changed to 'waiting'.

3 months ago

This update's test gating status has been changed to 'ignored'.

3 months ago

This update has been pushed to testing.

3 months ago

This update's test gating status has been changed to 'failed'.

3 months ago
User Icon martinpitt commented & provided feedback 3 months ago
karma

Completely breaks pmlogger.service:

# systemctl start pmlogger
Job for pmlogger.service failed because the service did not take the steps required by its unit configuration.

# systemctl status pmlogger
× pmlogger.service - Performance Metrics Archive Logger
     Loaded: loaded (/usr/lib/systemd/system/pmlogger.service; disabled; vendor preset: enabled)
     Active: failed (Result: protocol) since Mon 2021-10-11 04:25:21 UTC; 4s ago
       Docs: man:pmlogger(1)
    Process: 3953 ExecStart=/usr/libexec/pcp/lib/pmlogger start-systemd (code=exited, status=0/SUCCESS)
   Main PID: 3953 (code=exited, status=0/SUCCESS)
        CPU: 110ms

Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: Starting Performance Metrics Archive Logger...
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]: /usr/libexec/pcp/lib/pmlogger: Warning: Performance Co-Pilot archive logger(s) not permanently enabled.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]:     To enable pmlogger, run the following as root:
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]:     # /usr/bin/systemctl enable pmlogger.service
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: pmlogger.service: Failed with result 'protocol'.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: Failed to start Performance Metrics Archive Logger.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 1.

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

3 months ago

Thanks @martinpitt, this was a rather obscure regression caused by the run-level check used by pmlogger_check, which starts pmlogger. Now fixed in current main branch with commit b9ff7d65b5e11cae35 and will be in pcp-5.3.5 which is due to release Nov 3rd.

Thanks @mgoodwin! As three weeks is still quite far out, do you plan to remove this erratum, so that CIs stop tripping over this?

This update has been obsoleted by pcp-5.3.4-2.fc34.

3 months ago

Please login to add feedback.

Metadata
Type
bugfix
Severity
low
Karma
-1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
3 months ago
in testing
3 months ago

Automated Test Results