Updated node-script not showing in UI

[Nick Niehoff]

If you create and update a node-script via the CLI the CLI read and download both reflect the correct version history and the latest version. However if you then check the UI the contents of the script are the first version of the script.

Reproducing:

1. Create a node script as a text file script.sh
2. Use the CLI to create the node-script:

maas admin node-scripts create name=testingscript script@=/path/to/script.sh type=testing

3. Change the script.sh file
4. Use the CLI to update the script:

maas admin node-script update testingscript script@=/path/to/script.sh

5. Verify with the CLI:

maas admin node-script download testingscript

You should see your modified script from step 3

6. Verify history with CLI:

maas admin node-script read testingscript

You should see 2 history entries

7. Check the UI:

Under Settings/Scripts/Testing Scripts you should see your testingscript listed, select the script to view the contents. Note the contents are the original contents from step 1 not the updated contents from step 3

[Lee Trager (ltrager)]

The backend does have a database trigger which should be updating the UI. Tagging this UI for the design team to look into.

One thing to note is that even if the data doesn't update in the UI if you run commissioning/testing the right version will be used as its been committed to the database.