[POOL_UPGRADE] Transactions missing from config ledger after upgrade

After upgrading the STN to 1.1.33, the expected transactions are not being posted in the config ledger.  In addition to failed upgrades, I would expect to see upgrade successes.  Successes are not being recorded in the ledger.

The upgrade transaction used is:

send POOL_UPGRADE name=STNUpgrade20170831 version=1.1.33 sha256=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 action=start schedule=
{'UZH61eLH3JokEwjMWQoCMwB3PMD6zRBvG6NCv5yVwXz':'2017-08-31T11:05:05.555000-06:00','2MHGDD2XpRJohQzsXu4FAANcmdypfNdpcqRbqnhkQsCq':'2017-08-31T11:05:05.555000-06:00',
'8NZ6tbcPN2NVvf2fVhZWqU11XModNudhbe15JSctCXab':'2017-08-31T11:05:05.555000-06:00','DNuLANU7f1QvW1esN3Sv9Eap9j14QuLiPeYzf28Nub4W':'2017-08-31T11:05:05.555000-06:00',
'HCNuqUoXuK9GXGd2EULPaiMso2pJnxR6fCZpmRYbc7vM':'2017-08-31T11:05:05.555000-06:00','Dh99uW8jSNRBiRQ4JEMpGmJYvzmF35E6ibnmAAf7tbk8':'2017-08-31T11:05:05.555000-06:00',
'EoGRm7eRADtHJRThMCrBXMUM2FpPRML19tNxDAG8YTP8':'2017-08-31T11:05:05.555000-06:00','2VMDBjJCqxEonfaTcwvyBy5J473H2u65ZqQhPHx47iDG':'2017-08-31T11:05:05.555000-06:00'}
timeout=20 force=True

It appears that one node failed to upgrade properly.  The others upgraded fine.  After the upgrade, using "sudo read_ledger --type config" command, I get:

[1,\{"action":"start","force":false,"identifier":"6feBTywcmJUriqqnGc1zSJ","justification":null,"name":"STNUpgrade2","reqId":1501781257520465,"schedule":\{"2MHGDD2XpRJohQzsXu4FAANcmdypfNdpcqRbqnhkQsCq":"2017-08-03T17:30:33.555000+00:00","8NZ6tbcPN2NVvf2fVhZWqU11XModNudhbe15JSctCXab":"2017-08-03T17:35:33.555000+00:00","DNuLANU7f1QvW1esN3Sv9Eap9j14QuLiPeYzf28Nub4W":"2017-08-03T17:40:33.555000+00:00","Dh99uW8jSNRBiRQ4JEMpGmJYvzmF35E6ibnmAAf7tbk8":"2017-08-03T17:50:33.555000+00:00","EoGRm7eRADtHJRThMCrBXMUM2FpPRML19tNxDAG8YTP8":"2017-08-03T17:55:33.555000+00:00","HCNuqUoXuK9GXGd2EULPaiMso2pJnxR6fCZpmRYbc7vM":"2017-08-03T17:45:33.555000+00:00","UZH61eLH3JokEwjMWQoCMwB3PMD6zRBvG6NCv5yVwXz":"2017-08-03T18:00:33.555000+00:00"},"sha256":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","signature":"4h7mGrZE2JzjLY39ifnhNcyLpKbzXe1RgXrPmmqCJopEUPv6vsSmbk9p2XMkuZ4oij6kAWak6mpqpYCedv3gKJq9","timeout":10,"txnTime":1501781257,"type":"109","version":"1.0.3"}]
[2,\{"action":"start","force":true,"identifier":"6feBTywcmJUriqqnGc1zSJ","justification":null,"name":"STNUpgrade20170831","reqId":1504197853027234,"schedule":\{"2MHGDD2XpRJohQzsXu4FAANcmdypfNdpcqRbqnhkQsCq":"2017-08-31T11:05:05.555000-06:00","2VMDBjJCqxEonfaTcwvyBy5J473H2u65ZqQhPHx47iDG":"2017-08-31T11:05:05.555000-06:00","8NZ6tbcPN2NVvf2fVhZWqU11XModNudhbe15JSctCXab":"2017-08-31T11:05:05.555000-06:00","DNuLANU7f1QvW1esN3Sv9Eap9j14QuLiPeYzf28Nub4W":"2017-08-31T11:05:05.555000-06:00","Dh99uW8jSNRBiRQ4JEMpGmJYvzmF35E6ibnmAAf7tbk8":"2017-08-31T11:05:05.555000-06:00","EoGRm7eRADtHJRThMCrBXMUM2FpPRML19tNxDAG8YTP8":"2017-08-31T11:05:05.555000-06:00","HCNuqUoXuK9GXGd2EULPaiMso2pJnxR6fCZpmRYbc7vM":"2017-08-31T11:05:05.555000-06:00","UZH61eLH3JokEwjMWQoCMwB3PMD6zRBvG6NCv5yVwXz":"2017-08-31T11:05:05.555000-06:00"},"sha256":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","signature":"rmQirALnJJw6ziQa8zchH4mCzB3xFZN129HxLQ13acsJwcuvZs5BJXR952zdtNcngiHe7bRdNhAp6cwsDnHUgrK","timeout":20,"txnTime":1504197853,"type":"109","version":"1.1.33"}]
[3,\{"data":\{"action":"fail","version":"1.1.33"},"identifier":"2VMDBjJCqxEonfaTcwvyBy5J473H2u65ZqQhPHx47iDG","reqId":1504199153876348,"signature":"27w2iRrT34AUQcmbAdPhhoPvJ7iMMN2S3VkDBCjDHdsrJUcwaC3bhX8fD3Rd9SHXWKdgcw2oYJNFEXzVNisxX4wz","txnTime":1504199195,"type":"110"}]

In previous versions of sovrin, both successes and failures to upgrade were recorded on the config ledger. I would expect this to remain the case.