[atomic-wg] Issue #456: F28 Atomic Beta AMIs do not connect to the network when using private IPs only
1:02 a.m.
jdoss reported a new issue against the project: `atomic-wg` that you are following:
``
It seems that Fedora 28 Atomic Beta (and F28 Beta Cloud) when using private IPs only, does
not connect to the network. This results in the EC2 instance failing it's connectivity
test and you cannot connect to it via SSH. If you test the AMI with a Public IP however,
it will work just fine.
This was tested with the Fedora-AtomicHost-28_Beta-1.3.x86_64-us-west-2-HVM-gp2-0
(ami-e5841f9d) AMI. I detached the failed EC2 instance's EBS volume and attached it
to a working server to dump the cloud-init.log and the systemd journal. You can download
them here.
https://www.solidadmin.com/atomic/f28atomic-cloud-init.log
https://www.solidadmin.com/atomic/f28atomic-journal.log
I have included the Fedora 28 Cloud logs as well if they will help.
https://www.solidadmin.com/atomic/f28cloud-cloud-init.log
https://www.solidadmin.com/atomic/f28cloud-journal.log
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
2:28 a.m.
sayanchowdhury added a new comment to an issue you are following:
``
The links to the logs are throwing 403 to me.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
8:21 a.m.
jdoss added a new comment to an issue you are following:
``
@sayanchowdhury Sorry about that. Mod_security thought it was being helpful. Try these:
https://www.solidadmin.com/atomic/f28atomic-cloud-init
https://www.solidadmin.com/atomic/f28atomic-journal
https://www.solidadmin.com/atomic/f28cloud-cloud-init
https://www.solidadmin.com/atomic/f28cloud-journal
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
10:04 a.m.
dustymabe added a new comment to an issue you are following:
``
did this work for f27?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
10:27 a.m.
jdoss added a new comment to an issue you are following:
``
Yes, F27 works fine. We have 50+ servers running F27 in right now and they pull an
internal IP just fine.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
10:32 a.m.
jdoss added a new comment to an issue you are following:
``
To rule out any edge cases that maybe present from how my work sets up VPCs, I spun up a
VM in us-east-1 with the default VPC and the result was the same. You can see below the
instance is failing 1/2 checks and you cannot SSH to the machine over the private IP.
[](/atomic-wg/issue/raw/files/97448e902163677c4579142841dfa0843902c6ef3598b0bfc2a46d7d7f98c738-Screenshot_from_2018-04-18_09-54-10.png)
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
11:06 a.m.
jdoss added a new comment to an issue you are following:
``
I just noticed that the above screenshot was for Cloud. Here is the same test for Atomic
in a default VPC failing it's Instance Status Check.
[](/atomic-wg/issue/raw/files/f08ebd9f8e1e811aa1389b3dc7c01705563b8678ed19be75569d07f81d7ff7ff-Screenshot_from_2018-04-18_11-04-53.png)
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
3:46 p.m.
jdoss added a new comment to an issue you are following:
``
Looks like cloud-init is setting `BOOTPROTO=none` for some reason.
```
[fedora@worker ~]# cat /mnt/f28/etc/redhat-release
Fedora release 28 (Twenty Eight)
[fedora@worker ~]# cat /mnt/f28/etc/sysconfig/network-scripts/ifcfg-eth0
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=none
DEVICE=eth0
HWADDR=06:83:72:56:7c:66
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
```
```
[fedora@worker ~]$ cat /etc/redhat-release
Fedora release 27 (Twenty Seven)
[fedora@worker ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=dhcp
DEVICE=eth0
HWADDR=02:71:be:de:7b:e6
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
4:29 p.m.
dustymabe added a new comment to an issue you are following:
``
interesting.. I wonder if [this upstream
commit](https://git.launchpad.net/cloud-init/commit/?id=eb292c1) (first released in
cloud-init `17.2`) might fix the issue?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
10:46 p.m.
jdoss added a new comment to an issue you are following:
``
Using the patch from the upstream commit above resulted in no change.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
10:58 p.m.
jdoss added a new comment to an issue you are following:
``
Opened https://bugzilla.redhat.com/show_bug.cgi?id=1569321 per @dustymabe's request.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
3:46 p.m.
jdoss added a new comment to an issue you are following:
``
Reverting to `cloud-init-0.7.9-9.fc27.noarch` fixes the issue and allows the EC2 instance
to DHCP:
```
[jdoss@sts71 ~]$ ssh fedora(a)10.0.11.156
Warning: Permanently added '10.0.11.156' (ECDSA) to the list of known hosts.
[fedora@ip-10-0-11-156 ~]$ cat /etc/redhat-release
Fedora release 28 (Twenty Eight)
[fedora@ip-10-0-11-156 ~]$ rpm -qa |grep cloud-init
cloud-init-0.7.9-9.fc27.noarch
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
12:12 p.m.
dustymabe added a new comment to an issue you are following:
``
[BZ1569321](https://bugzilla.redhat.com/show_bug.cgi?id=1569321) has been resolved now and
is fixed in the f28 release going out tomorrow.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/456
12:12 p.m.
The status of the issue: `F28 Atomic Beta AMIs do not connect to the network when using
private IPs only` of project: `atomic-wg` has been updated to: Closed as Fixed by
dustymabe.
https://pagure.io/atomic-wg/issue/456
2194
days inactive
2206
days old
atomic@lists.fedoraproject.org
13 comments
3 participants
participants (3)
-
Dusty Mabe -
Joe Doss
-
Sayan Chowdhury