# \[12.0.1\] partner-onboarder installation errors / misisng minimoto

**URL:** <https://community.mosip.io/t/12-0-1-partner-onboarder-installation-errors-misisng-minimoto/1247>\
**Category:** Support\
**Created:** [April 24, 2024, 8:38am UTC](https://community.mosip.io/t/12-0-1-partner-onboarder-installation-errors-misisng-minimoto/1247 "2024-04-24T08:38:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tommaso\_Doninelli](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/tommaso_doninelli/32/930_2.png) [@Tommaso\_Doninelli](https://community.mosip.io/u/Tommaso_Doninelli)\
**Post date:** [April 24, 2024, 8:38am UTC](https://community.mosip.io/t/12-0-1-partner-onboarder-installation-errors-misisng-minimoto/1247/1 "2024-04-24T08:38:10Z")

</div>

Hi, I’m trying to install MOSIP 12.0.1 in an AWS EKS cluster (since a while…)  
I managed to get to deploy the `partner-onboarder` module, but all the jobs have errors.

Mostly, the error is related to a missing RBAC ClusterRole and missing secrets in namespaces.

As an example, the `partner-onboarder-resident` tries to download a secret from the `esignet` namespace that does not exist, using a cluster role “partner-onboarder” that does not exist - should it be deployed by the partner-onboarder install script?

```auto
 1. TypeError                                                                   
                Cannot read properties of null (reading 'signedCertificateData') 
                at test-script                                                   
                inside "cert_upload / upload-leaf-certificate"                   
Updating Resident OIDC Client Id
Error from server (Forbidden): error when retrieving current configuration of:
Resource: "/v1, Resource=secrets", GroupVersionKind: "/v1, Kind=Secret"
Name: "resident-oidc-onboarder-key", Namespace: "esignet"
from server for: "STDIN": secrets "resident-oidc-onboarder-key" is forbidden: User "system:serviceaccount:onboarder:partner-onboarder" cannot get resource "secrets" in API group "" in the namespace "esignet": RBAC: clusterrole.rbac.authorization.k8s.io "partner-onboarder" not found
Resident OIDC client id updated successfully

```

All the partner-onboarder jobs have the similar errors, as the partner-onboarder-mimoto

```auto
 1. TypeError                                                                   
                Cannot read properties of null (reading 'signedCertificateData') 
                at test-script                                                   
                inside "cert_upload / upload-leaf-certificate"                   
Updating Mimoto Wallet Binding Partner API Key
Error from server (Forbidden): error when retrieving current configuration of:
Resource: "/v1, Resource=secrets", GroupVersionKind: "/v1, Kind=Secret"
Name: "mimoto-wallet-binding-partner-api-key", Namespace: "mimoto"
from server for: "STDIN": secrets "mimoto-wallet-binding-partner-api-key" is forbidden: User "system:serviceaccount:onboarder:partner-onboarder" cannot get resource "secrets" in API group "" in the namespace "mimoto": RBAC: clusterrole.rbac.authorization.k8s.io "partner-onboarder" not found
Mimoto Wallet Binding Partner API Key updated successfully

```

Again, the `mimoto` namespace does not exists…

---

<div class="post-metadata">

**Author:** ![Tommaso\_Doninelli](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/tommaso_doninelli/32/930_2.png) [@Tommaso\_Doninelli](https://community.mosip.io/u/Tommaso_Doninelli)\
**Post date:** [April 24, 2024, 8:58am UTC](https://community.mosip.io/t/12-0-1-partner-onboarder-installation-errors-misisng-minimoto/1247/3 "2024-04-24T08:58:34Z")

</div>

The resident module delete the mimoto release, but It’s not clear to me who should have installed it in the first place

> <https://github.com/mosip/mosip-infra/blob/release-1.2.0.x/deployment/v3/mosip/resident/delete.sh#L11>

---

<div class="post-metadata">

**Author:** ![Tommaso\_Doninelli](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/tommaso_doninelli/32/930_2.png) [@Tommaso\_Doninelli](https://community.mosip.io/u/Tommaso_Doninelli)\
**Post date:** [April 24, 2024, 1:04pm UTC](https://community.mosip.io/t/12-0-1-partner-onboarder-installation-errors-misisng-minimoto/1247/4 "2024-04-24T13:04:22Z")

</div>

Ok, I managed to create the mimoto api key. I manually created the RBAC role, and granted `s3:*` on all resources to the datashare AWS Iam User

Now the README is telling me to restart the pod “mimoto”, but I don’t have any mimoto running in my cluster…

---

<div class="post-metadata">

**Author:** ![Rakshith\_B](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/rakshith_b/32/951_2.png) [@Rakshith\_B](https://community.mosip.io/u/Rakshith_B)\
**Post date:** [April 25, 2024, 12:38pm UTC](https://community.mosip.io/t/12-0-1-partner-onboarder-installation-errors-misisng-minimoto/1247/5 "2024-04-25T12:38:24Z")

</div>

Hi, We are deploying Mimoto independently and onboarding separately. You can find the repository here: [link](https://github.com/mosip/mimoto/tree/v0.11.0/partner-onboarder). For the partner-onboarder, please set the mimoto-keybinding to false in values.yaml and disregard the command ‘helm -n $NS delete mimoto’ as it was mistakenly left in. We apologize for any inconvenience caused