Bug 1107172 - Traffic Control start error
Summary: Traffic Control start error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
: ---
Assignee: Rajat Chopra
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-09 20:28 UTC by Bela Szalai
Modified: 2017-05-31 18:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-31 18:22:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Openshift Origin Node platform trace log file (7.53 KB, text/plain)
2014-06-09 20:28 UTC, Bela Szalai
no flags Details

Description Bela Szalai 2014-06-09 20:28:33 UTC
Created attachment 906250 [details]
Openshift Origin Node platform trace log file

Hi!

I'v installed Openshift Origin (all-in-one configuration) on a brand new Fedora 19 server (installed into virtualbox VM), by following the comprehensive deployment guide (release version). Everything seems to work fine except traffic control. If I execute oo-diagnostics or oo-accept-node, "tc htb qdisc not configured" error will be reported.
By the node's platform trace log, it seems the tc command fails by syntax error. Trace log attached.

I'v checked twice the node configuration instructions, but I could not recognize any configuration issue (typos, etc.).

Version info:
OS: Fedora 19 - Linux version 3.14.4-100.fc19.x86_64 (mockbuild@bkernel02) (gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) (GCC) ) #1 SMP Tue May 13 15:00:26 UTC 2014
Openshift: installation instructions followed from http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html
VirtualBox: Oracle VirtualBox v4.3.8 r92456

Reproduction:
1. OS install: in a new virtual box VM, install minimal configuration Fedora 19 x86_64 (NAT and bridged network devices configured).
2. Disable NAT network card for the VM.
3. Boot into Fedora. In grub set GRUB_CMDLINE_LINUX with "net.ifnames=0 biosdevname=0" options, regenerate grub config, and clean network configuration (/etc/sysconfig/network-scripts/ifcfg* configuration), only eth0 remaining.
4. Follow the comprehensive deployment guide, build all-in-one configuration.
5. When testing deployment, run oo-diagnostics -v command. One error never disappears when checking node acceptance (I fixed some minor warnings: disctrict configuration, mlocate install): "tc htb qdisc not configured". As platform trace log shows network device (eth0, confiugred in node.conf correctly as external device) was found, but the next script which would initialize traffic control qdisc configuration fails (trace log attached).

Actual results:
"oo-accept-node" or "oo-diagnostics -v" command:
tc htb qdisc not configured
1 ERROR

Expected results:
oo-accept-node
PASS

Additional info: "oo-diagnostics -v" command output:
INFO: loading list of installed packages
INFO: OpenShift broker installed.
INFO: OpenShift node installed.
INFO: Loading the broker rails environment.
/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:98: warning: already initialized constant Psych::VERSION
/usr/share/ruby/vendor_ruby/psych.rb:98: warning: previous definition of VERSION was here
/usr/share/gems/gems/psych-2.0.0/lib/psych.rb:101: warning: already initialized constant Psych::LIBYAML_VERSION
/usr/share/ruby/vendor_ruby/psych.rb:101: warning: previous definition of LIBYAML_VERSION was here
INFO: running: prereq_dns_server_available
INFO: checking that the first server in /etc/resolv.conf responds
INFO: running: prereq_domain_resolves
INFO: checking that we can resolve our application domain
INFO: running: test_enterprise_rpms
INFO: skipping test_enterprise_rpms
INFO: running: test_selinux_policy_rpm
INFO: running: test_selinux_enabled
INFO: running: test_broker_cache_permissions
INFO: broker application cache permissions appear fine
INFO: running: test_node_profiles_districts_from_broker
INFO: checking node profiles via MCollective
INFO: profile for broker.openshift.szte: small
INFO: checking that node profiles and districts are consistent
INFO: district 'small_district' has profile 'small'
INFO:   host broker.openshift.szte is active in district 'small_district'
INFO: running: test_broker_accept_scripts
INFO: running oo-accept-broker
INFO: oo-accept-broker ran without error:
--BEGIN OUTPUT--
NOTICE: SELinux is Enforcing
NOTICE: SELinux is  Enforcing
PASS

--END oo-accept-broker OUTPUT--
INFO: running oo-accept-systems -w 2
INFO: oo-accept-systems -w 2 ran without error:
--BEGIN OUTPUT--
PASS

--END oo-accept-systems -w 2 OUTPUT--
INFO: running: test_node_accept_scripts
INFO: running oo-accept-node
FAIL: run_script
oo-accept-node had errors:
--BEGIN OUTPUT--
FAIL: tc htb qdisc not configured
1 ERRORS

--END oo-accept-node OUTPUT--
INFO: running: test_broker_httpd_error_log
INFO: running: test_broker_passenger_ps
INFO: checking the broker application process tree
INFO: running: test_for_nonrpm_rubygems
INFO: skipping test_for_nonrpm_rubygems
INFO: running: test_for_multiple_gem_versions
INFO: checking for presence of gem-installed rubygems
INFO: running: test_node_httpd_error_log
INFO: running: test_node_containerization_plugin
INFO: running: test_node_mco_log
INFO: running: test_pam_openshift
INFO: running: test_services_enabled
INFO: checking that required services are running now
INFO: checking that required services are enabled at boot
INFO: running: test_node_quota_bug
INFO: skipping test_node_quota_bug
INFO: running: test_vhost_servernames
INFO: checking for vhost interference problems
INFO: running: test_altered_package_owned_configs
INFO: running: test_broken_httpd_version
INFO: running: test_usergroups_enabled
INFO: running: test_mcollective_context
INFO: running: test_mcollective_bad_facts
INFO: running: test_auth_conf_files
INFO: running: test_broker_certificate
WARN: test_broker_certificate
Using a self-signed certificate for the broker
INFO: running: test_abrt_addon_python
INFO: running: test_node_frontend_clash
INFO: running: test_yum_configuration
1 WARNINGS
1 ERRORS

Please, help me if there is a bug in the release, or missing any insruction from the deployment guide. I'm very interested in having a fully working Openshift Origin installation!

Please inform me, if any more information needed to be attached to this issue report!

Thanks,
Bela Szalai

Comment 1 Eric Paris 2017-05-31 18:22:11 UTC
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.


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