Couchbase Server

Need "engineered" way of determining whether certain hotfixes have been applied

Details

Description

There have been recent examples (http://www.couchbase.com/issues/browse/CBSE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50618) where there has been some question whether or not a particular hotfix has been applied.

Relying on the customer to put a certain text file in place is really not the same as being able to tell positively from the logs.

This improvement should cover all aspects of possible hotfixes (Erlang/memcached/anything else)

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MB-6850 Windows: can't tell whether a hotfix has been applied

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mike Wiederhold added a comment -
Perry,

Can you please comment on this bug what the typical procedure is for applying a hot fix (memcached, bucket-engine, ep-engine) and then assign the issue back to me.
Show
Mike Wiederhold added a comment - Perry, Can you please comment on this bug what the typical procedure is for applying a hot fix (memcached, bucket-engine, ep-engine) and then assign the issue back to me.
Hide
Permalink
Perry Krug added a comment -
The specific instructions are usually provided along with each hotfix and entail replacing one or more binary files and restarting the node(s). Usually ep.so and/or memcached are replaced. The current instructions require that a user also copy over a text file that support is then supposed to be able to find...which many times seems not to happen. Do you want the specific list of tasks?

As far as I can remember, we've had some issues in the past with build version numbers not being updated correctly, particularly on Windows. Hopefully that is resolved at this point, but the build version of ep-engine doesn't necessarily cover all of the areas that we might be patching and I think we need a more "software-wide" solution that is documented and easy to understand.

The general issue is that support and customers will be applying various hotfixes over long periods of time and be analyzing customer systems that may or may not have had a hotfix/patch applied sometime long in the past. That's what I'm hoping we can make more reliable and deterministic.

Thanks

Perry
Show
Perry Krug added a comment - The specific instructions are usually provided along with each hotfix and entail replacing one or more binary files and restarting the node(s). Usually ep.so and/or memcached are replaced. The current instructions require that a user also copy over a text file that support is then supposed to be able to find...which many times seems not to happen. Do you want the specific list of tasks? As far as I can remember, we've had some issues in the past with build version numbers not being updated correctly, particularly on Windows. Hopefully that is resolved at this point, but the build version of ep-engine doesn't necessarily cover all of the areas that we might be patching and I think we need a more "software-wide" solution that is documented and easy to understand. The general issue is that support and customers will be applying various hotfixes over long periods of time and be analyzing customer systems that may or may not have had a hotfix/patch applied sometime long in the past. That's what I'm hoping we can make more reliable and deterministic. Thanks Perry
Hide
Permalink
Phil Labee added a comment -
Will insert info into manifest.xml, which is echoed to log files which are reported to Customer Service.
Show
Phil Labee added a comment - Will insert info into manifest.xml, which is echoed to log files which are reported to Customer Service.
Hide
Permalink
Phil Labee added a comment -
The update scripts for 1.8.1 Hot-fix MB-7805 inserts a line at the top of manifest.txt, like:

-- MB-7805 -- hot-fix applied Thu Feb 28 13:22:09 PST 2013
couchbase-server 2.1.0-725-rel Linux-i686
bucket_engine 2.1.0-725-rel Linux-i686
couchbase-cli 2.1.0-725-rel Linux-i686
. . .
Show
Phil Labee added a comment - The update scripts for 1.8.1 Hot-fix MB-7805 inserts a line at the top of manifest.txt, like: -- MB-7805 -- hot-fix applied Thu Feb 28 13:22:09 PST 2013 couchbase-server 2.1.0-725-rel Linux-i686 bucket_engine 2.1.0-725-rel Linux-i686 couchbase-cli 2.1.0-725-rel Linux-i686 . . .
Hide
Permalink
Farshid Ghods added a comment -
Phil,
in the sprint planning meeting we discussed a way for updating manifest.xml files.

in addition to that we also need to add the attached document which is licensing related.
Show
Farshid Ghods added a comment - Phil, in the sprint planning meeting we discussed a way for updating manifest.xml files. in addition to that we also need to add the attached document which is licensing related.
Hide
Permalink
Perry Krug added a comment -
Is the manifest.xml file already included in the collect_info output?
Show
Perry Krug added a comment - Is the manifest.xml file already included in the collect_info output?

People

  • Assignee:
    Phil Labee
    Reporter:
    Perry Krug
Vote (0)
Watch (4)

Dates

  • Created:
    Updated: