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
Bug 1826021: Fix a problem with a greedy regular expression matching more than needed #1913
Bug 1826021: Fix a problem with a greedy regular expression matching more than needed #1913
Conversation
…ot the matching entry
|
@retroflexer: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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. |
|
Compare the outputs from test 1, test 2 and test 3 patterns. The pattern used in this script is test 3. Originally the code had a pattern of test 1. |
|
@retroflexer: This pull request references Bugzilla bug 1826021, which is invalid:
Comment In response to this:
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. |
|
/lgtm |
|
/bugzilla refresh |
|
@retroflexer: This pull request references Bugzilla bug 1826021, which is invalid:
Comment In response to this:
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. |
|
/test e2e-aws-scaleup-rhel7 |
|
/bugzilla refresh Recalculating validity in case the underlying Bugzilla bug has changed. |
|
@openshift-bot: This pull request references Bugzilla bug 1826021, which is invalid:
Comment In response to this:
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. |
|
/bugzilla refresh |
|
@retroflexer: This pull request references Bugzilla bug 1826021, which is invalid:
Comment In response to this:
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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hexfusion, retroflexer, runcom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Adding valid-bug since the file is not present in 4.4+ so there is no backporting. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
@retroflexer: All pull requests linked via external trackers have merged: . Bugzilla bug 1826021 has been moved to the MODIFIED state. In response to this:
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. |
Closes: 1826021
- What I did
Fixed a problem with a greedy regular expression.
- How to verify it
Run restore on a master which is not the first one in the ETCD_INITIAL_CLUSTER. It should finish successfully.
- Description for the changelog
Current restore shell script results in an error "Error: snapshot restore requires exactly one argument" if the attempted master in not the first member listed in the ETCD_INITIAL_CLUSTER. This is due to a bug in the regular expression.