apt-transport-https missing in kilo

Bug #1463155 reported by Bjoern
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
High
Kevin Carter
Kilo
Fix Released
High
Kevin Carter
Trunk
Fix Released
High
Kevin Carter

Bug Description

Since we started to move to https repositories in Kilo, the package apt-transport-https needs to be installed in order to support HTTPS as repositories in APT. That issue came up during a upgrade from juno to kilo

Changed in openstack-ansible:
importance: Undecided → High
assignee: nobody → Kevin Carter (kevin-carter)
milestone: none → 11.0.3
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

Fix proposed to branch: master
Review: https://review.openstack.org/189435

Changed in openstack-ansible:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (master)

Reviewed: https://review.openstack.org/189435
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=8bcaac5702f3ed29d74a3f49690cf2d6e3655828
Submitter: Jenkins
Branch: master

commit 8bcaac5702f3ed29d74a3f49690cf2d6e3655828
Author: kevin <email address hidden>
Date: Mon Jun 8 15:39:01 2015 -0500

    Updated upgrade and deployment processes for https

    This change simply makes sure that all containers and hosts have the
    `apt-transport-https` package installed. this package is absolutly
    required everywhere because we've changed all of the repo endpoints
    to https and not all systems have this package installed on a base
    kick. Furthermore an entry was added into the upgrade script to
    ensure that upon upgrade everything will converge and remain
    consistent.

    Change-Id: I4b357ff7099a4c1c63c85ac9560aefc8d56709be
    Closes-Bug: #1463155

Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (kilo)

Fix proposed to branch: kilo
Review: https://review.openstack.org/190049

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

Reviewed: https://review.openstack.org/190049
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=7a2221054607ad87a9b7ca8017181553e5300b35
Submitter: Jenkins
Branch: kilo

commit 7a2221054607ad87a9b7ca8017181553e5300b35
Author: kevin <email address hidden>
Date: Mon Jun 8 15:39:01 2015 -0500

    Updated upgrade and deployment processes for https

    This change simply makes sure that all containers and hosts have the
    `apt-transport-https` package installed. this package is absolutly
    required everywhere because we've changed all of the repo endpoints
    to https and not all systems have this package installed on a base
    kick. Furthermore an entry was added into the upgrade script to
    ensure that upon upgrade everything will converge and remain
    consistent.

    Change-Id: I4b357ff7099a4c1c63c85ac9560aefc8d56709be
    Closes-Bug: #1463155
    (cherry picked from commit 8bcaac5702f3ed29d74a3f49690cf2d6e3655828)

Revision history for this message
Michael Gale (gale-michael) wrote :

Hello,

    Not sure if this is the correct place for this or not, apologizes if it is not.

I think this bug still exist, I have been working with kilo branch from head and it seems that during lxc creation the sources.list is updated to the https links.

Here: roles/lxc_container_create/tasks/container_create.yml.

In order to get past the initial failure I scp the apt-transport-https deb over to each container, dpkg install it and run setup-everything again.

Michael

Revision history for this message
Kevin Carter (kevin-carter) wrote :

The image that we maintain here: http://rpc-repo.rackspace.com/container_images/rpc-trusty-container.tgz and comes with that package pre-installed. That said, if you had an old base image that was not updated with those bits you would still be having this issue. To correct the problem you can remove the base lxc cache on the hosts found here: "/var/cache/lxc/trusty" and then rerun setup everything, which will update the cache with the new image. This can be accomplished using ansible with the following command.

# root@hostname:/opt/os-ansible-deployment/playbooks# ansible hosts -m shell -a 'rm -rf /var/cache/lxc_trusty.tgz /var/cache/lxc/trusty'

Once that command completes your lxc cache for the trusty image will be purged, then you can rerun setup-everything.yml which will re-populate the cache with the updated lxc image.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.