tracker issue : CF-4118887

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] Bug for: ColdFusion Archives not migrating many settings

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 02/17/2016

Components: Installation/Config

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: CF2016_Final / 298843

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Platforms All

Vote Count: 0

Listed in the version 2016.0.02.299200 Issues Fixed doc
Verification notes: verified_partially_fixed on July 09, 2020 using build 2016.0.02.299200 
ColdFusion Archives not migrating these settings:

Server Settings > Settings
- Default ScriptSrc Directory
- Allow REST Discovery

Server Settings > WebSocket
- Start Flash Policy Server

Server Settings > Document
- OpenOffice Directory

Data & Services
- I haven't yet tested all the settings in this section.

Debugging & Logging > Debug Output Settings
- Enable Performance Monitoring
- Enable Metrics Logging
- Metrics Frequency
- Enable CFSTAT

Debugger Settings
- Debugger Port

Security > RDS
- Enable RDS Service

Security > Sandbox Security
- Enable ColdFusion Sandbox Security

Security > Secure Profile
- Enable Secure Profile

Steps to reproduce:
1) Install CF2016 (tested as standalone w/ Developer profile)
2) Change all of the above settings from their defaults
3) Create a .car file of all settings
4) Uninstall CF2016 and reinstall CF2016 (tested as standalone w/ Developer profile)
5) Deploy the .car file created in step #3
6) See none of the above changed settings were migrated

Note: The Release Notes only say "Deploying a ColdFusion archive (.car) file on another instance of ColdFusion (2016 release) does not migrate the Allow REST Discovery setting." But, as you see, there are many more settings that aren't migrated.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4118887

External Customer Info:
External Company:  
External Customer Name: Aaron Neff
External Customer Email:

Attachments:

Comments:

The Release Notes should be updated to list all of the above settings as not being migrated by .car deploy. Customers will want to know that. Thanks!, -Aaron
Comment by External U.
4705 | February 17, 2016 05:37:22 PM GMT
Nikhil , Server Settings > Font Management -User defined Fonts This should also be migrated as we are allowing local files/installations (eg OO , RESTful webservice) to migrating . Logging
Comment by Nitin K.
4706 | April 29, 2016 06:42:17 AM GMT
Below are the list of additional settings migrating in CAR migration after applying HF2 to CF2016 ----------------------------------------------------- Server Settings > Settings - Default ScriptSrc Directory ->Should not be migrated . This is expected behavior . - Allow REST Discovery -> Migrating Now Server Settings > WebSocket - Start Flash Policy Server -> Migrating Now -Enable WebSocket Service >Use Proxy -> Migrating Now Server Settings > Mail - Allow downloading the attachments for undelivered emails. -> Migrating now Server Settings > Document - OpenOffice Directory -> Migrating Now - Remote OpenOffice >Port -> Migrating Now - Remote OpenOffice >Hostname -> Migrating Now Debugging & Logging > Debug Output Settings - Enable Performance Monitoring -> Migrating Now - Enable Metrics Logging ->Migrating Now - Metrics Frequency ->Migrating Now - Enable CFSTAT -> Migrating Now Debugger Settings - Debugger Port -> Migrating Now Security > RDS - Enable RDS Service -> Expected Behavior . Should not be migrated Security > Sandbox Security - Enable ColdFusion Sandbox Security ->Expected Behavior . Should not be migrated . Security > Secure Profile - Enable Secure Profile -> Expected Behavior . Should not be migrated . Reason: As it adds a lot of restriction in server functionality . -------------------------------------------------- Note: Corba settings should not be migrated . For User defined fonts , a separate bug is logged targeted to CF13 . Secure Default Value in secure profile should not be migrated . --------------------------------------------------- The above mentioned settings will be taken care of in CAR migration(or CAR creation) of CF11 & CF10 as well . Separate bugs are logged for the same and is expected to be fixed in their latest HF
Comment by Nitin K.
4707 | May 10, 2016 12:38:13 AM GMT
Hi Nitin, Thank you *very much* for outlining which settings will/won't be migrated. Would you please consider the following?: Unless notified otherwise, users will expect all settings to be migrated. Thus, users should be notified of which settings won't be migrated. The notification, listing which settings won't be migrated, should be displayed 1) during CAR Creation and 2) during CAR Deploy. Should I log a separate ticket? Thanks!, -Aaron
Comment by External U.
4708 | May 10, 2016 01:36:21 AM GMT
I have logged a bug(#CF-4150663) for this . Once the bug is fixed ,the user will be able to view the list of settings being ignored while creation and deployment of CAR . This is expected to be merged in HF2 . Thanks for pointing it out .
Comment by Nitin K.
4709 | May 10, 2016 04:00:31 AM GMT
Now list of settings not getting migrated can be seen in Archive summary (under Settings Never Migrated) at the time of ColdFusion Archive creation as well as Deployment .
Comment by Nitin K.
4710 | May 12, 2016 05:32:50 AM GMT
I've added the list to the documentation as well as the release notes.
Comment by Saurav G.
4711 | May 13, 2016 03:22:00 AM GMT
Hi Nitin and Saurav, Awesome, thanks very much! I still don't understand why the security settings (RDS/Sandbox/Secure Profile) won't be migrated. Would someone please be able to explain the reason a little more? Thanks!, -Aaron
Comment by External U.
4712 | May 13, 2016 11:26:27 AM GMT
Example scenario: 1) Customer has CF11 installed and wants to upgrade to CF2016. 2) Customer creates .car file of all settings in CF11. 3) Customer installs CF2016. 4) Customer deploys .car file of all settings into CF2016. Why would customer not want security settings migrated? If there is risk, then same type of warning could be displayed as when selecting to migrate JVM settings. Thanks!, -Aaron
Comment by External U.
4713 | May 13, 2016 11:29:56 AM GMT
*bump* - I received notification that this ticket was updated, yet my questions above remain unanswered. Steps: 1) On Server 1, enable Sandbox Security & Secure Profile 2) On Server 1, create .car of all settings 3) On Server 2, deploy .car created in Step 2 Expected Result: Step #3 should cause Sandbox Security & Secure Profile to become enabled (if they weren't already) on Server 2 (regardless of which profile was selected during Server 2's installation). Could someone please confirm this ticket's fix resolved that issue? B/c, per Nitin's comment on 05/10/2016 00:38:13 GMT, it appears Adobe feels those 2 settings "Should not be migrated". Which, seems wrong IMO. If Adobe feels that way, could they please clarify reasoning? Thanks!, -Aaron
Comment by Aaron N.
4714 | September 21, 2017 04:58:48 AM GMT