Skip to content

openstack: Use CI DNS server to resolve API URL#3236

Merged
openshift-merge-robot merged 2 commits intoopenshift:masterfrom
trown:openstack-ci
Apr 2, 2019
Merged

openstack: Use CI DNS server to resolve API URL#3236
openshift-merge-robot merged 2 commits intoopenshift:masterfrom
trown:openstack-ci

Conversation

@trown
Copy link

@trown trown commented Mar 26, 2019

We need to use a DNS server we control in order to resolve the API
URL. This server is now setup in the CI tenant, and allows posting
A records in the shiftstack.ci domain.

This requires a special CI image with the openstackclient installed:
openshift/installer#1466

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 26, 2019
@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 27, 2019
@trown trown changed the title openstack: WIP: Use CI DNS server to resolve API URL openstack: Use CI DNS server to resolve API URL Mar 29, 2019
@trown
Copy link
Author

trown commented Apr 1, 2019

openshift/installer#1466 merged. If the openstack rehearse job gets to the point where a FIP is pulled this should be good to go.

@trown
Copy link
Author

trown commented Apr 1, 2019

/test pj-rehearse

@trown
Copy link
Author

trown commented Apr 2, 2019

This (grep "failed to initialize the cluster") failed in the same way the install currently fails for me manually. I think we should go ahead and merge this, as it gives us concurrent working (in terms of accuracy) CI jobs. We can then add fixes in smaller follow-up PRs.

Copy link
Contributor

@tomassedovic tomassedovic left a comment

Choose a reason for hiding this comment

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

Looks good to me, but I'd like to check the floating IP creation and assignment bit actually does what it's supposed to.

Copy link
Contributor

Choose a reason for hiding this comment

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

This can be written as: openstack floating ip list -f value -c 'Floating IP Address', which I'd say is cleaner and more robust (the default view is not really supposed to be used by scripts and can change).

More importantly though, won't this fail if there's another job running already? There will be a floating IP in that case, but it will be in use so we shouldn't be taking it.

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Author

Choose a reason for hiding this comment

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

Yes it is missing the --status DOWN check. Nice catch. I will also fix the awks.

We need to use a DNS server we control in order to resolve the API
URL. This server is now setup in the CI tenant, and allows posting
A records in the shiftstack.ci domain.
@tomassedovic
Copy link
Contributor

Thanks! That looks good to me. Let's see what the e2e-openstack job says.

Out of curiosity, how does the LOCAL_IMAGE_OPENSTACK_INSTALLER variable get set?

@tomassedovic
Copy link
Contributor

/approve
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tomassedovic, trown

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:

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 2, 2019
@openshift-merge-robot openshift-merge-robot merged commit ba9c361 into openshift:master Apr 2, 2019
@openshift-ci-robot
Copy link
Contributor

@trown: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/rehearse/openshift/installer/master/e2e-openstack 345fb50 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws 345fb50 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-rhel-scaleup 345fb50 link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-libvirt 345fb50 link /test pj-rehearse
ci/prow/pj-rehearse 345fb50 link /test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants