[Rdo-list] [rdo-manager] instackenv.json
John Trowbridge
trown at redhat.com
Mon Oct 12 12:50:26 UTC 2015
On 10/09/2015 08:34 PM, Mohammed Arafa wrote:
> Dan
>
> Thank you it worked
> Yes its only one node. I whittled it down to remove as many variables
> for errors as possible.
>
> [stack at rdomanager ~]$ openstack baremetal instackenv validate -f
> ~/instackenv.json
> System Power : off
> Power Overload : false
> Power Interlock : inactive
> Main Power Fault : false
> Power Control Fault : false
> Power Restore Policy : always-on
> Last Power Event :
> Chassis Intrusion : inactive
> Front-Panel Lockout : inactive
> Drive Fault : false
> Cooling/Fan Fault : false
> Front Panel Control : none
> SUCCESS: found 0 errors
>
>
> Now I have another problem, seems to be iptables related. So when I
> check the ironic-inspector service, it was stopped, and the only way i
> could get it to run was to reboot the machine. i verified it was
> started then did a bulk introspection. was i surprised when i saw that
> it failed again. and the service was stopped too.
>
> not sure why iptables would cause the service to crash and refuse to restart.
>
>
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.676
> 40112 INFO ironic_inspector.main [-] Enabled processing hooks:
> ['ramdisk_error', 'root_device_hint', 'scheduler',
> 'validate_interfaces']
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.694
> 40112 WARNING ironic_inspector.firewall [-] iptables does not support
> -w flag, please update it to at least version 1.4.21
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.740
> 40112 ERROR ironic_inspector.firewall [-] iptables ('-N',
> 'ironic-inspector') failed:
> Oct 10 01:40:25 rdomanager ironic-inspector: sudo: sorry, you must
> have a tty to run sudo
This error ^ has been fixed in the latest packaging for ironic-inspector
and is the cause of the crash. This means the latest repo with the
includepkgs whitelist was not used. The repo setup instructions in the
documentation[1], are exactly what we use in CI, so YMMV if using any
other repo combination.
[1]
https://repos.fedorapeople.org/repos/openstack-m/rdo-manager-docs/liberty/
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 CRITICAL ironic_inspector [-] CalledProcessError: Command
> '('sudo', 'ironic-inspector-rootwrap',
> '/etc/ironic-inspector/rootwrap.conf', 'iptables', '-N',
> 'ironic-inspector')' returned non-zero exit status 1
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector Traceback (most recent call last):
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector File "/usr/bin/ironic-inspector", line
> 10, in <module>
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector sys.exit(main())
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector File
> "/usr/lib/python2.7/site-packages/ironic_inspector/main.py", line 388,
> in main
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector init()
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector File
> "/usr/lib/python2.7/site-packages/ironic_inspector/main.py", line 325,
> in init
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector firewall.init()
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector File
> "/usr/lib/python2.7/site-packages/ironic_inspector/firewall.py", line
> 81, in init
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector _iptables('-N', CHAIN)
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector File
> "/usr/lib/python2.7/site-packages/ironic_inspector/firewall.py", line
> 42, in _iptables
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector subprocess.check_output(cmd,
> **kwargs)
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector File
> "/usr/lib64/python2.7/subprocess.py", line 575, in check_output
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector raise CalledProcessError(retcode,
> cmd, output=output)
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector CalledProcessError: Command '('sudo',
> 'ironic-inspector-rootwrap', '/etc/ironic-inspector/rootwrap.conf',
> 'iptables', '-N', 'ironic-inspector')' returned non-zero exit status 1
> Oct 10 01:40:25 rdomanager ironic-inspector: 2015-10-10 01:40:25.741
> 40112 ERROR ironic_inspector
> Oct 10 01:40:25 rdomanager systemd:
> openstack-ironic-inspector.service: main process exited, code=exited,
> status=1/FAILURE
> Oct 10 01:40:25 rdomanager systemd: Unit
> openstack-ironic-inspector.service entered failed state.
>
>
> On Fri, Oct 9, 2015 at 5:55 PM, Dan Sneddon <dsneddon at redhat.com> wrote:
>>
>> On 10/09/2015 02:43 PM, Mohammed Arafa wrote:
>>> i seem to have hit this bug where node registration fails silently if
>>> instackenv.json is badly formatted
>>>
>>> thing is i cant seem to decipher where my config file is broken
>>>
>>>
>>> {
>>> "nodes": [
>>> {
>>> "pm_password": "P at ssw0rd",
>>> "pm_type": "pxe_ipmitool",
>>> "mac": [
>>> "00:17:a4:77:00:1c"
>>> ],
>>> "cpu": "2",
>>> "memory": "65536",
>>> "disk": "900",
>>> "arch": "x86_64",
>>> "pm_user": "root",
>>> "pm_addr": "192.168.11.213"
>>> },
>>> ]
>>> }
>>>
>>>
>>> 1)
>>> https://downloads.plex.tv/plex-media-server/0.9.12.13.1464-4ccd2ca/plexmediaserver-0.9.12.13.1464-4ccd2ca.x86_64.rpm
>>>
>>
>> Do you only have the one node? Because I don't think you want a comma
>> after the node.
>>
>> This validates:
>>
>> {
>> "nodes": [
>> {
>> "pm_password": "P at ssw0rd",
>> "pm_type": "pxe_ipmitool",
>> "mac": [
>> "00:17:a4:77:00:1c"
>> ],
>> "cpu": "2",
>> "memory": "65536",
>> "disk": "900",
>> "arch": "x86_64",
>> "pm_user": "root",
>> "pm_addr": "192.168.11.213"
>> }
>> ]
>> }
>>
>> By the way, when I'm doing OpenStack deployments, these resources help
>> out a lot with both JSON and YAML validation:
>>
>> http://jsonlint.com
>> http://yamllint.com
>> http://jsontoyaml.com
>> http://yamltojson.com
>>
>> --
>> Dan Sneddon | Principal OpenStack Engineer
>> dsneddon at redhat.com | redhat.com/openstack
>> 650.254.4025 | dsneddon:irc @dxs:twitter
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>> To unsubscribe: rdo-list-unsubscribe at redhat.com
>
>
>
>
More information about the rdo-list
mailing list