You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using the most recent Foreman/Katello versions, it is not possible to check the status of package upgrade tasks using katprep_maintenance.
To Reproduce
Steps to reproduce the behavior:
Execute package upgrade on a particular host: katprep_maintenance *.json execute -p
Check status: katprep_maintenance *.json status
Package upgrade task cannot be found
I assume that the package upgrade task name changed from Actions::Katello::Host::Update to something different.
Expected behavior
Package upgrade task status is shown.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS version: CentOS 7.5
Red Hat Satellite or Foreman/Katello version: 1.19.0/3.8.0
Additional context
Command output:
$ katprep_maintenance --insecure -C katprep.auth -s pinkepank.test.loc errata-snapshot-report-*.json -I centos07 status
Authentication container password:
INFO:katprep_maintenance:No package task for 'st-centos07.stankowic.loc' found!
INFO:katprep_maintenance:Erratum task for host 'st-centos07.stankowic.loc' succeeded
The text was updated successfully, but these errors were encountered:
Describe the bug
Using the most recent Foreman/Katello versions, it is not possible to check the status of package upgrade tasks using
katprep_maintenance
.To Reproduce
Steps to reproduce the behavior:
katprep_maintenance *.json execute -p
katprep_maintenance *.json status
I assume that the package upgrade task name changed from
Actions::Katello::Host::Update
to something different.Expected behavior
Package upgrade task status is shown.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Command output:
The text was updated successfully, but these errors were encountered: