Skip to content
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

Fix Calico setup for Centos nodes #459

Merged
merged 1 commit into from
Sep 18, 2020

Conversation

kashifest
Copy link
Member

In Centos based target clusters the following error were seen while deploying Cert Manager:

error creating core-only manager: Get "https://10.96.0.1:443/api?timeout=32s": dial tcp 10.96.0.1:443: i/o timeout

This was caused by Calico as described here

This PR fixes the problem as suggested in the Calico issue.

@metal3-io-bot metal3-io-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 17, 2020
@kashifest
Copy link
Member Author

/assign @maelk
/cc @fmuyassarov

@kashifest
Copy link
Member Author

/test-centos-integration
/test-integration

@kashifest
Copy link
Member Author

/cc @furkatgofurov7

Copy link
Member

@furkatgofurov7 furkatgofurov7 left a comment

Choose a reason for hiding this comment

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

Local tests running feature_tests in Centos has successfully passed after these 2 lines added to calico setup. Good job @kashifest !

lgtm

@furkatgofurov7
Copy link
Member

Outputs after the local tests:

[centos]$ kubectl get bmh -n metal3
+ kubectl get bmh -n metal3
NAME     STATUS   PROVISIONING STATUS   CONSUMER   BMC                                                                                         HARDWARE PROFILE   ONLINE   ERROR
node-0   OK       ready                            ipmi://192.168.111.1:6230                                                                   unknown            false    
node-1   OK       ready                            redfish+http://192.168.111.1:8000/redfish/v1/Systems/af9b9c10-8ac2-4d6c-8fa4-f828523ad31d   unknown            false    
node-2   OK       ready                            ipmi://192.168.111.1:6232                                                                   unknown            false    
node-3   OK       ready                            redfish+http://192.168.111.1:8000/redfish/v1/Systems/ce78f6b6-d1f2-48d0-b38b-914702c1b11d   unknown            false

@kashifest
Copy link
Member Author

Outputs after the local tests:

[centos]$ kubectl get bmh -n metal3
+ kubectl get bmh -n metal3
NAME     STATUS   PROVISIONING STATUS   CONSUMER   BMC                                                                                         HARDWARE PROFILE   ONLINE   ERROR
node-0   OK       ready                            ipmi://192.168.111.1:6230                                                                   unknown            false    
node-1   OK       ready                            redfish+http://192.168.111.1:8000/redfish/v1/Systems/af9b9c10-8ac2-4d6c-8fa4-f828523ad31d   unknown            false    
node-2   OK       ready                            ipmi://192.168.111.1:6232                                                                   unknown            false    
node-3   OK       ready                            redfish+http://192.168.111.1:8000/redfish/v1/Systems/ce78f6b6-d1f2-48d0-b38b-914702c1b11d   unknown            false

Thats great

Copy link
Member

@fmuyassarov fmuyassarov left a comment

Choose a reason for hiding this comment

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

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Sep 17, 2020
@furkatgofurov7
Copy link
Member

/test-centos-integration

@metal3-io-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kashifest, maelk

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 18, 2020
@metal3-io-bot metal3-io-bot merged commit d0a4198 into metal3-io:master Sep 18, 2020
@kashifest kashifest deleted the fix/calico-centos-kashif branch September 18, 2020 10:23
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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants