Call Home Enabled in console

[bexsoft]

What does this do?

Enabled Call Home functionality in Console

How does it look?

Signed-off-by: Benjamin Perez [email protected]

[jinapurapu]

I don't have Subnet credentials to test the API, but UI LGTM

[cniackz]

@bexsoft when you get a chance, please resolve the conflicts:

[cniackz]

ok ignore my previous comment, maybe we need to have this on subnet first...

[bexsoft]

@bexsoft when you get a chance, please resolve the conflicts:

Fixed

[bexsoft]

Original PR: https://github.com/minio/console/pull/1664

[allanrogerr]

@bexsoft How do I enable these new options on the console - again I pulled the branch, checked out, ran make k8sdev and reloaded the console pod. I cannot see Call Home.

[prakashsvmx]

@bexsoft @dvaldivia

the call home can be enabled selectively as well e.g mc support callhome enable <alias> --logs mc support callhome enable <alias> --diag

So we would have to add these options in the UI as well. Could you please check this ?

[bexsoft]

@bexsoft @dvaldivia

the call home can be enabled selectively as well e.g mc support callhome enable <alias> --logs mc support callhome enable <alias> --diag

So we would have to add these options in the UI as well. Could you please check this ?

Hi @prakashsvmx !

Yes, Let me add them, this is an old PR so these features were not available at the time of development.

[bexsoft]

After attempting to use the API, the changes are not visible in the UI after refreshing the page

➜ portal-ui git:(call-home-api) ✗ sudo mc support callhome disable myminio --logs --insecure Logs is now disabled

but,

Yes, this was related to a functionality that was not implemented at the time this PR was originally made, implemented new functionality and redesigned screens

[pjuarezd]

Tested, build console and minio and loaded it into k8s kind using docker image, now the UI shows the callhome section

But keep receiving error code 500 in endpoint https://localhost:9444/api/v1/support/callhome.

{"code":500,"detailedMessage":"there is no target `subnet` for subsystem `logger_webhook`","message":"an error occurred, please try again"}

Could I be missing something?

So, I though it could be that I am missing to login in subnet, or register the cluster, so I went to subnet and reguistered it (using airgap method)

 ~ mc license update callhome ./cluster-license-.key --insecure
License updated successfully for callhome

And I still see the "Register your cluster" button, additionally to the redbanner error

So, noticed that a restart of the minio services is required to show the cluster as registered, so perhaps is worth show the "The instance needs to be restarted for configuration changes to take effec" banner?

Anyways, I restarted the cluster like this

Restart command successfully sent to `callhome`. Type Ctrl-C to quit or wait to follow the status of the restart process.
...!!
Restarted `callhome` successfully in 3 seconds

But I keep receiving that red banner error message, but at least I can enable callhome now

A console hard refresh and now the red banner is gone, looks like console (or minio, not sure) is looking for that webhook even before callhome is activated, because once calhome is activated it shows the logging webhook and the red banner dissapeared.

[jinapurapu]

Tested, working. I also saw the same red error banner with "there is no target subnet for subsystem logger_webhook" on first visiting the Call Home Screen, other than that LGTM.

[bexsoft]

Fixing red banner