Bug 1490188 - properly describe what release_version var should be set to during upgrade
Summary: properly describe what release_version var should be set to during upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 2.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 3.0
Assignee: seb
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-11 04:46 UTC by Shinobu KINJO
Modified: 2017-12-05 23:42 UTC (History)
11 users (show)

Fixed In Version: RHEL: ceph-ansible-3.0.0-0.1.rc9.el7cp Ubuntu: ceph-ansible_3.0.0~rc9-2redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-05 23:42:56 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 1891 0 None None None 2017-09-13 21:47:52 UTC
Red Hat Product Errata RHBA-2017:3387 0 normal SHIPPED_LIVE Red Hat Ceph Storage 3.0 bug fix and enhancement update 2017-12-06 03:03:45 UTC

Description Shinobu KINJO 2017-09-11 04:46:04 UTC 
Description of problem:
In < rolling_update.yml >, there is a comment below:

 # /!\ DO NOT FORGET TO CHANGE THE RELEASE VERSION FIRST! /!\

This makes users who are going to achieve minor version upgrade (e.g., 2.1 to 2.2) confused because there is no descriptive comment.

Which file(s) is/are this message pointing to?
Comment 2 seb 2017-09-13 21:38:35 UTC 
There is no such things as release version for RHCS but I agree this is confusing.
Comment 3 seb 2017-09-15 13:09:31 UTC 
Since I haven't received any response from you, I consider that what I did in the PR is correct, so moving ahead with this one.
Comment 6 Harish NV Rao 2017-09-19 14:58:44 UTC 
@Seb, please let us know what is changed and steps to test.
Comment 7 seb 2017-09-19 15:10:05 UTC 
Harish, nothing to verify, perhaps just read the header of rolling_update.yml and make sure it's comprehensive.
Comment 9 Shinobu KINJO 2017-09-21 02:25:05 UTC 
(In reply to seb from comment #3)
> Since I haven't received any response from you, I consider that what I did
> in the PR is correct, so moving ahead with this one.

Sorry for the delay. That's much better.
Comment 12 errata-xmlrpc 2017-12-05 23:42:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3387
Note You need to log in before you can comment on or make changes to this bug.