| 2024-01-08 18:48:24 |
Mohaseenkhan |
summary |
Hi all, I have hit a dead end. whenever i try to add machines or deploy applications using juju. The controller machines fails to get published images meta data. It keeps on pointing to link1. this url is not accessible anymore. The installation use to work well but after Jan 1 2024 things have changes it does not works they way it was working. I am trying install juju applications of LXD cluster link 1 http://cloud-images.ubuntu.com/releases/streams/v1/index2.sjson link 2 https://cloud-images.ubuntu.com/releases/ LXD version Client version: 5.19 Server version: 5.19 JUJU version’ 3.3.0-genericlinux-amd64 (tried on the classic 3.1.7 it dod not work either) OS Jammy 22.04 Solns tried: Hosted my own meta data internal site with pache2 it skips and defaults to link1 Changed juju version—same error Tried with Ubuntu 20.04—same error Boostraped the controller with link2 —same error error 4-01-05 23:44:14 WARNING juju.worker.proxyupdater proxyupdater.go:297 unable to update apt mirrors: exit status 1, output: “” 2024-01-05 23:44:48 INFO juju.worker.logforwarder logforwarder.go:105 config change - log forwarding not enabled 2024-01-05 23:44:48 INFO juju.worker.upgrader upgrader.go:166 desired agent binary version: 3.3.0 2024-01-05 23:49:29 INFO juju.state addmachine.go:506 new machine “1” has preferred addresses: private “”, public “” 2024-01-05 23:50:30 WARNING juju.environs.simplestreams datasource.go:212 Got error requesting “link1”: Get “link1”: dial tcp 185.125.190.40:80: i/o timeout 2024-01-05 23:51:01 WARNING juju.environs.simplestreams datasource.go:212 Got error requesting “link1”: Get “link1”: dial tcp 185.125.190.37:80: i/o timeout 2024-01-05 23:51:33 WARNING juju.environs.simplestreams datasource.go:212 Got error requesting “link1”: Get “link1”: dial tcp 185.125.190.40:80: i/o timeout |
Juju Controller keeps picking wrong meta data url during app deployment when used the right url on the model it skips without debug logs. |
|
