Skip to content
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.

Multiple issues with jenkins-x-mongodb after upgrading to 0.0.2191 #3020

Closed
sl1pm4t opened this issue Aug 21, 2018 · 7 comments
Closed

Multiple issues with jenkins-x-mongodb after upgrading to 0.0.2191 #3020

sl1pm4t opened this issue Aug 21, 2018 · 7 comments
Labels
lifecycle/rotten

Comments

@sl1pm4t
Copy link

sl1pm4t commented Aug 21, 2018

Initially I did an upgrade from 0.0.2137 to 0.0.2191 and got the following error:

error: failed to run 'helm upgrade --namespace  jenkins-x jenkins-x/jenkins-x-platform' command in directory '', output: 'Error: UPGRADE FAILED: Deployment.apps "jenkins-x-mongodb" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"chart":"mongodb-4.0.4", "release":"jenkins-x", "app":"mongodb"}: `selector` does not match template `labels`': exit status 1

To work around this, I manually deleted the jenkins-x-mongodb deployment and reran jx upgrade platform which appeared to complete successfully, however I noticed the new jenkins-x-mongodb was in CrashLoopBackOff state, due to the following error:

kubectl logs -f jenkins-x-mongodb-7dd488d47b-rwmm6

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

nami    INFO  Initializing mongodb
mongodb INFO  ==> Deploying MongoDB with persisted data...
mongodb INFO  ==> No injected configuration files found. Creating default config files...
mongodb INFO
mongodb INFO  ########################################################################
mongodb INFO   Installation parameters for mongodb:
mongodb INFO     Persisted data and properties have been restored.
mongodb INFO     Any input specified will not take effect.
mongodb INFO   This installation requires no credentials.
mongodb INFO  ########################################################################
mongodb INFO
nami    INFO  mongodb successfully initialized
INFO  ==> Starting mongodb...
INFO  ==> Starting mongod...
Expected boolean switch but found string:  for option: net.ipv6
try '/opt/bitnami/mongodb/bin/mongod --help' for more information

To workaround the second issue I used a myvalues.yaml file to force the mongodb container image tag to a version that has fixed the above error:

monocular:
  mongodb:
    image:
      tag: 4.0.1-debian-9-r12

See https://github.com/bitnami/bitnami-docker-mongodb/issues/108#issuecomment-414399540
@antweiss
Copy link

Just hit this too

@vishnoisuresh
Copy link

I had another upgradation issue after resolving the above issue. I needed to run it as a root user.

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

nami    INFO  Initializing mongodb
mongodb INFO  ==> Deploying MongoDB with persisted data...
mongodb INFO  ==> No injected configuration files found. Creating default config files...
mongodb INFO
mongodb INFO  ########################################################################
mongodb INFO   Installation parameters for mongodb:
mongodb INFO     Persisted data and properties have been restored.
mongodb INFO     Any input specified will not take effect.
mongodb INFO   This installation requires no credentials.
mongodb INFO  ########################################################################
mongodb INFO
nami    INFO  mongodb successfully initialized
INFO  ==> Starting mongodb...
INFO  ==> Starting mongod...
2018-08-21T08:16:01.193+0000 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten] MongoDB starting : pid=44 port=27017 dbpath=/opt/bitnami/mongodb/data/db 64-bit host=jenkins-x-mongodb-7fcffc98d5-krkwg
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten] db version v4.0.1
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten] git version: 54f1582fc6eb01de4d4c42f26fc133e623f065fb
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.0f  25 May 2017
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten] modules: none
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten] build environment:
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten]     distmod: debian92
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten]     distarch: x86_64
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2018-08-21T08:16:01.198+0000 I CONTROL  [initandlisten] options: { config: "/opt/bitnami/mongodb/conf/mongodb.conf", net: { bindIpAll: true, ipv6: true, port: 27017, unixDomainSocket: { enabled: true, pathPrefix: "/opt/bitnami/mongodb/tmp" } }, processManagement: { fork: false, pidFilePath: "/opt/bitnami/mongodb/tmp/mongodb.pid" }, security: { authorization: "disabled" }, setParameter: { enableLocalhostAuthBypass: "true" }, storage: { dbPath: "/opt/bitnami/mongodb/data/db", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: true } }
2018-08-21T08:16:01.198+0000 I STORAGE  [initandlisten] Detected data files in /opt/bitnami/mongodb/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-08-21T08:16:01.198+0000 I STORAGE  [initandlisten]
2018-08-21T08:16:01.198+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2018-08-21T08:16:01.198+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2018-08-21T08:16:01.198+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=2972M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2018-08-21T08:16:02.121+0000 I STORAGE  [initandlisten] WiredTiger message [1534839362:121319][44:0x7f2c615f19c0], txn-recover: Main recovery loop: starting at 591/768
2018-08-21T08:16:02.232+0000 I STORAGE  [initandlisten] WiredTiger message [1534839362:232698][44:0x7f2c615f19c0], txn-recover: Recovering log 591 through 592
2018-08-21T08:16:02.320+0000 I STORAGE  [initandlisten] WiredTiger message [1534839362:320368][44:0x7f2c615f19c0], txn-recover: Recovering log 592 through 592
2018-08-21T08:16:02.370+0000 I STORAGE  [initandlisten] WiredTiger message [1534839362:370395][44:0x7f2c615f19c0], txn-recover: Set global recovery timestamp: 0
2018-08-21T08:16:02.528+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
2018-08-21T08:16:02.574+0000 I CONTROL  [initandlisten] ** WARNING: You are running this process as the root user, which is not recommended.
2018-08-21T08:16:02.574+0000 I CONTROL  [initandlisten]
2018-08-21T08:16:02.574+0000 I CONTROL  [initandlisten]
2018-08-21T08:16:02.574+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2018-08-21T08:16:02.574+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2018-08-21T08:16:02.574+0000 I CONTROL  [initandlisten]
2018-08-21T08:16:02.592+0000 F CONTROL  [initandlisten] ** IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.6 before attempting an upgrade to 4.0; see http://dochub.mongodb.org/core/4.0-upgrade-fcv for more details.
2018-08-21T08:16:02.592+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2018-08-21T08:16:02.592+0000 I NETWORK  [initandlisten] removing socket file: /opt/bitnami/mongodb/tmp/mongodb-27017.sock
2018-08-21T08:16:02.592+0000 I STORAGE  [initandlisten] WiredTigerKVEngine shutting down
2018-08-21T08:16:02.675+0000 I STORAGE  [initandlisten] Downgrading WiredTiger datafiles.
2018-08-21T08:16:02.885+0000 I STORAGE  [initandlisten] WiredTiger message [1534839362:885140][44:0x7f2c615f19c0], txn-recover: Main recovery loop: starting at 592/3968
2018-08-21T08:16:02.985+0000 I STORAGE  [initandlisten] WiredTiger message [1534839362:985252][44:0x7f2c615f19c0], txn-recover: Recovering log 592 through 593
2018-08-21T08:16:03.052+0000 I STORAGE  [initandlisten] WiredTiger message [1534839363:52648][44:0x7f2c615f19c0], txn-recover: Recovering log 593 through 593
2018-08-21T08:16:03.103+0000 I STORAGE  [initandlisten] WiredTiger message [1534839363:103244][44:0x7f2c615f19c0], txn-recover: Set global recovery timestamp: 0
2018-08-21T08:16:03.626+0000 I STORAGE  [initandlisten] shutdown: removing fs lock...
2018-08-21T08:16:03.627+0000 I CONTROL  [initandlisten] now exiting
2018-08-21T08:16:03.627+0000 I CONTROL  [initandlisten] shutting down with code:62

@salaboy
Copy link

salaboy commented Sep 19, 2018

This can be solved by adding this to the deployment:
- name: MONGODB_ENABLE_IPV6
value: "no”

Can we set this as default env variable for Mongo?

@ryandawsonuk ryandawsonuk mentioned this issue Sep 20, 2018
Closed
@jenkins-x-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@jenkins-x-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

@jenkins-x-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/rotten
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@salaboy @antweiss @sl1pm4t @vishnoisuresh @jenkins-x-bot