Ah, I was upgrading OpenShift enterprise, which apparently is still at 3.7.46.
Thanks Gary Franczyk Unix Administrator, Expert, Infrastructure Availity | 10752 Deerwood Park Blvd S. Ste 110, Jacksonville FL 32256 W 904.470.4953 | M 561.313.2866 [email protected]<mailto:[email protected]> From: Scott Dodson <[email protected]> Date: Tuesday, May 22, 2018 at 2:42 PM To: Gary Franczyk <[email protected]> Cc: "[email protected]" <[email protected]> Subject: [EXTERNAL] Re: Upgrade bug from 3.6 to 3.7 WARNING: This email originated outside of the Availity email system. DO NOT CLICK links or open attachments unless you recognize the sender and know the content is safe. ________________________________ This was fixed recently, can you confirm it's fixed? It should be in openshift-ansible-3.7.48-1 or the latest release-3.7 branch of a github checkout. https://github.com/openshift/openshift-ansible/pull/8311<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openshift_openshift-2Dansible_pull_8311&d=DwMFaQ&c=OICO5LaDH-Xi2CSZAJgmTQ&r=DWo_ijwFGqBf00dIEKrMRiq5JjUOT-29YI7Con8CGIc&m=6Yo1ffOqAky2Xl1Q2OjQyZ28zJ3GmmfDhVr45zbdM6A&s=ZPD8B6E3ZBoPVb-mGvycdgWyWpz4CTUpZplCA0D8zGw&e=> https://bugzilla.redhat.com/show_bug.cgi?id=1573827<https://urldefense.proofpoint.com/v2/url?u=https-3A__bugzilla.redhat.com_show-5Fbug.cgi-3Fid-3D1573827&d=DwMFaQ&c=OICO5LaDH-Xi2CSZAJgmTQ&r=DWo_ijwFGqBf00dIEKrMRiq5JjUOT-29YI7Con8CGIc&m=6Yo1ffOqAky2Xl1Q2OjQyZ28zJ3GmmfDhVr45zbdM6A&s=x3ODmKkUjsNlPyqMMvhzcxrOBDVRZPBxmkVndwga1Js&e=> On Tue, May 22, 2018 at 12:44 PM, Gary Franczyk <[email protected]<mailto:[email protected]>> wrote: I’ve discovered what I believe is a bug when upgrading from 3.6 to 3.7. There is a file that creates the components for the API Aggregator in the install scripts that does not get called during separate control-plane and node upgrades. The file is: /usr/share/ansible/openshift-ansible/playbooks/common/openshift-master/tasks/wire_aggregator.yml It does not get called in the upgrade_control_plane.yml or the upgrade_nodes.yml playbooks, but is called in the upgrade.yml file. In addition, the only time it is run is when there are hosts listed in the “oo_masters_to_config”, which is only before they are upgraded. This means that if you try to run the upgrade.yml afterward, it does not apply these changes. Perhaps I this list can notify someone that can correct this. Gary Franczyk Unix Administrator, Expert, Infrastructure ________________________________ The information contained in this e-mail may be privileged and confidential under applicable law. It is intended solely for the use of the person or firm named above. If the reader of this e-mail is not the intended recipient, please notify us immediately by returning the e-mail to the originating e-mail address. Availity, LLC is not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Availity, LLC. _______________________________________________ users mailing list [email protected]<mailto:[email protected]> http://lists.openshift.redhat.com/openshiftmm/listinfo/users<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openshift.redhat.com_openshiftmm_listinfo_users&d=DwMFaQ&c=OICO5LaDH-Xi2CSZAJgmTQ&r=DWo_ijwFGqBf00dIEKrMRiq5JjUOT-29YI7Con8CGIc&m=6Yo1ffOqAky2Xl1Q2OjQyZ28zJ3GmmfDhVr45zbdM6A&s=kPKDSbpx1e8G9igTHYW_0UYmKbIfmWe0eHCuCcXIt5w&e=>
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
