Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pacific kickoff #34272

Merged
merged 32 commits into from Apr 12, 2020
Merged

pacific kickoff #34272

merged 32 commits into from Apr 12, 2020

Conversation

liewegas
Copy link
Member

Add release definitions, release kickoff checklist, and other bits needed at the
start of each major release.

@@ -1082,7 +1082,7 @@ function try_known_milestones {
mimic) mn="11" ;;
nautilus) mn="12" ;;
octopus) mn="13" ;;
pacific) mn="TBD" ;;
pacific) mn="14" ;;
Copy link
Contributor

@smithfarm smithfarm Mar 31, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need to be careful with this one - the milestone number is set by GitHub. Pacific is expected to be milestone number 14, but we need to verify that before setting it here

Also, the script will work for pacific even when the number is set to "TBD" - it will fall back to querying the GitHub API to get the number.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, the "pacific" milestone has not been created yet, so we should not make this change now

it will be made when backporting to pacific starts.

Scripts
~~~~~~~

- [x] src/script/backport-create-issue (`releases()`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we will modify backport-create-issue to support pacific only when backporting to pacific starts, so this item doesn't belong here


- [x] src/script/backport-create-issue (`releases()`)
- [x] src/script/backport-resolve-issue (`releases()`, `ver_to_release()`... but for X-1)
- [x] src/script/ceph-backport.sh (`try_known_milestones()`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we will modify ceph-backport.sh to support pacific only when backporting to pacific starts, so this item doesn't belong here

@@ -350,7 +350,8 @@ def tag_sha1(repo, sha1):

def ver_to_release():
return {'v9.2': 'infernalis', 'v10.2': 'jewel', 'v11.2': 'kraken',
'v12.2': 'luminous', 'v13.2': 'mimic', 'v14.2': 'nautilus'}
'v12.2': 'luminous', 'v13.2': 'mimic', 'v14.2': 'nautilus',
'v15.2': 'octopus'}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is OK

@@ -324,7 +324,7 @@ def read_from_file(fs):
def releases():
return ('argonaut', 'bobtail', 'cuttlefish', 'dumpling', 'emperor',
'firefly', 'giant', 'hammer', 'infernalis', 'jewel', 'kraken',
'luminous', 'mimic', 'nautilus')
'luminous', 'mimic', 'nautilus', 'octopus')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is OK

@@ -122,7 +122,7 @@ def connect_to_redmine(a):
def releases():
return ('argonaut', 'bobtail', 'cuttlefish', 'dumpling', 'emperor',
'firefly', 'giant', 'hammer', 'infernalis', 'jewel', 'kraken',
'luminous', 'mimic', 'nautilus', 'octopus')
'luminous', 'mimic', 'nautilus', 'octopus', 'pacific')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not OK

- [x] src/script/backport-create-issue (`releases()`)
- [x] src/script/backport-resolve-issue (`releases()`, `ver_to_release()`... but for X-1)
- [x] src/script/ceph-backport.sh (`try_known_milestones()`)
- [x] src/script/ceph-release-notes (X-1)
Copy link
Contributor

@smithfarm smithfarm Mar 31, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@liewegas
Copy link
Member Author

liewegas commented Apr 3, 2020

Doing a final check that the upgrades are working, but otherwise I think this is ready to go

@liewegas
Copy link
Member Author

liewegas commented Apr 3, 2020 via email

@@ -20,7 +20,7 @@ upgrade-sequence:
- sleep:
duration: 60
- ceph.restart:
daemons: [mon.c]
daemons: [mon.c, mgr.x]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We recently made this change in #33705 to fix https://tracker.ceph.com/issues/44387. I am afraid reverting it will make the bug reappear.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, ok. i'll just whitelist the message here too then. i was hoping to have one test that did the mons before mgr, but i think a manual test for this is sufficient.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cool, want to get rid of the qa/suites/upgrade/nautilus-x/parallel/3-upgrade-sequence/upgrade-mon-osd-mds.yaml change?

Copy link
Member

@neha-ojha neha-ojha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, assuming #34272 (comment) is addressed.

Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
If our release isn't in the always_on_map, say because you just upgraded,
then start with the modules from the last/most recent release.  This
should be sufficient to allow an upgrade when the mon is still the old
release and the mgrmap doesn't tell us what modules we should be enabling.

(Arguably, the always_on_modules should be enshrined in the MgrMap itself
and not in the mon?)

Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
v2 was introduced in nautilus, and we don't support mimic -> pacific
upgrades (only mimic -> octopus).  This test can be removed!

Signed-off-by: Sage Weil <sage@redhat.com>
This happens because mgrs may start before mons, or before mons have
published a new mgrmap that disables orchestrator_cli.

Signed-off-by: Sage Weil <sage@redhat.com>
Also rename 3-compat_client/mimic -> pacific to match the min_client
setting (the naming here confuses me...).

Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
@tchaikov
Copy link
Contributor

@tchaikov
Copy link
Contributor

@liewegas is this PR good to merge?

@liewegas
Copy link
Member Author

@liewegas is this PR good to merge?

Almost, still sorting out why upgrade/nautilus-x is failing with

2020-04-10T21:46:37.686 INFO:teuthology.orchestra.run.smithi134.stdout:{"checks":{"MGR_MODULE_ERROR":{"severity":"HEALTH_ERR","summary":{"message":"Module 'orchestrator_cli' has failed: Not found or unloadable"}}},"status":"HEALTH_ERR"}

Old modules may be in the mgrmap (and always_on) but no longer exist.  Do
not try to load those or raise errors about them.

Signed-off-by: Sage Weil <sage@redhat.com>
@liewegas liewegas merged commit d3d1ea5 into ceph:master Apr 12, 2020
@liewegas
Copy link
Member Author

finally merged!

clean upgrade run: http://pulpito.ceph.com/sage-2020-04-11_21:45:45-upgrade-wip-sage3-testing-2020-04-11-1337-distro-basic-smithi/

@liewegas liewegas deleted the pacific-kickoff branch April 12, 2020 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants