Support for XenServer 8.2

[loquanet]

Getting host list using: /opt/xensource/bin/xe host-list hostname=grep "^HOSTNAME=" /etc/sysconfig/network | awk -F= '{print$2}' params=uuid --minimal Detected HOST UUID: Error: Failed to obtain HOSTUUID from XE CLI

./patch_checker.py -D Citrix_XenServer_Patcher_Version: 1.5.2 Detected XenServer Version: 8.2.0

xsver: 82 XenServer machine identified. XenServer Version 82 detected. XE utility located OK Testing XE CLI function using: /opt/xensource/bin/xe host-list XE working OK Downloading patch list XML

[dalgibbard]

Does this help at all? https://github.com/dalgibbard/citrix_xenserver_patcher/issues/70

[loquanet]

Yes that fixed it.

But new error:

Installed Patches: ['51398fd6-0000-0000-984a-fc7c2a4779b4', '661184a8-0000-0000-b6fb-7a62a232dda5'] Trying to establish which 'null' is correct. If you see an 'X MATCHED' message, please notify me on Github via an Issue!

Failed to read Auto-Exclusion List from: https://raw.githubusercontent.com/dalgibbard/citrix_xenserver_patcher/master/exclusions/XS82_excludes.py Check the URL is available, and connectivity is OK.

Error: HTTP Error 404: Not Found

NOTE: To proceed without downloading the Auto-Excludes file (not recommended), pass the "-E" flag.

On Sun, Dec 20, 2020 at 9:28 AM Darren Gibbard notifications@github.com wrote:

Does this help at all? #70 https://github.com/dalgibbard/citrix_xenserver_patcher/issues/70

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dalgibbard/citrix_xenserver_patcher/issues/82#issuecomment-748636149, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOQDW2TNKBDW7DVKF3HCPRLSVYX4HANCNFSM4VDHGU4A .

-- -- Derek Gold Solutions Consultant / Systems Solutions Architect

Loquanet, Inc. MSP, IT Solutions, Hosted IaaS, & Private Sector Solutions

Office // 213-290-1890

[dalgibbard]

Probably worth checking this :) https://github.com/dalgibbard/citrix_xenserver_patcher/issues/81

[loquanet]

I ran it with the -E and it said the same error. Like the switch e didn't do anything.

On Mon, Dec 21, 2020, 00:30 Darren Gibbard notifications@github.com wrote:

Probably worth checking this :) #81 https://github.com/dalgibbard/citrix_xenserver_patcher/issues/81

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dalgibbard/citrix_xenserver_patcher/issues/82#issuecomment-748814972, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOQDW2WOKDSKF52Y3EZEM5TSV32QJANCNFSM4VDHGU4A .

[dalgibbard]

I mean specifically, that xenserver patcher isn't required for this build, as it's managed by a different update process (yum or similar)

[loquanet]

Well was on the phone with Citrix tech support and I was told and I performed a required one by one update manually for each patch on 8.1 or 8.2. They said start at the highest patch because they might include lower patches.

Manually patching several xen host is beyond time consuming and annoying.

I thought your repo might help eliminate this headache.

On Mon, Dec 21, 2020, 11:29 Darren Gibbard notifications@github.com wrote:

I mean specifically, that xenserver patcher isn't required for this build, as it's managed by a different update process (yum or similar)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dalgibbard/citrix_xenserver_patcher/issues/82#issuecomment-749126024, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOQDW2W2ZYPL2OSYASOXZULSV6HXLANCNFSM4VDHGU4A .

[dalgibbard]

I haven't had to support xenserver hosts since 6.2 unfortunately, so this hasn't been tested past v7.

Maybe check forked versions of this repo in case someone has continued to support it in their own branch?

According to the linked ticket, the patch application process might just be via yum, which wouldn't need a new utility, but I can't confirm that unfortunately.