RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 969031 - os cant bring bridge up after installation
Summary: os cant bring bridge up after installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-30 14:03 UTC by Xiaoqing Wei
Modified: 2016-11-25 13:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-12 07:49:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
kickstart (6.36 KB, text/plain)
2013-05-30 14:03 UTC, Xiaoqing Wei 		no flags Details
View All

Description Xiaoqing Wei 2013-05-30 14:03:56 UTC 
Created attachment 754871 [details]
kickstart

Description of problem:

os cant bring bridge up after installation

Version-Release number of selected component (if applicable):

initscripts-9.46-1.el7.x86_64
all components from 20130522.0

How reproducible:

5/5

Steps to Reproduce:
1.install a host w/ a kickstart, attached.
2.
3.

Actual results:
host didn't have network access after installation

Expected results:
host network should functional

Additional info:
Comment 1 Lukáš Nykrýn 2013-05-30 14:13:15 UTC 
Can you please attach the output of systemctl status network.service?
Comment 3 Xiaoqing Wei 2013-05-31 02:01:28 UTC 
(In reply to Lukáš Nykrýn from comment #1)
> Can you please attach the output of systemctl status network.service?

[root@localhost staf-kvm-devel]# systemctl status network.service
network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network)
   Active: active (exited) since Thu 2013-05-30 17:00:28 CST; 17h ago
Comment 4 Lukáš Nykrýn 2013-05-31 07:13:48 UTC 
I was more interested in lines which can be below these, can you try to restart network and post here the output again and also "journalctl -u network.service
"?
Comment 5 Xiaoqing Wei 2013-05-31 07:53:23 UTC 
(In reply to Lukáš Nykrýn from comment #4)
> I was more interested in lines which can be below these, can you try to
> restart network and post here the output again and also "journalctl -u
> network.service
> "?

[root@dhcp-10-30 ~]# systemctl restart network.service
[root@dhcp-10-30 ~]# journalctl -u network.service
-- Logs begin at Thu 2013-05-30 21:29:51 CST, end at Fri 2013-05-31 15:52:41 CST. --
May 30 21:30:02 dhcp-10-30.nay.redhat.com systemd[1]: Starting LSB: Bring up/down networking...
May 30 21:30:02 dhcp-10-30.nay.redhat.com systemd[1]: Started LSB: Bring up/down networking.
May 31 10:20:08 dhcp-10-30.nay.redhat.com systemd[1]: Stopping LSB: Bring up/down networking...
May 31 10:20:08 dhcp-10-30.nay.redhat.com systemd[1]: Stopped LSB: Bring up/down networking.
-- Reboot --
May 31 10:22:02 dhcp-10-30.nay.redhat.com systemd[1]: Starting LSB: Bring up/down networking...
May 31 10:22:02 dhcp-10-30.nay.redhat.com systemd[1]: Started LSB: Bring up/down networking.
May 31 10:38:44 dhcp-10-30.nay.redhat.com systemd[1]: Stopping LSB: Bring up/down networking...
May 31 10:38:44 dhcp-10-30.nay.redhat.com systemd[1]: Stopped LSB: Bring up/down networking.
-- Reboot --
May 31 15:52:41 dhcp-10-30.nay.redhat.com systemd[1]: Stopping LSB: Bring up/down networking...
May 31 15:52:41 dhcp-10-30.nay.redhat.com systemd[1]: Starting LSB: Bring up/down networking...
May 31 15:52:41 dhcp-10-30.nay.redhat.com systemd[1]: Started LSB: Bring up/down networking.
Comment 6 Lukáš Nykrýn 2013-07-11 14:11:31 UTC 
Sorry for a delay. I still can't see where the issue might be.
Please attach sour configuration files and try:
[root@notas system]# export SYSTEMCTL_SKIP_REDIRECT=1
[root@notas system]# /etc/init.d/network restart
Comment 7 Xiaoqing Wei 2013-07-12 07:20:26 UTC 
Alright, looks this issue doesn't exist now, 

initscripts-9.47-1.el7.x86_64
systemd-204-9.el7.1.x86_64

[root@dhcp-10-30 ~]# systemctl status network.service
network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network)
   Active: active (running) since Fri 2013-07-12 15:10:13 CST; 4min 58s ago
  Process: 578 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS)
   CGroup: name=systemd:/system/network.service

now the bridge would up and running after os installation.




[root@dhcp-10-30 network-scripts]# cat ifcfg-br0 ifcfg-eth0 
DEVICE=switch
BOOTPROTO=dhcp
ONBOOT=yes
DELAY=0
TYPE=Bridge
# Generated by parse-kickstart
IPV6INIT=yes
DEVICE=eth0
ONBOOT=yes
UUID=ee4931a5-c78a-467a-9405-2260ea674dc4
HWADDR=E8:39:35:52:93:D0
TYPE=Ethernet
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME="System eth0"
BRIDGE=switch
Comment 8 Lukáš Nykrýn 2013-07-12 07:49:51 UTC 
So I will close this as a current release, if the issue reappears please reopen this bug.
Note You need to log in before you can comment on or make changes to this bug.