I havent been able to test this yet, but you can still use the 7.3 yumconf package, once installed, you will have the mwg-dist-upgrade and mwg-switch-repo commands available
yum install yumconf-7.3-mwg
mwg-dist-upgrade <version number>
I'll give it a shot on one my VM's and report back.
After running 'yum install yumconf-7.3-mwg' the 'mwg-dist-upgrade' command was available, but 'mwg-switch-repo' was not.
In any case you should run the mwg-dist-upgrade anyways.
Here is an example:
yum install yumconf-7.3-mwg worked
mwg-dist-upgrade 22.214.171.124 wasn't as successful
Towards the end of the process, this was reported:
Loaded plugins: changelog, downloadonly, fastestmirror
Determining fastest mirrors
http://appliance.webwasher.com/mwg/126.96.36.199/base/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "Couldn't resolve host 'appliance.webwasher.com'"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: mlos2. Please verify its path and try again
Error during upgrade, rolling back
Upgrade to MLOS 2 failed. Please examine
Checked named -- not running.
Attempted to start named and it failed to start with
kernel: named: segfault at 0 ip 00007f6ab7c89145 sp 00007fff4118f218 error 6 in libcrypto.so.1.0.1c[7f6ab7bc8000+1fb000]
Edited /etc/resolv.conf and pointed nameserver to a local (known working) namedserver.
Ran mwg-switch-repo and set it to 188.8.131.52:
mwg-switch-repo --sticky 184.108.40.206
Creating repository configuration for Sticky MWG 220.127.116.11 (release)
Repository configuration has been updated.
Now run "yum upgrade" to perform the actual upgrade.
Ran yum upgrade
Things seemed to go well, but post-upgrade I was no longer able to sudo.
Logged in via GUI -- at least one screen said 7.3.2.
Given the cumulative issues, despite the amount of pain it's going to cause, I'm now leaning toward doing a clean install of 7.4 for all of our MWG systems.