-
Notifications
You must be signed in to change notification settings - Fork 110
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
Ensure ocp is reachable from ocpbm before deploying #2186
Conversation
Thanks for the PR! ❤️ |
1ae0913
to
ae249a1
Compare
ae249a1
to
8085350
Compare
This PR was successfully tested in a shift on stack deployment |
reproducer.yml
Outdated
when: | ||
- cifmw_deploy_architecture | default(false) | bool | ||
no_log: "{{ cifmw_nolog | default(true) | bool }}" | ||
async: "{{ 7200 + cifmw_test_operator_timeout|default(3600) }}" # 2h should be enough to deploy EDPM and rest for tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
async: "{{ 7200 + cifmw_test_operator_timeout|default(3600) }}" # 2h should be enough to deploy EDPM and rest for tests. | |
async: "{{ 7200 + cifmw_test_operator_timeout | default(3600) }}" # 2h should be enough to deploy EDPM and rest for tests. |
let's improve jinja spacing
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rebtoor 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 |
Since we now run the shifstack deployment using the reproducer by toggling `cifmw_deploy_architecture` we must ensure the iptables change we do is done before reaching the deployment step.
8085350
to
7e6d580
Compare
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/lgtm |
Since we now run the shifstack deployment using the reproducer by toggling
cifmw_deploy_architecture
we must ensure the iptables change we do is done before reaching the deployment step.As a pull request owner and reviewers, I checked that: