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

win_hotfix not failing but not installing a KBXXXX.msu #597

Open
hugohdz89 opened this issue Dec 13, 2024 · 1 comment
Open

win_hotfix not failing but not installing a KBXXXX.msu #597

hugohdz89 opened this issue Dec 13, 2024 · 1 comment

Comments

@hugohdz89
Copy link

SUMMARY

I'm trying to install the Cumulative Update for Microsoft server for November and it's not installing it but also not showing any error. Tried to install the most recent Cumulative Update for Microsoft server December and I'm facing the same situation. The task is not failing and it doesn't change anything, like if the hotfix was already installed in the server.

ISSUE TYPE
  • Bug Report
COMPONENT NAME

win_hotfix

ANSIBLE VERSION

I'm running the playbook using AAP.

  ansible-playbook [core 2.16.11]
  config file = /runner/project/ansible.cfg
  configured module search path = ['/home/runner/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.11/site-packages/ansible
  ansible collection location = /runner/requirements_collections:/home/runner/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible-playbook
  python version = 3.11.9 (main, Aug 26 2024, 10:40:41) [GCC 8.5.0 20210514 (Red Hat 8.5.0-22)] (/usr/bin/python3.11)
  jinja version = 3.1.4
  libyaml = True
COLLECTION VERSION
  - name: community.windows
    version: 2.2.0
  - name: ansible.windows
    version: 2.5.0
CONFIGURATION

OS / ENVIRONMENT

Target OS: Microsoft Windows Server 2022 Version 21H2

STEPS TO REPRODUCE

Running this task via AAP. The file is already existing in the remote server.

    - name: Installing KB
      community.windows.win_hotfix:
        source: "C:\\kb_update\\KB5048654.msu"
        state: present
EXPECTED RESULTS

TASK [Installing KB] *******************************************************
changed: [my-windows-server]

ACTUAL RESULTS

ok: [my-windows-server] => {"changed": false, "identifier": "Package_for_ServicingStack_275031bf3856ad364e35amd6420348.2750.1.0", "identifiers": ["Package_for_ServicingStack_275031bf3856ad364e35amd6420348.2750.1.0", "Multiple_Packages~~~~0.0.0.0"], "kb": "KB5048654", "kbs": ["KB5048654", "KB5048654"], "reboot_required": false}


@hugohdz89
Copy link
Author

Checking on the server, the last Cumulative Update installed in the server is from October, KB5044281.

Tried to run the same playbook using that KB and got this, which means the package is already installed so the output is expected.

ok: [my-windows-server] => {"changed": false, "identifier": "Package_for_ServicingStack_275031bf3856ad364e35amd6420348.2750.1.0", "identifiers": ["Package_for_ServicingStack_275031bf3856ad364e35amd6420348.2750.1.0", "Multiple_Packages~~~~0.0.0.0"], "kb": "KB5044281", "kbs": ["KB5044281", "KB5044281"], "reboot_required": false}

However, when tried to install the KB from November, KB5046616. Got this output, which for my understanding, means that the Packages from the KB are already installed in the server, but checking in the server, the KB5046616 is not installed there.

ok: [my-windows-server] => {"changed": false, "identifier": "Package_for_ServicingStack_275031bf3856ad364e35amd6420348.2750.1.0", "identifiers": ["Package_for_ServicingStack_275031bf3856ad364e35amd6420348.2750.1.0", "Multiple_Packages~~~~0.0.0.0"], "kb": "KB5046616", "kbs": ["KB5046616", "KB5046616"], "reboot_required": false}

Finally, I just tried with the KB from December, KB5048654 and got the same output.


ok: [my-windows-server] => {"changed": false, "identifier": "Package_for_ServicingStack_275031bf3856ad364e35amd6420348.2750.1.0", "identifiers": ["Package_for_ServicingStack_275031bf3856ad364e35amd6420348.2750.1.0", "Multiple_Packages~~~~0.0.0.0"], "kb": "KB5048654", "kbs": ["KB5048654", "KB5048654"], "reboot_required": false}

Looks like the Identifier within the three KB's from the last 3 months is the same.

Is win_hotfix relying on this Identifier name to decide whether to install the KB or just confirm it's already installed and do nothing on the server?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant