Public bug reported:
MAAS Version 2.1.5+bzr5596-0ubuntu1 (16.04.1)
Juju version: 2.0.2-xenial-amd64
MAAS cloud YAML:
clouds:
devmaas:
type: maas
auth-types: [oauth1]
endpoint: http://192.168.8.1:5240/MAAS
where 192.168.8.1 is the MAAS server. All nodes are on a dedicated
subnet 192.168.8.x, with 8.1 acting as a router to the internet. I have
provisioned centos node using MAAS and it worked fine.
Using Juju bootstrap to start a Centos7 node produced an error:
command: juju bootstrap --bootstrap-series=centos7 --config bootstrap-
timeout=1800 --constraints mem=900 devmaas testmaas-controller
------------------------
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the
problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save
--setopt=<repoid>.skip_if_unavailable=true
Cannot find a valid baseurl for repo: base/7/x86_64
Could not retrieve mirrorlist
http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=genclo error
was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service
not known"
ERROR failed to bootstrap model: subprocess encountered error code 1
Node shown as READY in MAAS. Last message on node shows "-----BEGIN SSH
HOST KEY KEYS-----" and "Cloud-init v. 0.7.5 finished at....".
What did I miss?
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691663
Title:
Juju bootstrap maas centos7 yum repo not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1691663/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
