Release-note

Symptom:
show configuration failed misleads the configuration error. The actual error message was not shown.

Step:1 - (config)#call-home reporting anonymous
          - (config)#commit
Step:2 - (config)#call-home reporting anonymous http-proxy <i>WORD</i> port <i>65535</i>
 then we are seeing the below issue:

#conf t
Thu Jan 18 07:45:19.130 UTC
call-home reporting anonymous http-proxy WORD port 65535
(config)#call-home reporting anonymous http-proxy <i>WORD</i> port <i>65535</i>
(config)#commit
Thu Jan 18 07:45:22.202 UTC

% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
(config)#show configuration failed
Thu Jan 18 07:45:27.945 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.


call-home
service active
!!% Call-Home configuration failed: rejected as a previous request is rejected
http-proxy WORD port 65535
!!% Call-Home configuration failed: rejected as a previous request is rejected
profile CiscoTAC-1
  active
!!% Call-Home configuration failed: rejected as a previous request is rejected
  anonymous-reporting-only
!!% Call-Home configuration failed: rejected as a previous request is rejected
  reporting smart-call-home-data
!!% Call-Home configuration failed: rejected as a previous request is rejected
!
!

Conditions:
This problem occurs when the following configuration is failed and use show configuration failed to show the reason. 
Step:1 - (config)#call-home reporting anonymous
           - (config)#commit
Step:2 - (config)#call-home reporting anonymous http-proxy <i>WORD</i> port <i>65535</i>
Step:3 - (config)#commit
Step:4 - (config)#show configuration failed