Punnycode conversion of international domain name is returning
unexpected output on solaris 11 x86. This is causing test
failure in SCX SSL certificate test.
Disabling the test so that build can go through.
When upgrading from 2012 R2 to latest scx omikey ownership
is not getting updated to omi:omi. Due to this omi is not
able to read the key file, hence port 1270 is getting closed.
To address this scxsslconfig is updated to check and update
omikey ownership if key file alreday exists.
JBoss standalone mode allows multiple instances to run using same
Jboss home dir. To support this Key and Diskpath is set to the
complete configuration file used for the instance.
Also same configuration file can be used for different instances
by giving diffrenet port offset. The code is updated to check
for port offset in command line parameters. If present it will
be appended to Key and Diskpath to uniquely identify the instance.
JBoss does not mandate that standalone should be a directory in
configuration path. Updated the agent to pass detected deployment type
from appserver enumeration to JBoss instance. Value of deployment type
will be used to determine if it is an JBoss standalone instance.
While upgrading omsagent, azure linux extension calls --remove
followed by --install, instead of directly calling --upgrade.
This sequence wascausing port 1270 to close as we close the
port on uninstall and do not open it by default on install.
To support this scenario we will now check if port 1270 is
open at uninstall. If yes we will create a marker file in
scx conf directory. On install if the marker file is present
then port 1270 will be opened.
As marker file is created in scx conf directory, it will get
deleted in --purge call.
Uninstall script should be used remove packages
during upgrade failure recovery. Since scx and
omi have to be forcibly removed, uninstall script
is updated to accept force parameter.
Also if uninstall script is not present then install
check will not be performed before removing the scx
and omi packages.
SCOM CB release will ship omsagent bundle instead of scx bundle on
Linux platform. SCOM console needs to report omsagent version as
the installed agent version.
kitVersionString's value in SCX_Agent enumeration is shown in SCOM
console. Change is made to check if omsagent install info file is
present or not. If present it will be parsed to get the value of
install version and install time. If not scx install info file
will continue to be used.
This change is only for SCOM CB release. 2016 UR's will remain
on current implementation.
To check whether a websphere is still installed, presence
of file wsBundleMetadata is checked. At least on websphere
8.5.x wsBundleMetadata is a directory.
Updated the method to check for the presence of directory.
Also did not remove the file check to avoid any backward
compatibility issues.
Shell bundles were downgrading installed packages during upgarde/install.
Added version checks on during upgarde in unix platforms.
Added installed omi version check during install on all platforms.
Fix Omiserver is still running under /opt/microsoft/scx/bin/
after upgrading OM agent from 2012 to 2016, Fix is to stop
the 2012 scx agent before upgrading it to 2016
scx will no longer build omi packages. Instead it will
take the omi packages from the omi-kits repo where omi
team will check in latest certified omi packages for all
platforms.
scx partners (omagent, azure) does not need port 1270
to be opened. We have introduced various mechanism through
which they can disable port 1270. But now we are disabling
port 1270 by default and have added a flag --enable-opsmgr
that needs to be passed to shell bundle if the installation
is expected to work with opsmgr.
Previously, we used a "install all packages as a list" (commit hash 6a0acc1)
to shake an upgrade bug from kit -240 to later. But this didn't pan out
consistently. So now if upgrade fails for some reason then remove underlying
packages and reinstall them (forcing removal in case of dependencies).
This seems to work reliably on both rpm and dpkg systems.
Commit hash 0921ef7 (back in 2013) incorporated a memory leak of the
SCXThread object. This was "fixed" in f004d08, which was supposed to
roll back other changes to the SCX_OperatingSystem_Class_Provider.cxx
and then fix the bug.
However, it turns out that the fixes never made it past the rollback.
This commit fixes those leaks for real.
Saroj Patra
Vishal Mishra
John Liu
Jeff Coffler
Nirbhay Singh
Nicolas Roy
Steve Weber