-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
upgrade: Verify required network items are set #5256
Conversation
aos-ci-test |
@sdodson It looks like everything actually passed by looking at the logs ... 😕 |
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. Error message is helpful, I love when software tells me more than just 'it went bad, something with a variable...'
osm_cluster_network_cidr and openshift_portal_net are required inventory variables when upgrading. | ||
These variables should match what is currently used in the cluster. If you don't remember what | ||
these values are you can find them in /etc/origin/master/master-config.yaml on a master with the names | ||
clusterNetworkCIDR(osm_cluster_network_cidr) and hostSubnetLength (openshift_portal_net). |
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.
I'll approve it because it fixes the bug. I think it could be improved though for extra help-a-user-out value. Another task or play or something that fetched those values from a master so they didn't have to search them out themselves. I won't block on it, that might be excessive work, it's just something I thought of.
[merge] |
[test]ing while waiting on the merge queue |
Failing on elastic search. |
aos-ci-test |
Hrm, hitting the same thing again...
|
Rebasing just in case ... |
aos-ci-test |
👍 good failure. Now to figure out how to get CI to add these variables for upgrade testing ...
|
When upgrading osm_cluster_network_cidr, osm_host_subnet_length, and openshift_portal_net must be set to avoid SDN initialization errors. This was found when the default parameters were changed between Openshift versions. This meant users who upgraded and did not specify either mentioned variable at install/upgrade time ended up getting SDN errors post upgrade. When osm_cluster_network_cidr, osm_host_subnet_length, and openshift_portal_net are not set the upgrade will fail telling the user that the variables must be set and how to find the current values in the current install. References: openshift@b50b4ea Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1451023
Evaluated for openshift ansible merge up to 10ecef4 |
[test] |
continuous-integration/openshift-jenkins/merge FAILURE (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_openshift_ansible/1003/) (Base Commit: 756ab33) (PR Branch Commit: 10ecef4) |
I'm guessing either the change didn't make it to the CI servers yet OR the test kicked off before the change became available. |
aos-ci-test |
Test only failed on job ordering, when aos-ci-test comes back green i'll merge. |
Unrelated to this change:
|
aos-ci-test |
Different missing image 😦
|
lets assume that's a temporary issue, lets see what [test] says |
Evaluated for openshift ansible test up to 10ecef4 |
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_openshift_ansible/636/) (Base Commit: 69f0384) (PR Branch Commit: 10ecef4) |
When upgrading
osm_cluster_network_cidr
,osm_host_subnet_length
, andopenshift_portal_net
must be set to avoid SDN initialization errors.This was found when the default parameters were changed between Openshift
versions. This meant users who upgraded and did not specify either
mentioned variable at install/upgrade time ended up getting SDN errors
post upgrade.
When
osm_cluster_network_cidr
,osm_host_subnet_length
, andopenshift_portal_net
are not set the upgrade will fail telling the userthat the variables must be set and how to find the current values in the
current install.
References: b50b4ea
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1451023