Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
7.0.0, 7.0.1
-
Ubuntu 18.04
-
Untriaged
-
Ubuntu 64-bit
-
1
-
Yes
-
Build Team 2021 Sprint 20
Description
Problem
When an offline upgrade is performed on a debian or ubuntu package install of 7.0.0 or 7.0.1, the chronicle directory gets erased due to an issue in the installer. This regression was introduced due to the fix made for MB-44229. This issue was originally reported by a forum user (https://forums.couchbase.com/t/couchbase-upgrade-issues-from-7-0-0-to-7-0-1/31867/2).
Steps to reproduce
1. Create a 2 node Ubuntu 18.04 cluster on 7.0.0 or 7.0.1
2. Create the travel-sample bucket
3. Offline upgrade cluster to 7.0.1 (steps can be found here: https://docs.couchbase.com/server/current/install/upgrade-cluster-offline.html)
What happens:
Upgrade is marked as successful in the CLI but the admin console does not come up
What is expected to happen:
Upgrade goes through fine and we are able to access the admin console. All the data remains intact.
Logs:
This issue was originally reproduced on an AWS instance. Logs to which have been attached to the ticket.
Appendix
QE has validated that this issue is not observed in all other supported platforms (Centos 7/8, Rhel 7/8, Suse 12/15, Oel 7/8, Amazon Linux 2 and Windows). It is only observed in deb installs in QE testing (Debian 10/11, Ubuntu 18/20).
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | collectinfo-2021-10-06T224640-ns_1@ec2-54-189-144-232.us-west-2.compute.amazonaws.com.zip [ 162894 ] |
Assignee | Meni Hillel [ JIRAUSER25407 ] | Bryan McCoid [ JIRAUSER25453 ] |
Summary | [Upgrade] Erlang crashed in ubuntu 18.04 when upgrade from 6.5.1 -> 7.0.0 -> 7.0.1 | [Upgrade][Ubuntu 18.04] Erlang crashed in ubuntu 18.04 when upgrade from 6.5.1 -> 7.0.0 -> 7.0.1 |
Summary | [Upgrade][Ubuntu 18.04] Erlang crashed in ubuntu 18.04 when upgrade from 6.5.1 -> 7.0.0 -> 7.0.1 | [Upgrade] Erlang crashed in ubuntu 18.04 when upgrade from 6.5.1 -> 7.0.0 -> 7.0.1 |
Assignee | Bryan McCoid [ JIRAUSER25453 ] | Thuan Nguyen [ thuan ] |
Assignee | Thuan Nguyen [ thuan ] | Bryan McCoid [ JIRAUSER25453 ] |
Attachment | erl_crash.dump.1633559222.11900.babysitter [ 162907 ] |
Attachment | node_down_upgrade.zip [ 162908 ] |
Attachment | image-2021-10-06-18-03-19-099.png [ 162926 ] |
Description |
Create 2 nodes cluster 6.5.1 in Ubuntu 18.04 in AWS.
Create travel-sample bucket. Upgrade cluster to 7.0.0 using offline upgrade. Upgrade passed. UI is up and running ok. Upgrade again this cluster to 7.0.1 using offline upgrade. Upgrade successfull in command line but failed to start UI. http://ec2-54-189-144-232.us-west-2.compute.amazonaws.com:8091/ui/index.html#/servers/list?commonBucket=travel-sample&scenarioZoom=minute&scenario=vfkz40slg Tested in centos 7.7 in AWS. After upgrade to 7.0.1, UI on both nodes are up as expected. |
Create 2 nodes cluster 6.5.1 in Ubuntu 18.04 in AWS.
Create travel-sample bucket. Upgrade cluster to 7.0.0 using offline upgrade. Upgrade passed. UI is up and running ok. Upgrade again this cluster to 7.0.1 using offline upgrade. Upgrade successfull in command line but failed to start UI. http://ec2-54-189-144-232.us-west-2.compute.amazonaws.com:8091/ui/index.html#/servers/list?commonBucket=travel-sample&scenarioZoom=minute&scenario=vfkz40slg I tried to test in other operating system like centos 7.7 in AWS. I could not reproduce this issue in centos 7.7. After upgrade to 7.0.1, UI on both nodes are up as expected. So this issue may be on ubuntu 18.04 only. |
Attachment | image-2021-10-07-12-48-55-553.png [ 163156 ] |
Fix Version/s | 7.0.2 [ 18012 ] |
Attachment | image-2021-10-07-13-46-41-040.png [ 163168 ] |
Attachment | image-2021-10-06-18-03-19-099.png [ 162926 ] |
Assignee | Bryan McCoid [ JIRAUSER25453 ] | Chris Hillery [ ceej ] |
Component/s | build [ 10200 ] | |
Component/s | ns_server [ 10019 ] |
Assignee | Chris Hillery [ ceej ] | Aliaksey Artamonau [ aliaksey artamonau ] |
Remote Link | This issue links to "Page (Couchbase, Inc. Wiki)" [ 23262 ] |
Comment | [ Is "chronicle" only used in clusters with more than one node? ] |
Assignee | Aliaksey Artamonau [ aliaksey artamonau ] | Chris Hillery [ ceej ] |
Sprint | Build Team 2021 Sprint 20 [ 1788 ] |
Component/s | installer [ 10221 ] | |
Component/s | tools [ 10223 ] | |
Component/s | build [ 10200 ] |
Worklog Id | 15238 [ 15238 ] | |
Remaining Estimate | 0h [ 0 ] | |
Time Spent | 3h [ 10800 ] |
Link | This issue blocks MB-46308 [ MB-46308 ] |
Labels | upgrade | approved-for-7.0.2 upgrade |
Assignee | Chris Hillery [ ceej ] | Thuan Nguyen [ thuan ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Labels | approved-for-7.0.2 upgrade | approved-for-7.0.2 releasenote upgrade |
Link | This issue relates to CBSP-3934 [ CBSP-3934 ] |
Summary | [Upgrade] Erlang crashed in ubuntu 18.04 when upgrade from 6.5.1 -> 7.0.0 -> 7.0.1 | [Upgrade] Offline Upgrade corrupts cluster config on ubuntu & debian 7.0.0 -> 7.0.x and 7.0.1 ->7.0.x |
Link | This issue is triggering FEWD-6045 [ FEWD-6045 ] |
Link | This issue is triggering FEWD-6046 [ FEWD-6046 ] |
Summary | [Upgrade] Offline Upgrade corrupts cluster config on ubuntu & debian 7.0.0 -> 7.0.x and 7.0.1 ->7.0.x | Offline upgrade on debian package installs corrupts config files |
Summary | Offline upgrade on debian package installs corrupts config files | Offline upgrade from 7.0.0 or 7.0.1 on debian and ubuntu package installs corrupts config files |
Affects Version/s | 7.0.0 [ 17233 ] |
Environment | Ubuntu 18.04 in AWS | Ubuntu 18.04 |
Description |
Create 2 nodes cluster 6.5.1 in Ubuntu 18.04 in AWS.
Create travel-sample bucket. Upgrade cluster to 7.0.0 using offline upgrade. Upgrade passed. UI is up and running ok. Upgrade again this cluster to 7.0.1 using offline upgrade. Upgrade successfull in command line but failed to start UI. http://ec2-54-189-144-232.us-west-2.compute.amazonaws.com:8091/ui/index.html#/servers/list?commonBucket=travel-sample&scenarioZoom=minute&scenario=vfkz40slg I tried to test in other operating system like centos 7.7 in AWS. I could not reproduce this issue in centos 7.7. After upgrade to 7.0.1, UI on both nodes are up as expected. So this issue may be on ubuntu 18.04 only. |
+Problem+
When an offline upgrade is performed on a debian or ubuntu package install of 7.0.0 or 7.0.1, the chronicle directory gets erased due to an issue in the installer. This regression was introduced due to the fix made for +Steps to reproduce+ 1. Create a 2 node cluster on 7.0.0 or 7.0.1 in Ubuntu 18.04 Create travel-sample bucket. Upgrade cluster to 7.0.0 using offline upgrade. Upgrade passed. UI is up and running ok. Upgrade again this cluster to 7.0.1 using offline upgrade. Upgrade successfull in command line but failed to start UI. http://ec2-54-189-144-232.us-west-2.compute.amazonaws.com:8091/ui/index.html#/servers/list?commonBucket=travel-sample&scenarioZoom=minute&scenario=vfkz40slg I tried to test in other operating system like centos 7.7 in AWS. I could not reproduce this issue in centos 7.7. After upgrade to 7.0.1, UI on both nodes are up as expected. So this issue may be on ubuntu 18.04 only. |
Description |
+Problem+
When an offline upgrade is performed on a debian or ubuntu package install of 7.0.0 or 7.0.1, the chronicle directory gets erased due to an issue in the installer. This regression was introduced due to the fix made for +Steps to reproduce+ 1. Create a 2 node cluster on 7.0.0 or 7.0.1 in Ubuntu 18.04 Create travel-sample bucket. Upgrade cluster to 7.0.0 using offline upgrade. Upgrade passed. UI is up and running ok. Upgrade again this cluster to 7.0.1 using offline upgrade. Upgrade successfull in command line but failed to start UI. http://ec2-54-189-144-232.us-west-2.compute.amazonaws.com:8091/ui/index.html#/servers/list?commonBucket=travel-sample&scenarioZoom=minute&scenario=vfkz40slg I tried to test in other operating system like centos 7.7 in AWS. I could not reproduce this issue in centos 7.7. After upgrade to 7.0.1, UI on both nodes are up as expected. So this issue may be on ubuntu 18.04 only. |
+Problem+
When an offline upgrade is performed on a debian or ubuntu package install of 7.0.0 or 7.0.1, the chronicle directory gets erased due to an issue in the installer. This regression was introduced due to the fix made for +Steps to reproduce+ 1. Create a 2 node Ubuntu 18.04 cluster on 7.0.0 or 7.0.1 2. Create the travel-sample bucket 3. Offline upgrade cluster to 7.0.1 (steps can be found here: https://docs.couchbase.com/server/current/install/upgrade-cluster-offline.html) +What happens:+ Upgrade is marked as successful in the CLI but the admin console does not come up +What is expected to happen:+ Upgrade goes through fine and we are able to access the admin console. All the data remains intact. +Logs:+ This issue was originally reproduced on an AWS instance. Logs to which have been attached to the ticket. +Appendix+ QE has been able to confirm that this issue is not observed in centos 7. We are validating all other supported platforms currently. |
Description |
+Problem+
When an offline upgrade is performed on a debian or ubuntu package install of 7.0.0 or 7.0.1, the chronicle directory gets erased due to an issue in the installer. This regression was introduced due to the fix made for +Steps to reproduce+ 1. Create a 2 node Ubuntu 18.04 cluster on 7.0.0 or 7.0.1 2. Create the travel-sample bucket 3. Offline upgrade cluster to 7.0.1 (steps can be found here: https://docs.couchbase.com/server/current/install/upgrade-cluster-offline.html) +What happens:+ Upgrade is marked as successful in the CLI but the admin console does not come up +What is expected to happen:+ Upgrade goes through fine and we are able to access the admin console. All the data remains intact. +Logs:+ This issue was originally reproduced on an AWS instance. Logs to which have been attached to the ticket. +Appendix+ QE has been able to confirm that this issue is not observed in centos 7. We are validating all other supported platforms currently. |
+Problem+
When an offline upgrade is performed on a debian or ubuntu package install of 7.0.0 or 7.0.1, the chronicle directory gets erased due to an issue in the installer. This regression was introduced due to the fix made for +Steps to reproduce+ 1. Create a 2 node Ubuntu 18.04 cluster on 7.0.0 or 7.0.1 2. Create the travel-sample bucket 3. Offline upgrade cluster to 7.0.1 (steps can be found here: https://docs.couchbase.com/server/current/install/upgrade-cluster-offline.html) +What happens:+ Upgrade is marked as successful in the CLI but the admin console does not come up +What is expected to happen:+ Upgrade goes through fine and we are able to access the admin console. All the data remains intact. +Logs:+ This issue was originally reproduced on an AWS instance. Logs to which have been attached to the ticket. +Appendix+ QE has been able to confirm that this issue is not observed in centos 7. We are validating all other supported platforms currently. |
Summary | Offline upgrade from 7.0.0 or 7.0.1 on debian and ubuntu package installs corrupts config files | Offline upgrade from 7.0.0 or 7.0.1 on debian and ubuntu package install corrupts config files |
Component/s | tools [ 10223 ] |
Description |
+Problem+
When an offline upgrade is performed on a debian or ubuntu package install of 7.0.0 or 7.0.1, the chronicle directory gets erased due to an issue in the installer. This regression was introduced due to the fix made for +Steps to reproduce+ 1. Create a 2 node Ubuntu 18.04 cluster on 7.0.0 or 7.0.1 2. Create the travel-sample bucket 3. Offline upgrade cluster to 7.0.1 (steps can be found here: https://docs.couchbase.com/server/current/install/upgrade-cluster-offline.html) +What happens:+ Upgrade is marked as successful in the CLI but the admin console does not come up +What is expected to happen:+ Upgrade goes through fine and we are able to access the admin console. All the data remains intact. +Logs:+ This issue was originally reproduced on an AWS instance. Logs to which have been attached to the ticket. +Appendix+ QE has been able to confirm that this issue is not observed in centos 7. We are validating all other supported platforms currently. |
+Problem+
When an offline upgrade is performed on a debian or ubuntu package install of 7.0.0 or 7.0.1, the chronicle directory gets erased due to an issue in the installer. This regression was introduced due to the fix made for +Steps to reproduce+ 1. Create a 2 node Ubuntu 18.04 cluster on 7.0.0 or 7.0.1 2. Create the travel-sample bucket 3. Offline upgrade cluster to 7.0.1 (steps can be found here: https://docs.couchbase.com/server/current/install/upgrade-cluster-offline.html) +What happens:+ Upgrade is marked as successful in the CLI but the admin console does not come up +What is expected to happen:+ Upgrade goes through fine and we are able to access the admin console. All the data remains intact. +Logs:+ This issue was originally reproduced on an AWS instance. Logs to which have been attached to the ticket. +Appendix+ QE has validated that this issue is not observed in all other supported platforms (Centos 7/8, Rhel 7/8, Suse 12/15, Oel 7/8, Amazon Linux 2 and Windows). It is only observed in deb installs in QE testing (Debian 10/11, Ubuntu 18/20). |
Attachment | ss 2021-10-11 at 11.38.54 AM.png [ 163539 ] |
Attachment | ss 2021-10-11 at 11.38.54 AM-1.png [ 163549 ] | |
Attachment | ss 2021-10-11 at 11.52.43 AM.png [ 163550 ] |
Attachment | ss 2021-10-11 at 11.38.54 AM.png [ 163539 ] |
Attachment | ss 2021-10-11 at 12.12.58 PM.png [ 163554 ] |
Sprint Status | Current Sprint [ 10027 ] | |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Remote Link | This issue links to "Page (Couchbase, Inc. Wiki)" [ 23278 ] |
Link | This issue relates to CBSP-3952 [ CBSP-3952 ] |
User hit this upgrade issue https://forums.couchbase.com/t/couchbase-upgrade-issues-from-7-0-0-to-7-0-1/31867/2