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 857846 - Configured a static ip for RHEV-H and registered RHEV-M successful, status page should display "static" not "none".
Summary: Configured a static ip for RHEV-H and registered RHEV-M successful, status pa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 863161
TreeView+ depends on / blocked
 
Reported: 2012-09-17 08:26 UTC by chencong
Modified: 2016-04-26 14:05 UTC (History)
16 users (show)

Fixed In Version: ovirt-node-2.5.0-5.el6
Doc Type: Bug Fix
Doc Text:
When interfaces on the hypervisor were configured to use a static IP address the status page listed the relevant connection as "none". The hypervisor has been updated. Connections configured to use a static IP address are now correctly listed on the status page as "static".
Clone Of:
Environment:
Last Closed: 2013-02-28 16:38:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vdsm.log,libvirt.log,vdsm-reg.log (16.97 KB, application/x-gzip)
2012-09-17 08:26 UTC, chencong
no flags Details
ovirt.log (126.25 KB, text/x-log)
2012-09-17 10:12 UTC, chencong
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0556 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2013-02-28 21:29:06 UTC

Description chencong 2012-09-17 08:26:56 UTC
Created attachment 613590 [details]
vdsm.log,libvirt.log,vdsm-reg.log

Description of problem:
If configured a static ip for rhev-h to registered rhev-m, at the status page of rhev-h should display:"static" not "none".

Version-Release number of selected component (if applicable):
rhev-hypervisor 6-6.3-20120910.0.rhev31.el6_3
vdsm-4.9-113.3.el6_3.x86_64
rhev-m 3.0.7_0001-2.el6_3
rhev-m 3.1.0-14.el6ev

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H.
2. Configure static ip for the nic ,registered to RHEV-M successful.
3. Check the status page "Networking" display.

Actual results:
Configured a static ip and registered to RHEV-M successful, the status page of RHEV-H display "Networking :    rhevm:    none 10.66.11.20".

Expected results:
Configured a static ip and regiested to RHEV-M successful, the status page of RHEV-H should display "Networking :    rhevm: static    10.66.11.20".


Additional info:
It's right when configured a dhcp ip.No such issue in RHEV-H 6.3-20120815.0.el6_3 , so it is a regression bug.

Comment 3 chencong 2012-09-17 10:12:51 UTC
Created attachment 613621 [details]
ovirt.log

Comment 4 Fabian Deutsch 2012-09-17 13:56:16 UTC
Cong,

could you also provide the vdsm log and the output if ifcfg and brctl show.

thanks

Comment 5 Fabian Deutsch 2012-09-17 14:38:34 UTC
vdms is setting BOOTPROTO=static [1], the UI is just displaying that variable.
According to vdsm static is the correct value for static IP configurations.

In this case we should just replace none with "static".

[1] http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm/configNetwork.py;hb=HEAD#l402

Comment 6 Fabian Deutsch 2012-09-17 14:50:28 UTC
http://gerrit.ovirt.org/#/c/8023/

Tested as follows:

1. Install Node
2. Apply patch
3. Configure static net
4. Change ifcfg-breth0 bootproto to none
5. Re-login into the tui
6. static is displayed on status page

Comment 8 Fabian Deutsch 2012-09-20 08:51:53 UTC
(In reply to comment #5)
> vdms is setting BOOTPROTO=static [1], the UI is just displaying that
> variable.

Correction:
vdsm is setting BOOTPROTO=none

Comment 9 Fabian Deutsch 2012-09-20 08:59:39 UTC
Just to point it out, Node is setting BOOTPROTO=static in ifcfg-breth*, but looking at the docs [1] 'static' is no intended value for BOOTPROTO. 
It's noteworthy that looking at the search results of a famous search engine it seems to be common to use BOOTPROTO=static.
So, vdsm is doing the right thing and the TUI just needs to interprete BOOTPROTO=none as a static IP configuration.

[1] https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html

Comment 12 cshao 2012-10-31 10:18:33 UTC
There is a existing bug: Bug 867784 - [RHEV-H 6.4] The "DHCP" was marked "*" in network detail page if configured nic by using "static" .
So I will verify this bug after 867784 fixed.

Comment 17 errata-xmlrpc 2013-02-28 16:38:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0556.html


Note You need to log in before you can comment on or make changes to this bug.