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

[BUG] RHEL8 - pkg.latest shows failed when actually successful when updating kernel #60931

Closed
owmtia opened this issue Sep 23, 2021 · 1 comment
Assignees
Labels
Feature new functionality including changes to functionality and code refactors, etc.

Comments

@owmtia
Copy link
Contributor

owmtia commented Sep 23, 2021

Description
Using pkg.latest on RHEL8 and compatible systems to update the kernel the state will fail as multiple versions are now installed and the expected target doesn't match.

Steps to Reproduce the behavior
The following is the state which will fail on a successful patch.

common::patch::kernel:
  pkg.latest:
    - name: kernel
    - refresh: True

With the following output:

          ID: common::patch::kernel
    Function: pkg.latest
      Result: False
     Comment: The following packages failed to update: kernel
     Started: 22:29:33.006972
    Duration: 62886.163 ms
     Changes:   
              ----------
              kernel:
                  ----------
                  new:
                      4.18.0-305.19.1.el8_4,4.18.0-305.17.1.el8_4
                  old:
                      4.18.0-305.17.1.el8_4
              kernel-core:
                  ----------
                  new:
                      4.18.0-305.17.1.el8_4,4.18.0-305.19.1.el8_4
                  old:
                      4.18.0-305.17.1.el8_4
              kernel-modules:
                  ----------
                  new:
                      4.18.0-305.17.1.el8_4,4.18.0-305.19.1.el8_4
                  old:
                      4.18.0-305.17.1.el8_4

Expected behavior

Expects the pkg.latest to succeed as it has installed the expected version.

Versions Report

This is running on a masterless minion.

Salt Version:
          Salt: 3003.3

Dependency Versions:
          cffi: Not Installed
      cherrypy: Not Installed
      dateutil: 2.6.1
     docker-py: Not Installed
         gitdb: Not Installed
     gitpython: Not Installed
        Jinja2: 2.10.1
       libgit2: Not Installed
      M2Crypto: 0.35.2
          Mako: Not Installed
       msgpack: 0.6.2
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     pycparser: Not Installed
      pycrypto: Not Installed
  pycryptodome: Not Installed
        pygit2: Not Installed
        Python: 3.6.8 (default, Sep 21 2021, 10:09:35)
  python-gnupg: Not Installed
        PyYAML: 3.12
         PyZMQ: 19.0.0
         smmap: Not Installed
       timelib: Not Installed
       Tornado: 4.5.3
           ZMQ: 4.3.4

System Versions:
          dist: oracle 8.4
        locale: UTF-8
       machine: x86_64
       release: 4.18.0-305.17.1.el8_4.x86_64
        system: Linux
       version: Oracle Linux Server 8.4
@owmtia owmtia added Bug broken, incorrect, or confusing behavior needs-triage labels Sep 23, 2021
@garethgreenaway garethgreenaway added Feature new functionality including changes to functionality and code refactors, etc. and removed Bug broken, incorrect, or confusing behavior needs-triage labels Oct 19, 2021
@garethgreenaway garethgreenaway added this to the Phosphorus v3005.0 milestone Oct 19, 2021
@garethgreenaway garethgreenaway added the Phosphorus v3005.0 Release code name and version label Oct 19, 2021
@Ch3LL Ch3LL assigned twangboy and MKLeb and unassigned krionbsd and twangboy May 24, 2023
@MKLeb MKLeb removed the Phosphorus v3005.0 Release code name and version label Aug 22, 2023
@MKLeb
Copy link
Contributor

MKLeb commented Aug 23, 2023

Fixed by #65030

@MKLeb MKLeb closed this as completed Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature new functionality including changes to functionality and code refactors, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants