Follow

Hotfixes / Updates

From time to time an issue may emerge for which we will provide a hotfix. This article lists the available hotfixes that we believe are of interest to our customers who host SD Elements onsite.

Release 4.2 (4.2.21 and prior)

We fixed an error that impacts ALM sync jobs. The mechanism can hit a permission error depending on who triggers a job.

If you deployed version 4.2 prior to December 1, 2016 you can either:

1. Hotfix your SD Elements by replacing the permissions.py module (directions below)

2. Update to the latest build of 4.2

If you haven't deployed version 4.2 this issue will not affect you since they have been fixed and deployed in the latest available build of version 4.2

Hotfix Steps

Contact SD Elements support (support@sdelements.com) for the updated permissions.py file. Log in to the SD Elements command-line. Run the following:

umask 0002
cp permissions.py /docs/sde/live/code/sigma/apiv2/permissions.py
sde apache restart
sde supervisor restart all

The server will restart with less than a minute of downtime.

Release 4.1

We fixed an error that impacts ALM sync jobs. The mechanism can hit a permission error depending on who triggers a job.

If you deployed version 4.1 you can hotfix your SD Elements by replacing the permissions.py module (directions below)

If you haven't deployed version 4.1 this issue will not affect you since they have been fixed and deployed in the latest available build of version 4.2

Hotfix Steps

Contact SD Elements support (support@sdelements.com) for the updated permissions.py file. Log in to the SD Elements command-line. Run the following:

umask 0002
cp permissions.py /docs/sde/live/code/sigma/apiv2/permissions.py
sde apache restart
sde supervisor restart all

The server will restart with less than a minute of downtime.

Release 3.3 (3.3.29 and prior)

We fixed an error that impacts certain ALM and Scanner import jobs. The mechanism can hit a permission error depending on who triggers a job.

If you deployed version 3.3 prior to December 1, 2015 you can either:

1. Hotfix your SD Elements by replacing the integrations.py module (directions below)

2. Update to the latest build of 3.3

If you haven't deployed version 3.3 this issues will not affect you since they have been fixed and deployed in the latest available build of version 3.3

Hotfix Steps

Contact SD Elements support (support@sdelements.com) for the updated integrations.py file. Log in to the SD Elements command-line. Run the following:

umask 0002
cp integrations.py /docs/sde/live/code/sigma/applications/models/integrations.py
touch /docs/sde/live/code/sigma/deployment/*wsgi

The server will restart with less than a minute of downtime.

Release 3.3 (3.3.28 and prior)

We fixed an error that impacts on-going ALM and Scanner import jobs. The cron script almsync.py that runs the sync and imports does not run as expected and can fail.

If you deployed version 3.3 prior to November 16, 2015 you can either:

1. Hotfix your SD Elements by replacing the almsync.py script (directions below)

2. Update to the latest build of 3.3

If you haven't deployed version 3.3 these two issues will not affect you since they have been fixed and deployed in the latest available build of version 3.3

Hotfix Steps

Contact SD Elements support (support@sdelements.com) for the updated almsync.py. Log in to the SD Elements command-line. Copy almsync.py to:

/docs/sde/live/code/sigma/applications/management/commands/almsync.py

You don't need to restart the server. The next time the cron job triggers it will run the new updated script.

Release 3.3 (3.3.27 and prior)

We have identified and fixed three issues in version 3.3 which affect our AppScan Enterprise and Jira integration capability. Specifically the two bugs fixed are:

  • Certain AppScan Enterprise reports do not successfully import (internal identifier SDE-1898)
  • Syncing SD Elements tasks to Jira sub-task issues can result in an error (internal identifier SDE-1826)

If you deployed version 3.3 prior to October 28, 2015 and are affected by these two issues, you can either hotfix your SD Elements or update to the latest build of 3.3. Hotfix steps are provided below.

If you haven't deployed version 3.3 yet these two issues will not affect you since they have been fixed and deployed in the latest available build of version 3.3

Hotfix Steps

After logging in to the SD Elements command-line, the following steps will apply the fix:

umask 0022
source /docs/sde/live/env/bin/activate
/docs/sde/live/env/bin/pip install sdetools==4.8.4
sde supervisor restart all
sde apache restart
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments