Created attachment 1103899 [details] screenshot with error message Description of problem: If you try to start appliance_console but the appliance does not have an IP address configured, it will fail to start. Version-Release number of selected component (if applicable): 5.5.0.13 How reproducible: always Steps to Reproduce: 1. deploy a CF appliance but make sure there is no DHCP available 2. log in and start appliance_console 3. Actual results: appliance_console fails Expected results: Additional info: I only tested this with CF4 on RHEV, but I expect similar results with other providers.
Christian, Can you provide the output from `ip addr show eth0` when this fails for you? This may have been fixed already and I can't seem to reproduce it. Thanks For me the output shows: 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 00:0c:29:e0:d6:51 brd ff:ff:ff:ff:ff:ff
With a slightly different configuration I get: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:0c:29:e0:d6:51 brd ff:ff:ff:ff:ff:ff inet6 fe80::20c:29ff:fee0:d651/64 scope link valid_lft forever preferred_lft forever In this case it is the same failure as https://bugzilla.redhat.com/show_bug.cgi?id=1286560 and has been fixed.
Any update here? Otherwise I will close as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1286560 as they have the same symptoms and fix.
Created attachment 1106036 [details] output of ip addr show eth0
Thanks, closing as a duplicate. *** This bug has been marked as a duplicate of bug 1286560 ***