cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8838) [KVM] agent setup failed when physical interface name is in ensX format (CentOS7)
Date Sun, 13 Sep 2015 09:02:46 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742412#comment-14742412
] 

ASF GitHub Bot commented on CLOUDSTACK-8838:
--------------------------------------------

Github user remibergsma commented on the pull request:

    https://github.com/apache/cloudstack/pull/811#issuecomment-139854597
  
    @giraffeforestg Thanks. Is it an idea to add all possible systemd names to prevent more
issues in the future?
    
    ```
    With systemd 197 we have added native support for a number of different naming policies
into systemd/udevd proper and made a scheme similar to biosdevname's (but generally more powerful,
and closer to kernel-internal device identification schemes) the default. The following different
naming schemes for network interfaces are now supported by udev natively:
    
    Names incorporating Firmware/BIOS provided index numbers for on-board devices (example:
eno1)
    Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example:
ens1)
    Names incorporating physical/geographical location of the connector of the hardware (example:
enp2s0)
    Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
    Classic, unpredictable kernel-native ethX naming (example: eth0)
    ```
    Source: http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
    
    Shall we add: enoX enpX enxX as well?


> [KVM] agent setup failed when physical interface name is in ensX format (CentOS7)
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8838
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8838
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.5.2
>         Environment:  CloudStack 4.5.2 (http://packages.shapeblue.com/cloudstack/upstream/centos7/4.5)
>  CentOS 7.1.1503 / KVM
>  mariadb-5.5.44-1
>            Reporter: satoru nakaya
>
> [KVM] agent setup failed when physical interface name is in ensX format (CentOS7)
> My environment:
>  CloudStack 4.5.2 (http://packages.shapeblue.com/cloudstack/upstream/centos7/4.5)
>  CentOS 7.1.1503 / KVM
>  mariadb-5.5.44-1
> management.log:
> 2015-09-12 08:19:41,930 WARN  [o.a.c.alerts] (AgentConnectTaskPool-2:ctx-4925d5ec)  alertType::
7 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: Incorrect Network setup
on agent, Reinitialize agent after network names are setup, details : Can not find network:
cloudbr1
> [root@acs ~]# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>     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: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master cloudbr0
state UP qlen 1000
>     link/ether 00:0c:29:a9:09:3f brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::20c:29ff:fea9:93f/64 scope link
>        valid_lft forever preferred_lft forever
> 3: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master cloudbr1
state UP qlen 1000
>     link/ether 00:0c:29:a9:09:49 brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::20c:29ff:fea9:949/64 scope link
>        valid_lft forever preferred_lft forever
> 4: cloudbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
>     link/ether 00:0c:29:a9:09:3f brd ff:ff:ff:ff:ff:ff
>     inet 10.0.0.30/24 brd 10.0.0.255 scope global cloudbr0
>        valid_lft forever preferred_lft forever
>     inet6 fe80::20c:29ff:fea9:93f/64 scope link
>        valid_lft forever preferred_lft forever
> 5: cloudbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
>     link/ether 00:0c:29:a9:09:49 brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::20c:29ff:fea9:949/64 scope link
>        valid_lft forever preferred_lft forever
> 6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
>     link/ether 52:54:00:99:14:38 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
>        valid_lft forever preferred_lft forever
> 7: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state
DOWN qlen 500
>     link/ether 52:54:00:99:14:38 brd ff:ff:ff:ff:ff:ff
> 8: cloud0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
>     link/ether 72:0f:e1:35:ac:6b brd ff:ff:ff:ff:ff:ff
>     inet 169.254.0.1/16 scope global cloud0
>        valid_lft forever preferred_lft forever
>     inet6 fe80::700f:e1ff:fe35:ac6b/64 scope link
>        valid_lft forever preferred_lft forever
> [root@acs ~]#
> workaround:
> Don't use ensX format.
> add net.ifnames=0 biosdevname=0 to GRUB_CMDLINE_LINUX
> [root@acs ~]# vi /etc/default/grub
>   :
> GRUB_CMDLINE_LINUX="vconsole.keymap=jp106 crashkernel=auto vconsole.font=latarcyrheb-sun16
rhgb quiet net.ifnames=0 biosdevname=0"
>   :
> [root@acs ~]# grub2-mkconfig -o /boot/grub2/grub.cfg
> And
> Edit /etc/sysconfig/network-scripts/ifcfg-ensX
>  ensX-> ethX
> [root@acs ~]# reboot
>    :
> [root@acs ~]# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>     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 master cloudbr0
state UP qlen 1000
>     link/ether 00:0c:29:a9:09:3f brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::20c:29ff:fea9:93f/64 scope link
>        valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master cloudbr1
state UP qlen 1000
>     link/ether 00:0c:29:a9:09:49 brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::20c:29ff:fea9:949/64 scope link
>        valid_lft forever preferred_lft forever
> 4: cloudbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
>     link/ether 00:0c:29:a9:09:3f brd ff:ff:ff:ff:ff:ff
>     inet 10.0.0.30/24 brd 10.0.0.255 scope global cloudbr0
>        valid_lft forever preferred_lft forever
>     inet6 fe80::20c:29ff:fea9:93f/64 scope link
>        valid_lft forever preferred_lft forever
> 5: cloudbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
>     link/ether 00:0c:29:a9:09:49 brd ff:ff:ff:ff:ff:ff
>     inet6 fe80::20c:29ff:fea9:949/64 scope link
>        valid_lft forever preferred_lft forever
> 6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
>     link/ether 52:54:00:99:14:38 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
>        valid_lft forever preferred_lft forever
> 7: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state
DOWN qlen 500
>     link/ether 52:54:00:99:14:38 brd ff:ff:ff:ff:ff:ff
> 8: cloud0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
>     link/ether 26:08:0e:aa:44:f7 brd ff:ff:ff:ff:ff:ff
>     inet 169.254.0.1/16 scope global cloud0
>        valid_lft forever preferred_lft forever
>     inet6 fe80::2408:eff:feaa:44f7/64 scope link
>        valid_lft forever preferred_lft forever
> [root@acs ~]#



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

Mime
View raw message