Skip to content
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

Checking status of package upgrade tasks not working #107

Open
stdevel opened this issue Oct 3, 2018 · 0 comments
Open

Checking status of package upgrade tasks not working #107

stdevel opened this issue Oct 3, 2018 · 0 comments
Assignees
Labels
bug confirmed Confirmed behaviour
Milestone

Comments

@stdevel
Copy link
Owner

stdevel commented Oct 3, 2018

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:

  1. Execute package upgrade on a particular host: katprep_maintenance *.json execute -p
  2. Check status: katprep_maintenance *.json status
  3. 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
@stdevel stdevel added bug confirmed Confirmed behaviour labels Oct 3, 2018
@stdevel stdevel added this to the 0.5.x milestone Oct 3, 2018
@stdevel stdevel self-assigned this Oct 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed Confirmed behaviour
Projects
None yet
Development

No branches or pull requests

1 participant