Blocked on upgrading Hub due to Monocular MongoDB license

[scottrigby]

Problem

The problem and a longer-term recommended solution is outlined nicely here: helm/monocular#622

However in the meantime we're blocked on releasing Hub changes. Example: #210

Workaround

Test upgrading Monocular with the older (pre-license-change) version of MongoDB. If that goes well, temporarily deploy this workaround for a near-future Hub release.

[scottrigby]

Quick test, mongo seems unhappy:

config/hub-212.yaml (compare with config/helm-hub-values.yaml):

chartsvc:
  replicas: 6
  
ui:
  appName: Helm Hub
  aboutUrl: "https://github.com/helm/hub/blob/master/README.md"
  replicaCount: 3

ingress:
  enabled:  false

mongodb:
  image:
    tag: 4.0.3

$ NAME=hub-212
$ k create ns $NAME
namespace/hub-212 created
$ CHART_VERSION=1.4.14
$ MONGODB_ROOT_PASSWORD=****
$ VALUES=config/$NAME.yaml
$ helm upgrade --install $NAME monocular/monocular \
  --version $CHART_VERSION \
  --namespace $NAME \
  --set mongodb.mongodbRootPassword=$MONGODB_ROOT_PASSWORD \
  -f config/$NAME.yaml \
  -f config/repo-values.yaml
Release "hub-212" does not exist. Installing it now.

$ k get po -l app=mongodb
NAME                               READY   STATUS             RESTARTS   AGE
hub-212-mongodb-5ff4546c74-q52ld   0/1     CrashLoopBackOff   6          11m

Uh oh.

$ k describe po -l app=mongodb | tail
  Type     Reason     Age                  From                               Message
  ----     ------     ----                 ----                               -------
  Normal   Scheduled  12m                  default-scheduler                  Successfully assigned hub-212/hub-212-mongodb-5ff4546c74-q52ld to aks-nodepool1-31748052-2
  Warning  Unhealthy  10m                  kubelet, aks-nodepool1-31748052-2  Readiness probe failed: cannot exec in a stopped state: unknown
  Warning  Unhealthy  9m35s                kubelet, aks-nodepool1-31748052-2  Readiness probe failed: MongoDB shell version v4.0.3
  Normal   Pulled     8m52s (x5 over 12m)  kubelet, aks-nodepool1-31748052-2  Container image "docker.io/bitnami/mongodb:4.0.3" already present on machine
  Normal   Created    8m51s (x5 over 11m)  kubelet, aks-nodepool1-31748052-2  Created container hub-212-mongodb
  Normal   Started    8m48s (x5 over 11m)  kubelet, aks-nodepool1-31748052-2  Started container hub-212-mongodb
  Warning  Unhealthy  8m36s                kubelet, aks-nodepool1-31748052-2  Readiness probe errored: rpc error: code = Unknown desc = container not running (bda7883b74cf14b1b2606d27c9bbb96ae27ba5dc8525141083fbe1861294d89d)
  Warning  BackOff    117s (x39 over 10m)  kubelet, aks-nodepool1-31748052-2  Back-off restarting failed container

Logs:

$ k logs -l app=mongodb

Welcome to the Bitnami mongodb container
Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mongodb
Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mongodb/issues

Scott-CC:hub scottrigby$ k logs -l app=mongodb -p
2019-12-19T22:19:52.324+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2019-12-19T22:19:52.324+0000 I CONTROL  [initandlisten] 
2019-12-19T22:19:52.349+0000 F STORAGE  [initandlisten] Unable to start up mongod due to missing featureCompatibilityVersion document.
2019-12-19T22:19:52.349+0000 F STORAGE  [initandlisten] Please run with --repair to restore the document.
2019-12-19T22:19:52.349+0000 F -        [initandlisten] Fatal Assertion 40652 at src/mongo/db/repair_database_and_check_version.cpp 579
2019-12-19T22:19:52.349+0000 F -        [initandlisten] 

***aborting after fassert() failure

I found a bitnami issue with a similar error https://github.com/bitnami/bitnami-docker-mongodb/issues/117, but the recommendation was to upgrade the image, which we can't do because… license. Anyone have thoughts on this?

[phumberdroz]

There is an Open PR in Monocular to change Database providers from MongoDB to Foundation DB helm/monocular#656

[phumberdroz]

So I tested a similar deployment with

helm upgrade -i hub212 monocular/monocular \
--version 1.4.14 \
--namespace=hub-212 \
--set mongodb.mongodbRootPassword=test \
--set mongodb.image.tag=4.0.3-debian-9-r108

This worked fine

[mattfarina]

As there is a Monocular issue for this and the Helm Hub has been redirect to the Artifact Hub I'm going to close this issue.