maas-cert-server

  1. Bug #1599171
  2. Comment #1

Comment 1 for bug 1599171

Revision history for this message
Jeff Lane  (bladernr) wrote : Re: It's possible that the curtin files are not being updated when the package updates, leading to stale config files that break deployments

Yeah, so this looks more like a procedural problem...

To replicate this I did the following:

Fresh trusty install in a VM
in the VM:
* add the hardware-cert PPA only
* modify the cert ppa .list to change trusty to utopic (to get an older version of m-c-s)
* sudo apt-get update
* sudo apt-get maas-cert-server

eventually got it all installed, or at least what I needed.
Checked /etc/maas/preseeds and found that curtin_userdata and curtin_userdata_custom were default
ran maniacs-setup
* had to move the preseed bit to the front, as this older m-c-s version breaks here due to some DNS problem that isn't germane to this.
* verified that maniacs setup DID create the -orig files and copied our versions to /etc/maas/preseed

So now, I have trusty, with maas, and with our preseeds via m-c-s (version 2.1.0 utopic)
Next, I corrected /etc/maas/source.list.d/hardware-certification.list and changed utopic back to trusty.

I then also added the maas/stable ppa to also grab the latest MAAS.

I did an update and upgrade and got the latest maas (1.9.3) and the latest m-c-s (2.20 trusty)

Then I rechecked and noted that the preseeds are not updated.

This only occurs manually.