Failure in updating Ubuntu repository!

Bug #1872018 reported by redgreenblue
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MicroStack
Expired
Undecided
Unassigned

Bug Description

Hello everyone,

I have installed microstack successfully on Ubuntu 16.04. But when I want to update a Ubuntu VM repository, the updating process fails:

ubuntu@ubun18:~$ sudo apt-get update
Err:1 http://archive.canonical.com/ubuntu bionic InRelease
  Temporary failure resolving 'archive.canonical.com'
Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu bionic InRelease
  Temporary failure resolving 'archive.ubuntu.com'
0% [Working]^C

Should I activate any services?
I checked /etc/resolv.conf and it was as follows:

nameserver is 127.0.0.53
options edns0
search openstacklocal

Would you please help me?

Thanks.

summary: - ssh: connect to host port 22: No route to host
+ Failure in updating Ubuntu repository!
description: updated
Revision history for this message
Pen Gale (pengale) wrote :

Are you in a restricted egress environment? MicroStack routers use Cloudflare's DNS (1.1.1.1) by default, and this may not work everywhere.

You can set a different DNS by doing:

    sudo snap set microstack config.network.dns=<some dns>
    sudo snap restart microstack

Revision history for this message
Corey Bryant (corey.bryant) wrote :

What Pete said in comment #1 is still true but the setting is now 'config.network.dns-servers'. E.g.

$ sudo snap get microstack config.network.dns-servers
1.1.1.1

I'm going to mark this bug as incomplete for now. Please change the status back to New if there are more details that point to this being a bug in microstack.

Thanks,
Corey

Changed in microstack:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MicroStack because there has been no activity for 60 days.]

Changed in microstack:
status: Incomplete → Expired
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.