yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1857468@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

During the maas-enlisting-node phase, cloud init tries to run an 'apt-
get update' and it fails because of an error as given below:

2019-12-18T06:08:39+00:00 maas-enlisting-node cloud-init[2655]: Get:4 http://<repo_name>/ubuntu bionic-security InRelease [10.1 kB]
2019-12-18T06:08:39+00:00 maas-enlisting-node cloud-init[2655]: Err:5 http://<repo_name>/ubuntu bionic-backports Release
2019-12-18T06:08:39+00:00 maas-enlisting-node cloud-init[2655]:   404  Not Found [IP: 32.68.226.74 80]
2019-12-18T06:08:40+00:00 maas-enlisting-node cloud-init[2655]: Reading package lists...
2019-12-18T06:08:40+00:00 maas-enlisting-node cloud-init[2655]: E: The repository 'http://<repo_name>/ubuntu bionic-backports Release' does not have a Release file.
2019-12-18T06:08:40+00:00 maas-enlisting-node cloud-init[2655]: E: Repository 'http://<repo_name>/ubuntu bionic InRelease' changed its 'Label' value from 'Ubuntu' to 'ubuntu bionic'
2019-12-18T06:08:40+00:00 maas-enlisting-node cloud-init[2655]: E: Repository 'http://<repo_name>/ubuntu bionic-updates InRelease' changed its 'Label' value from 'Ubuntu' to 'ubuntu bionic-updates'
2019-12-18T06:08:40+00:00 maas-enlisting-node cloud-init[2655]: E: Repository 'http://<repo_name>/ubuntu bionic-updates InRelease' changed its 'Codename' value from 'bionic' to 'bionic-updates'
2019-12-18T06:08:40+00:00 maas-enlisting-node cloud-init[2655]: E: Repository 'http://<repo_name>/ubuntu bionic-security InRelease' changed its 'Label' value from 'Ubuntu' to 'ubuntu bionic-security'
2019-12-18T06:08:40+00:00 maas-enlisting-node cloud-init[2655]: E: Repository 'http://<repo_name>/ubuntu bionic-security InRelease' changed its 'Codename' value from 'bionic' to 'bionic-security'


apt has an option to to ignore this error by providing a parameter -"--allow-releaseinfo-change", however I am unable to set this parameter in maas. Is there a place in the code or in the cloud init phase where we can set this option to avoid the above error? If not then would it make sense to add such functionality?

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
Unable to set Apt config parameter during maas-enlisting-node phase
https://bugs.launchpad.net/bugs/1857468
You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init.