Skip to content

release-21.2: roachprod,roachtest: fix mounting on GCP and disable RAID0 in roachtests#72861

Merged
AlexTalks merged 1 commit intorelease-21.2from
blathers/backport-release-21.2-72803
Nov 17, 2021
Merged

release-21.2: roachprod,roachtest: fix mounting on GCP and disable RAID0 in roachtests#72861
AlexTalks merged 1 commit intorelease-21.2from
blathers/backport-release-21.2-72803

Conversation

@blathers-crl
Copy link
Copy Markdown

@blathers-crl blathers-crl bot commented Nov 17, 2021

Backport 1/1 commits from #72803 on behalf of @AlexTalks.

Fixes #72858.
Fixes #72859.
Fixes #72860.
FIxes #72866.
FIxes #72867.

/cc @cockroachdb/release


Fixes bugs introduced by #72553, which ported support for multiple
stores from AWS to GCP. This change fixes the bugs that caused
disks mounted to not be written to /etc/fstab on GCP instances,
causing mounts to go missing on instance restart. Additionally, this
change modifies roachtest to default to creating multiple stores on GCP
in roachprod invocations rather than mounting a RAID 0 array, thus
preserving the existing behavior used in roachtests such as
kv/multi-store-with-overload.

Fixes #72635

Release note: None


Release justification: fixes to internal roachtest/roachprod tooling only.

Fixes bugs introduced by #72553, which ported support for multiple
stores from AWS to GCP.  This change fixes the bugs that caused
disks mounted to not be written to `/etc/fstab` on GCP instances,
causing mounts to go missing on instance restart.  Additionally, this
change modifies roachtest to default to creating multiple stores on GCP
in roachprod invocations rather than mounting a RAID 0 array, thus
preserving the existing behavior used in roachtests such as
`kv/multi-store-with-overload`.

Fixes #72635

Release note: None
@blathers-crl blathers-crl bot requested review from a team as code owners November 17, 2021 09:13
@blathers-crl blathers-crl bot requested review from AlexTalks, nicktrav and tbg and removed request for a team November 17, 2021 09:13
@blathers-crl
Copy link
Copy Markdown
Author

blathers-crl bot commented Nov 17, 2021

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-21.2-72803 branch 2 times, most recently from 774ea54 to adee966 Compare November 17, 2021 09:13
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants