aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Cohen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-1788) vagrant up does not properly configure network adapters
Date Fri, 07 Oct 2016 01:08:20 GMT

     [ https://issues.apache.org/jira/browse/AURORA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joshua Cohen updated AURORA-1788:
---------------------------------
    Assignee: Andrew Jorgensen

> vagrant up does not properly configure network adapters
> -------------------------------------------------------
>
>                 Key: AURORA-1788
>                 URL: https://issues.apache.org/jira/browse/AURORA-1788
>             Project: Aurora
>          Issue Type: Bug
>            Reporter: Andrew Jorgensen
>            Assignee: Andrew Jorgensen
>
> I am not sure of the specifics of why this happens but on vagrant 1.8.6 the network interface
does not come up correctly and the private_network is attached to the eth0 nat interface rather
than the host-only interface. I tried a number of different parameters but none of them were
able to configure the network appropriately. This change manually configures the static ip
so that it is connected to the correct adapter. Without this change I could not access the
aurora web interface when running vagrant up.
> I've created a patch here: https://reviews.apache.org/r/52609/
> This is what the configuration looks like when run off master:
> {code}
> ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>        valid_lft forever preferred_lft forever
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group
default qlen 1000
>     link/ether 08:00:27:b3:1b:30 brd ff:ff:ff:ff:ff:ff
>     inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
>        valid_lft forever preferred_lft forever
>     inet 192.168.33.7/24 brd 192.168.33.255 scope global eth1
>        valid_lft forever preferred_lft forever
>     inet6 fe80::a00:27ff:feb3:1b30/64 scope link
>        valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DOWN
group default
>     link/ether 08:00:27:7c:4e:72 brd ff:ff:ff:ff:ff:ff
> 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
group default
>     link/ether 02:42:f6:de:a3:ca brd ff:ff:ff:ff:ff:ff
>     inet 172.17.0.1/16 scope global docker0
>        valid_lft forever preferred_lft forever
> {code}
> here is what it is supposed to look like:
> {code}
> ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>        valid_lft forever preferred_lft forever
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group
default qlen 1000
>     link/ether 08:00:27:b3:1b:30 brd ff:ff:ff:ff:ff:ff
>     inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0
>        valid_lft forever preferred_lft forever
>     inet6 fe80::a00:27ff:feb3:1b30/64 scope link
>        valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group
default qlen 1000
>     link/ether 08:00:27:7c:4e:72 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.33.7/24 brd 192.168.33.255 scope global eth1
>        valid_lft forever preferred_lft forever
>     inet6 fe80::a00:27ff:fe7c:4e72/64 scope link
>        valid_lft forever preferred_lft forever
> 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
group default
>     link/ether 02:42:f6:de:a3:ca brd ff:ff:ff:ff:ff:ff
>     inet 172.17.0.1/16 scope global docker0
>        valid_lft forever preferred_lft forever
> {code}
> Steps to reproduce:
> 1. Update to vagrant 1.8.6 (unsure if previous versions are affected as well)
> 2. Run `vagrant up`
> 3. Try to visit http://192.168.33.7:8081
> Expected outcome:
> I expect that following the steps in http://aurora.apache.org/documentation/latest/getting-started/vagrant/
I would be able to visit the web interface for aurora.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message