(solved) Firmware - Plugins -> shows misconfigured / orphaned

[ArminF]

Hello,
just updated the firmware for OPNSense to OPNsense 21.1.3-amd64.
Took a look on the plugins later and saw the attached screenshot.

Anything i did wrong? Anything how to fix it?

os-sensei (misconfigured)   1.7.1   81.6MiB   
os-sensei-db (orphaned)   1.7.20210208135119   64.7MiB   unknown-repository
os-sensei-updater (misconfigured)   1.7   4.45KiB   SunnyValley   OPNsense Sensei Plugin Updater   
os-sunnyvalley (installed)

I do not use the cloud thing from Sensei. So local usage only. Free Edition

thanks
armin

[mb]

Hi Armin,

Cloud is not related to package management. You're fine.

With regard to "misconfigured" ones, does a refresh of the browser help?

For sensei-db, it is expected that the package is in "orphaned" state; since we are maintaining this package independent of a repo.

Having said that, we're changing this with 1.8 (expected this week). With 1.8 sensei-db will not show up here since we'll be shipping it as a plain tarball. This will be a lot simpler and convenient to maintain.

[franco]

Orphaned isn't new and misconfigured is explained here:

https://github.com/opnsense/changelog/blob/b2e3f2d06e2762f56d844b0cdb1be8cc1f47a13a/community/21.1/21.1.3#L5-L10

Misconfigured basically means installed but not via GUI.


Cheers,
Franco

[ArminF]

Thank you both!

I reset the plugin and rebooted but it still shows as "misconfigured"

***GOT REQUEST TO RESYNC***
Ignoring invalid metadata: /usr/local/opnsense/version/sensei
Ignoring invalid metadata: /usr/local/opnsense/version/sensei-db
Ignoring invalid metadata: /usr/local/opnsense/version/sensei-updater
***DONE***

Anything i else can do?
Would i need to reinstall and restore my backup for sensei?

thanks
armin

[franco]

Hi Armin,

Ah, ok, sensei repository needs to add our plugin metadata changes for this to work:

https://github.com/opnsense/plugins/commit/e06826bf9e71e

You can probably work around this by reinstalling the misconfigured plugins from the packages tab.

In any case "misconfigured" is just cosmetics: the config doesn't know about this plugin in case you want to restore the configuration elsewhere losing the information that this plugin was previously installed.


Cheers,
Franco

[ArminF]

Franko,
thanks!

i did reinstall it through plugins but it still shows misconfigured.
So if its "just cosmetics" i would say it does look ugly but works :)

i will wait for the update and uninstall it with a install later and restore backup.

thanks
armin

[franco]

Ok, the reinstall trick also requires the plugin metadata. I'm sure Murat and crew will fix this soon.


Cheers,
Franco

[ArminF]

Gracie Mille Franco!

[mb]

@franco, thanks for the heads-up. We were not aware of this.

@ArminF, we'll have a look at this. This should not cause any operational problems for now.

[IsaacFL]

So what was the solution? Mine still has this issue.  Says solved?

[franco]

It's not a super pressing issue. It's just a mismatch between config.xml and installed plugins that can't be solved with the old plugin metadata format.

You see, people always asked for a way to register their plugins in the config.xml to restore then at once, but now that we have this feature people ask how they can solve a situation that never really changed or at least can't be moved from 95% to 100% done immediately for third party plugins because they need to ship the new format first.


Cheers,
Franco

[mb]

An update on this: we have the new packages ready and they are being tested now. We hope to ship them next Monday.

[wget]

Today when upgrading to 21.7 to 21.7.1, I noticed that some of the plugins I had previously installed did have a mention "misconfigured" next to them.

This was happening for
* os-acme-client
* os-dmidecode
* os-dnscrypt-proxy
* os-dyndns

I removed each of them and reinstalled them. Just for people reading this afterwards after a search on a search engine, I didn't have to respecify the configuration, so **it seems** removing and reinstalling them do keep their configuration. This would have been annoying if I had to (esp. for DynDNS on Cloudflare and the LetsEncrypt conf).

Now the "misconfigured" mention is just replaced by "installed" and everything goes fine.