Welcome to the Linux Foundation Forum!

Lab 3.2: apt-get update fails on compute-node


./stack.sh fails due to errors while fetching packages with apt.

manual "sudo apt-get update" on the compute nodes fails as well.

Ign:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/ocata/main Translation-en_CA
Ign:7 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/ocata/main Translation-en
Fetched 323 kB in 0s (355 kB/s)
Reading package lists... Done
W: The repository 'http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/ocata Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/xenial-updates/ocata/main/binary-amd64/Packages 503 Service Temporarily Unavailable
E: Some index files failed to download. They have been ignored, or old ones used instead.
ubuntu@compute-node:~$ wget http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/xenial-updates/ocata/main/binary-amd64/Release
--2018-09-21 10:05:06-- http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/xenial-updates/ocata/main/binary-amd64/Release
Resolving ubuntu-cloud.archive.canonical.com (ubuntu-cloud.archive.canonical.com)...
Connecting to ubuntu-cloud.archive.canonical.com (ubuntu-cloud.archive.canonical.com)||:80... connected.
HTTP request sent, awaiting response... 503 Service Temporarily Unavailable
2018-09-21 10:05:06 ERROR 503: Service Temporarily Unavailable.


I also got disconnected from the Lab once with the error message "connection dropped..." Are there any
issues with the network on your side?

Thanks and regards!


  • serewicz
    serewicz Posts: 1,000


    Thank you for contacting us. I also am finding some issues getting to and working with the lab. I have sent a message to the infrastructure support team with this information. I will let you know as soon as I hear something back.


  • pekon
    pekon Posts: 12

    I'm observing same error while using devstack/stack.sh .. Please help with the resolution.
    My Lab session is : http://2886795295-80-frugo03.openstack-environments.katacoda.com/

    with regards, pekon

  • pekon
    pekon Posts: 12

    just want to add .. same devstack setup works for Lab-3-3

    NOT Working Lab URL: https://www.katacoda.com/linuxfoundation/courses/lfs252/2
    NOT Working Session: http://2886795295-80-frugo03.openstack-environments.katacoda.com/

    Working Lab URL: https://www.katacoda.com/linuxfoundation/courses/lfs252/3-3
    Working Session: http://2886795274-80-frugo03.openstack-environments.katacoda.com/

    Are the ubuntu xenial images used in two sessions same ? It seems something is blocking the update in sessions created by lsfs252/2. It may be the default firewall config .. please check.

    regards, pekon

  • serewicz
    serewicz Posts: 1,000

    Hello Pekon,

    Thank you for the detailed feedback. It sounds like something is not working with that particular image or setup. I am unaware of any intentional change. I will forward your issues on to the infrastructure person.

    Thank you,

  • serewicz
    serewicz Posts: 1,000

    I have heard back from the infrastructure person. It seems that the pt-get update issues were due to a mirror what had issues for a bit, but is back in working order.

    As for the devstack install issues, this seems to be tied to ongoing work in the Pike release github source, where configuration files were changed and an "undocumented feature" was introduced. Should the code not be updated back to expected manner in a timely manner I will update the content for whichever the new installation process of the Pike it may call for. This was not an expected change by the community, as sometimes happens with open source and fast changing projects.

    Thank you again for contacting us,


  • pekon
    pekon Posts: 12

    @serewicz said:


    As for the devstack install issues, this seems to be tied to ongoing work in the Pike release github source, where configuration files were changed and an "undocumented feature" was introduced.

    Thank You very much for sharing the details. Its good to know the background for understanding what all possibilities exist in real world scenario. However I was assuming devstack uses stable/pike branch, does this mean "undocumented feature" got pushed to the 'stable' branch ? :smile:
    if feasible, please update the LAB images to stable/stein instead of patching stable/pike.

    regards, pekon


Upcoming Training