Bug 1314274
Summary: | livemedia-creator doesn't recognize "--network" from kickstart file | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | dearfriend <appraprv> | ||||||||||
Component: | lorax | Assignee: | Brian Lane <bcl> | ||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 7.2 | CC: | anater78, appraprv, rvykydal | ||||||||||
Target Milestone: | rc | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2016-03-30 19:05:32 UTC | Type: | Bug | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
dearfriend
2016-03-03 10:19:08 UTC
I'm not sure that it's going to be possible to setup team interfaces with livemedia-creator. Could you attach the installation logs from ./anaconda/* as individual text/plain attachments? I've also added our network expert, Radek, to the cc list for his thoughts. Created attachment 1132880 [details]
./anaconda/anaconda.log
Created attachment 1132881 [details]
./anaconda/packaging.log
Created attachment 1132885 [details]
./anaconda/program.log
Created attachment 1132887 [details]
./anaconda/storage.log
./anaconda/ifcfg.log is empty. We don't write network configuration to target root for dirinstall so the ifcfg files would need to be copied in %post script. When I copy files in %post: %post cat << 'EOF' > /etc/sysconfig/network-scripts/ifcfg-team0 DEVICE=team0 DEVICETYPE=Team ONBOOT=yes BOOTPROTO=dhcp TEAM_CONFIG='{"runner": {"name": "activebackup"}, "link_watch": {"name": "ethtool"}}' EOF cat << 'EOF' > /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 DEVICETYPE=TeamPort ONBOOT=yes TEAM_MASTER=team0 TEAM_PORT_CONFIG='{"prio": 100}' EOF cat << 'EOF' > /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 DEVICETYPE=TeamPort ONBOOT=yes TEAM_MASTER=team0 TEAM_PORT_CONFIG='{"prio": 10}' EOF Files exists in rootfs, not initramfs. While boot eth0 stands up, receives IP address from dhcp and downloads rootfs image. After mount rootfs, eth0 is still active with address from dhcp. team0 interface have mac-address from eth2 and doesn't work. (dhcp configured to use mac from eth0). Second way is to set up interfaces in cmdline like team=team0:eth0,eth1 ip=dhcp But after boot there is another problem: teamdctl team0 state libteamdctl: teamdctl_connect: Failed to connect using all CLIs. teamdctl_connect failed (Invalid argument) nmcli shows extra team interface: nmcli connection show NAME UUID TYPE DEVICE Team team0 702de3eb-2e80-897c-fd52-cd0494dd8123 team -- System eth0 b48971eb-621a-99c1-8ef3-319130930ee5 802-3-ethernet eth0 System eth1 0ff8880e-97c8-95d5-45d4-064bf1f84ea2 802-3-ethernet eth1 team0 7e713034-6705-4016-a61f-e833e4949ffd team team0 third way is to omit dracut module "ifcg" and manually add ifcfg-files in initramfs. But teamdctl is not a part of initramfs image. So interface team0 doesn't start correctly anyway. I think this is going to end up being something you have to figure out how to do manually, and isn't something lmc supports. Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. |