Ubuntu

security.ubuntu.com in AWS fails when connecting to 91.189.91.39

Bug #1972915 reported by Bryan Turner on 2022-05-11

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	Invalid	Undecided	Unassigned

Bug Description

I have been having on and off again issues when running apt-get update from an AWS machine. It appears that this site is behind a load balancer and every 3rd attempt fails.

From an AWS EC-2 instance today, every 3rd try to ping gets me to a bad instance (91.189.91.39):

$ ping security.ubuntu.com
PING security.ubuntu.com (185.125.190.39) 56(84) bytes of data.
64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=1 ttl=37 time=73.2 ms
64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=2 ttl=37 time=73.1 ms
64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=3 ttl=37 time=73.1 ms
^C
--- security.ubuntu.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 73.160/73.203/73.266/0.225 ms

$ ping security.ubuntu.com
PING security.ubuntu.com (185.125.190.36) 56(84) bytes of data.
64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=1 ttl=37 time=73.3 ms
64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=2 ttl=37 time=73.4 ms
64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=3 ttl=37 time=73.5 ms
64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=4 ttl=37 time=73.4 ms
^C
--- security.ubuntu.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 73.396/73.438/73.527/0.336 ms

ping security.ubuntu.com
PING security.ubuntu.com (91.189.91.39) 56(84) bytes of data.
^C
--- security.ubuntu.com ping statistics ---
71 packets transmitted, 0 received, 100% packet loss, time 71657ms

Tags:

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2022-05-11:

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1972915/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags:

added: bot-comment

Revision history for this message

Brian Murray (brian-murray) wrote on 2022-05-11:

I escalated this with Canonical's IS department and they are currently tracking and working on the issue. Thanks for bringing it to our attention!

Revision history for this message

Bryan Turner (aef0x) wrote on 2022-05-11: Re: [Bug 1972915] Re: security.ubuntu.com in AWS fails when connecting to 91.189.91.39

Excellent... I thought it was addressed this morning (8-10AM Pacific time)
however I started seeing it again after that.

On Wed, May 11, 2022, 2:50 PM Brian Murray <email address hidden>
wrote:

> I escalated this with Canonical's IS department and they are currently
> tracking and working on the issue. Thanks for bringing it to our
> attention!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1972915
>
> Title:
> security.ubuntu.com in AWS fails when connecting to 91.189.91.39
>
> Status in Ubuntu:
> New
>
> Bug description:
> I have been having on and off again issues when running apt-get update
> from an AWS machine. It appears that this site is behind a load
> balancer and every 3rd attempt fails.
>
> From an AWS EC-2 instance today, every 3rd try to ping gets me to a
> bad instance (91.189.91.39):
>
> $ ping security.ubuntu.com
> PING security.ubuntu.com (185.125.190.39) 56(84) bytes of data.
> 64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=1
> ttl=37 time=73.2 ms
> 64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=2
> ttl=37 time=73.1 ms
> 64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=3
> ttl=37 time=73.1 ms
> ^C
> --- security.ubuntu.com ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2000ms
> rtt min/avg/max/mdev = 73.160/73.203/73.266/0.225 ms
>
> $ ping security.ubuntu.com
> PING security.ubuntu.com (185.125.190.36) 56(84) bytes of data.
> 64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=1
> ttl=37 time=73.3 ms
> 64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=2
> ttl=37 time=73.4 ms
> 64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=3
> ttl=37 time=73.5 ms
> 64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=4
> ttl=37 time=73.4 ms
> ^C
> --- security.ubuntu.com ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3001ms
> rtt min/avg/max/mdev = 73.396/73.438/73.527/0.336 ms
>
> ping security.ubuntu.com
> PING security.ubuntu.com (91.189.91.39) 56(84) bytes of data.
> ^C
> --- security.ubuntu.com ping statistics ---
> 71 packets transmitted, 0 received, 100% packet loss, time 71657ms
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1972915/+subscriptions
>
>

Excellent...  I thought it was addressed this morning (8-10AM Pacific time)
however I started seeing it again after that.

On Wed, May 11, 2022, 2:50 PM Brian Murray <1972915@bugs.launchpad.net>
wrote:

> I escalated this with Canonical's IS department and they are currently
> tracking and working on the issue. Thanks for bringing it to our
> attention!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1972915
>
> Title:
>   security.ubuntu.com in AWS fails when connecting to 91.189.91.39
>
> Status in Ubuntu:
>   New
>
> Bug description:
>   I have been having on and off again issues when running apt-get update
>   from an AWS machine.  It appears that this site is behind a load
>   balancer and every 3rd attempt fails.
>
>   From an AWS EC-2 instance today, every 3rd try to ping gets me to a
>   bad instance (91.189.91.39):
>
>   $ ping security.ubuntu.com
>   PING security.ubuntu.com (185.125.190.39) 56(84) bytes of data.
>   64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=1
> ttl=37 time=73.2 ms
>   64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=2
> ttl=37 time=73.1 ms
>   64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=3
> ttl=37 time=73.1 ms
>   ^C
>   --- security.ubuntu.com ping statistics ---
>   3 packets transmitted, 3 received, 0% packet loss, time 2000ms
>   rtt min/avg/max/mdev = 73.160/73.203/73.266/0.225 ms
>
>   $ ping security.ubuntu.com
>   PING security.ubuntu.com (185.125.190.36) 56(84) bytes of data.
>   64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=1
> ttl=37 time=73.3 ms
>   64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=2
> ttl=37 time=73.4 ms
>   64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=3
> ttl=37 time=73.5 ms
>   64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=4
> ttl=37 time=73.4 ms
>   ^C
>   --- security.ubuntu.com ping statistics ---
>   4 packets transmitted, 4 received, 0% packet loss, time 3001ms
>   rtt min/avg/max/mdev = 73.396/73.438/73.527/0.336 ms
>
>   ping security.ubuntu.com
>   PING security.ubuntu.com (91.189.91.39) 56(84) bytes of data.
>   ^C
>   --- security.ubuntu.com ping statistics ---
>   71 packets transmitted, 0 received, 100% packet loss, time 71657ms
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1972915/+subscriptions
>
>

Revision history for this message

Junien F (axino) wrote on 2022-11-17:

Hi Bryan ! Sorry for the delay in getting back to you. Is this problem still happening ?

Thanks

Changed in ubuntu:
status:	New → Incomplete

Revision history for this message

Bryan Turner (aef0x) wrote on 2022-11-17:

Nope, have not seen this issue since shortly after I filed the bug.

Thanks

On Thu, Nov 17, 2022 at 2:43 PM Junien Fridrick <email address hidden>
wrote:

> Hi Bryan ! Sorry for the delay in getting back to you. Is this problem
> still happening ?
>
> Thanks
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1972915
>
> Title:
> security.ubuntu.com in AWS fails when connecting to 91.189.91.39
>
> Status in Ubuntu:
> Incomplete
>
> Bug description:
> I have been having on and off again issues when running apt-get update
> from an AWS machine. It appears that this site is behind a load
> balancer and every 3rd attempt fails.
>
> From an AWS EC-2 instance today, every 3rd try to ping gets me to a
> bad instance (91.189.91.39):
>
> $ ping security.ubuntu.com
> PING security.ubuntu.com (185.125.190.39) 56(84) bytes of data.
> 64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=1
> ttl=37 time=73.2 ms
> 64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=2
> ttl=37 time=73.1 ms
> 64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=3
> ttl=37 time=73.1 ms
> ^C
> --- security.ubuntu.com ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2000ms
> rtt min/avg/max/mdev = 73.160/73.203/73.266/0.225 ms
>
> $ ping security.ubuntu.com
> PING security.ubuntu.com (185.125.190.36) 56(84) bytes of data.
> 64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=1
> ttl=37 time=73.3 ms
> 64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=2
> ttl=37 time=73.4 ms
> 64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=3
> ttl=37 time=73.5 ms
> 64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=4
> ttl=37 time=73.4 ms
> ^C
> --- security.ubuntu.com ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3001ms
> rtt min/avg/max/mdev = 73.396/73.438/73.527/0.336 ms
>
> ping security.ubuntu.com
> PING security.ubuntu.com (91.189.91.39) 56(84) bytes of data.
> ^C
> --- security.ubuntu.com ping statistics ---
> 71 packets transmitted, 0 received, 100% packet loss, time 71657ms
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1972915/+subscriptions
>
>

Nope, have not seen this issue since shortly after I filed the bug.

Thanks

On Thu, Nov 17, 2022 at 2:43 PM Junien Fridrick <1972915@bugs.launchpad.net>
wrote:

> Hi Bryan ! Sorry for the delay in getting back to you. Is this problem
> still happening ?
>
> Thanks
>
> ** Changed in: ubuntu
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1972915
>
> Title:
>   security.ubuntu.com in AWS fails when connecting to 91.189.91.39
>
> Status in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have been having on and off again issues when running apt-get update
>   from an AWS machine.  It appears that this site is behind a load
>   balancer and every 3rd attempt fails.
>
>   From an AWS EC-2 instance today, every 3rd try to ping gets me to a
>   bad instance (91.189.91.39):
>
>   $ ping security.ubuntu.com
>   PING security.ubuntu.com (185.125.190.39) 56(84) bytes of data.
>   64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=1
> ttl=37 time=73.2 ms
>   64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=2
> ttl=37 time=73.1 ms
>   64 bytes from aerodent.canonical.com (185.125.190.39): icmp_seq=3
> ttl=37 time=73.1 ms
>   ^C
>   --- security.ubuntu.com ping statistics ---
>   3 packets transmitted, 3 received, 0% packet loss, time 2000ms
>   rtt min/avg/max/mdev = 73.160/73.203/73.266/0.225 ms
>
>   $ ping security.ubuntu.com
>   PING security.ubuntu.com (185.125.190.36) 56(84) bytes of data.
>   64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=1
> ttl=37 time=73.3 ms
>   64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=2
> ttl=37 time=73.4 ms
>   64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=3
> ttl=37 time=73.5 ms
>   64 bytes from actiontoad.canonical.com (185.125.190.36): icmp_seq=4
> ttl=37 time=73.4 ms
>   ^C
>   --- security.ubuntu.com ping statistics ---
>   4 packets transmitted, 4 received, 0% packet loss, time 3001ms
>   rtt min/avg/max/mdev = 73.396/73.438/73.527/0.336 ms
>
>   ping security.ubuntu.com
>   PING security.ubuntu.com (91.189.91.39) 56(84) bytes of data.
>   ^C
>   --- security.ubuntu.com ping statistics ---
>   71 packets transmitted, 0 received, 100% packet loss, time 71657ms
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1972915/+subscriptions
>
>

Revision history for this message

Junien F (axino) wrote on 2022-11-18:

OK that's good to hear - thanks for the update :)

Changed in ubuntu:
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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