juju add-machine gives missing CentOS-base repo

What happened to this?

Den ons 23 sep. 2020 20:15Pete Vander Giessen <email address hidden>
skrev:

> ** Changed in: juju
> Milestone: 2.8.4 => None
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1850952
>
> Title:
> juju add-machine gives missing CentOS-base repo
>
> Status in juju:
> Triaged
>
> Bug description:
> I'm getting an error when I try to add a centos machine to a juju
> model as:
>
> juju add-machine ssh:<email address hidden>
> Logging to /var/log/cloud-init-output.log on the bootstrap machine
> Installing curl, bridge-utils, cloud-utils, nmap-ncat, tmux
> Changing package mirror does not yet work on CentOS
> sed: can't read /etc/yum/repos.d/CentOS-Base.repo: No such file or
> directory
> ERROR provisioning failed, removing machine 97: subprocess encountered
> error code 1
> ERROR subprocess encountered error code 1
>
> After manually creating the file as:
> juju ssh <email address hidden>
> mkdir -p /etc/yum/repos.d/
> touch CentOS-Base.repo
>
> ... then the juju agent installs fine as:
>
> juju add-machine ssh:<email address hidden>
> created machine 98
>
> Getting juju to work better on centos is a good thing =)
>
>
> # Versions etc. below
>
> [centos@actual-moth ~]$ cat /etc/redhat-release
> CentOS Linux release 7.6.1810 (Core)
>
> juju --version
> 2.6.10-bionic-amd64
>
>
> agent binaries from
> https://10.104.131.3:17070/model/93c6e589-bfc4-4d4c-8913-aca9d0c110dd/tools/2.6.5-centos7-amd64
> downloaded: HTTP 200; time 11.635s; size 47941071 bytes; speed 4120475.000
> bytes/s Agent binaries downloaded successfully.
> bb04c23df58d0eea986edeeedf5e2e4ac818e5189d977da57c3b32e4bc403e91
> /var/lib/juju/tools/2.6.5-centos7-amd64/tools.tar.gz
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1850952/+subscriptions
>

@erik-lonroth it's still something that we want to get done, but it kept getting bumped from milestone to milestone, without action.

I'm working on getting a better handle on our bug backlog, and part of that is giving more meaning to a bug being attached to a milestone, along with developing some strategies to work through our backlog.

So, basically, juju should make use of the model config for configuring yum. Perhaps with a
 config variable: "yum-mirror" which is set on the controller level?

juju has the apt-mirror config already, which is apparently used in this context. I would like to see this for centos also since we would like to use this with centos.

Attribute From Value
agent-metadata-url default ""
agent-stream default released
agent-version model 2.8.1
apt-ftp-proxy default ""
apt-http-proxy default ""
apt-https-proxy default ""
apt-mirror controller https://apt-mirror.example.com/artifactory/ubuntu
apt-no-proxy default ""
automatically-retry-hooks default true
backup-dir default ""
cloudinit-userdata default ""
container-image-metadata-url default ""
container-image-stream default released
container-inherit-properties default ""

Agree that we should add a yum-proxy element.

Or, better yet, replace apt-proxy with something generic like package-manager-proxy (or even package-manager-proxies, in order to accommodate a list that would be able to accept a snap store proxy, an apt proxy, a yum proxy, a flatpak proxy, etc in one command).

Here is a great resource on how to move with this

https://discourse.charmhub.io/t/tutorial-how-to-deploy-centos7-images-on-vmwares-vsphere-using-juju/3792/3

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.