Invoke-IcingaCheckMSSQLHealth - Icinga Exception: The term 'Get-IcingaServiceCheckName' is not recognized as the name of a cmdlet

Question

Invoke-IcingaCheckMSSQLHealth - Icinga Exception: The term 'Get-IcingaServiceCheckName' is not recognized as the name of a cmdlet

Skeletitor opened this issue 2 years ago · comments

Hi,

this error occures since the function 'Get-IcingaServiceCheckName' is moved to a private provider in powershell-plugins (Icinga/icinga-powershell-plugins@ac25708).

mrgohin · Answer 1 · Tue Jul 12 2022 21:34:50 GMT+0800 (China Standard Time)

+1 Not working as well

Lord Hepipud · Answer 2 · Thu Jul 14 2022 16:00:23 GMT+0800 (China Standard Time)

Thanks, will fix this with v1.10.0 of the plugins!

Lord Hepipud · Answer 3 · Thu Jul 14 2022 16:09:59 GMT+0800 (China Standard Time)

Fixed with v1.10.0: Icinga/icinga-powershell-plugins#308

mrgohin · Answer 4 · Thu Jul 14 2022 17:29:55 GMT+0800 (China Standard Time)

This is a great information but don't really solve my problem right now.

What do I have to do for a working implementation? At the moment this is used for a PoC and is considered as the way to go for our environment but if we don't get it to work it will be dropped as "not working, already fixed and release date out of range for testing".

This is no blame at all. Yours and your colleagues work on this framework is great and so bad needed. But we as user can't live with the fact that we rise our framework from 1.2.0 to 1.9.0 and some required / offered stuff is kinda bricked afterwards. It would be awesome if those dependencies like plugins will be more tested after core stuff changes.

Lord Hepipud · Answer 5 · Fri Jul 15 2022 01:12:33 GMT+0800 (China Standard Time)

Thank you for the feedback. I fully understand this point. Our test environments are frequently updated and maintained to ensure such things will not happen in the future. A change was already made internally after investigating this issue, as this slipped through our test environment because of some configuration errors.

Icinga for Windows v1.10.0 will be released on August 9th 2022, which might be to late for the internal testing. It depends a little on your requirements and handling of patches.

If you are willing to modify the files locally for the testing at the moment, you could simply make the changes as done in this PR: Icinga/icinga-powershell-plugins@51b2ca6

There are only two files affected to make the function available to the public.

Would this be something considerable for your testing? Once these two files are updated, you would simply require to run Publish-IcingaForWindowsComponent -Name 'plugins'

mrgohin · Answer 6 · Wed Jul 20 2022 16:12:14 GMT+0800 (China Standard Time)

Thank you for your reply. I will try this and report back!