OCPBUGS-11592: increase etcd memory limit floor

[dusk125]

The memory limit floor of 50mb was too low and was causing issues in testing, this PR raises this minimum valid value to 128mb to resolve this issue.

[openshift-ci-robot]

@dusk125: This pull request references Jira Issue OCPBUGS-11497, which is invalid:

• expected the bug to target the "4.14.0" version, but it targets "4.13" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

The memory limit floor of 50mb was too low and was causing issues in testing, this PR raises this minimum valid value to 128mb to resolve this issue.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@dusk125: This pull request references Jira Issue OCPBUGS-11592, which is invalid:

• expected the bug to target the "4.14.0" version, but it targets "4.14" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

The memory limit floor of 50mb was too low and was causing issues in testing, this PR raises this minimum valid value to 128mb to resolve this issue.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dusk125]

/jira refresh

[openshift-ci-robot]

@dusk125: This pull request references Jira Issue OCPBUGS-11592, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.0) matches configured target version for branch (4.14.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jogeo

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dusk125]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@dusk125: once the present PR merges, I will cherry-pick it on top of release-4.13 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dhellmann]

The verify job is reporting an error because we now require changes to microshift code that show up in the etcd build to be revendored as part of the same PR.

You need to run 'make vendor-etcd' and commit the results to include
these files in the PR:

etcd/vendor/github.com/openshift/microshift/pkg/config/etcd.go

[dhellmann]

Given the refactoring of the config code that landed last week for 4.14 that we won't be backporting, you may have to hand-craft the backport of this fix into 4.13.

[dhellmann]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, dusk125

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dhellmann]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@dusk125: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@dusk125: Jira Issue OCPBUGS-11592: All pull requests linked via external trackers have merged:

• openshift/microshift#1647

Jira Issue OCPBUGS-11592 has been moved to the MODIFIED state.

Details

In response to this:

The memory limit floor of 50mb was too low and was causing issues in testing, this PR raises this minimum valid value to 128mb to resolve this issue.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@dusk125: #1647 failed to apply on top of branch "release-4.13":

Applying: OCPBUGS-11497: increase etcd memory limit floor
Using index info to reconstruct a base tree...
M	docs/howto_config.md
A	etcd/vendor/github.com/openshift/microshift/pkg/config/etcd.go
M	pkg/config/config_test.go
A	pkg/config/etcd.go
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): pkg/config/etcd.go deleted in HEAD and modified in OCPBUGS-11497: increase etcd memory limit floor. Version OCPBUGS-11497: increase etcd memory limit floor of pkg/config/etcd.go left in tree.
Auto-merging pkg/config/config_test.go
CONFLICT (content): Merge conflict in pkg/config/config_test.go
CONFLICT (modify/delete): etcd/vendor/github.com/openshift/microshift/pkg/config/etcd.go deleted in HEAD and modified in OCPBUGS-11497: increase etcd memory limit floor. Version OCPBUGS-11497: increase etcd memory limit floor of etcd/vendor/github.com/openshift/microshift/pkg/config/etcd.go left in tree.
Auto-merging docs/howto_config.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OCPBUGS-11497: increase etcd memory limit floor
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick release-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.