| 2022-12-17 01:40:10 |
Ghada Khalil |
description |
Brief Description:
Provide a brief description of the issue. Usually, it should not be more than 2 to 3 lines.
Example: After performing a restore of the system, user is unable to swact the controller.
Severity:
<Minor: System/Feature is usable with minor issue>
Steps to Reproduce:
Deploy system, run 'system registry-garbage-collect'
Expected Behavior:
puppet finishes successfully
Actual Behavior:
puppet doesn't finish successfully
Reproducibility:
100%
System Configuration:
all
Load info (eg: 2022-03-10_20-00-07):
I assume day 0 Debian, but say 23 Nov 2022
Last Pass:
?? Only CentOS passes I assume
Timestamp/Logs:
2022-11-23T17:27:13.513 Error: 2022-11-23 17:27:11 +0000 /Stage[main]/Platform::Dockerdistribution::Garbagecollect/Exec[run garbage collect]/returns: change from 'notrun' to ['0'] failed: Could not find command '/usr/bin/registry'
Alarms:
N/A
Test Activity:
Developer Testing
Workaround:
N/A |
Brief Description:
system registry-garbage-collect fails on Debian load
Severity:
<Minor: System/Feature is usable with minor issue>
Steps to Reproduce:
Deploy system, run 'system registry-garbage-collect'
Expected Behavior:
puppet finishes successfully
Actual Behavior:
puppet doesn't finish successfully
Reproducibility:
100%
System Configuration:
all
Load info (eg: 2022-03-10_20-00-07):
I assume day 0 Debian, but say 23 Nov 2022
Last Pass:
?? Only CentOS passes I assume
Timestamp/Logs:
2022-11-23T17:27:13.513 Error: 2022-11-23 17:27:11 +0000 /Stage[main]/Platform::Dockerdistribution::Garbagecollect/Exec[run garbage collect]/returns: change from 'notrun' to ['0'] failed: Could not find command '/usr/bin/registry'
Alarms:
N/A
Test Activity:
Developer Testing
Workaround:
N/A |
|
