Skip to content

puppet provisioner seem to break with python26-pip #3

Description

@ShaunLadd

Last week amazon upgraded the python-pip package in their yum repo to python26-pip. I upgraded the package on the slaves and now the puppet provisioner portion does not work with aminate. I have copied the error I receive when I try to aminate. If I use a slave that has python-pip, it works fine.

2014-09-30 19:48:24 [DEBUG] Entering chroot at /var/aminator/volumes/xvdf2
2014-09-30 19:48:24 [DEBUG] Chroot path: /var/aminator/volumes/xvdf2
2014-09-30 19:48:24 [DEBUG] Configuring chroot at /var/aminator/volumes/xvdf2
2014-09-30 19:48:24 [DEBUG] Inside chroot
2014-09-30 19:48:25 [INFO] Installing Puppet with yum.
2014-09-30 19:48:25 [DEBUG] command: yum --nogpgcheck -y install puppet
2014-09-30 19:48:36 [DEBUG] stdout: Loaded plugins: priorities, update-motd, upgrade-helper
Could not retrieve mirrorlist http://repo.$awsregion.$awsdomain/latest/main/mirror.list error was
14: PYCURL ERROR 6 - "Could not resolve host: repo.$awsregion.$awsdomain"

stderr:

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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions