[Rdo-list] instack-virt-setup depends on EPEL for Liberty
by Samuel Cassiba
Clean install of CentOS 7.1 (as of yesterday) and following along with
http://docs.openstack.org/developer/tripleo-docs/ for Liberty.
When I go to run instack-virt-setup, I'm prompted to configure EPEL:
+ tripleo install-dependencies
EPEL repository is required to install python-pip for CentOS.
See http://fedoraproject.org/wiki/EPEL
When I look at /usr/libexec/openstack-tripleo/install-dependencies, I find
it does call for EPEL:
if [ "$TRIPLEO_OS_FAMILY" = "redhat" ]; then
# For CentOS, python-pip and jq are in EPEL
if [ "$TRIPLEO_OS_DISTRO" = "centos" ] && [ ! -f
/etc/yum.repos.d/epel.repo ]; then
echo EPEL repository is required to install python-pip for CentOS.
echo See http://fedoraproject.org/wiki/EPEL
exit 1
fi
sudo -E yum install -y python-lxml libvirt-python libvirt qemu-img
qemu-kvm git python-pip openssl-devel python-devel gcc audit
python-virtualenv openvswitch python-yaml net-tools redhat-lsb-core
libxslt-devel jq openssh-server libffi-devel which glusterfs-api
python-netaddr
sudo service libvirtd restart
sudo service openvswitch restart
sudo chkconfig openvswitch on
fi
Indeed after removing the if statement for EPEL, instack-virt-setup appears
to proceed without issue and provisions the instack VM, but that VM won't
allow me to login as root. Any pointers would be great.
9 years
[Rdo-list] Undercloud Installation Version
by AliReza Taleghani
Hi, what will happen if I just enable:
- Enable last known good RDO Trunk Delorean repository for core
openstack packages
- Enable the Delorean Deps repository
I mean not to enable:
- Enable latest RDO Trunk Delorean repository only for the TripleO
packages
dose it mean that I am strictly sticked to stable ci passed branch?
or it's miss configration and I should reinstall Cent OS 7 (minimal) to be
able to reinstall undercloud?
dose it reflect on openstack version of overcloud? (Juno vs Kilo)
Sincerely,
Ali R. Taleghani
@linkedIn <http://ir.linkedin.com/in/taleghani>
9 years
[Rdo-list] Undercloud Deployment Error
by Dan Sneddon
I'm working with a Red Hat partner who is doing development against
RDO, and he was trying to install the latest undercloud code from RDO
Delorean passed CI. His Undercloud isn't installing:
"Error: Could not find resource 'Keystone_domain[heat_domain]' for
relationship from 'Class[Keystone::Roles::Admin]' on node instack" in
the file /etc/puppet/manifests/puppet-stack-config.pp:295
He looked further into the code to see what was causing this, and found
something which has changed in the last few weeks:
"Service['keystone'] -> Class['::keystone::roles::admin'] ->
Keystone_domain['heat_domain']" -> file
/etc/puppet/manifests/puppet-stack-config.pp:295 [NEW CODE]
as opposed to :
"Service['keystone'] -> Class['::keystone::roles::admin'] ->
Exec['heat_domain_create']" -> file
/etc/puppet/manifests/puppet-stack-config.pp: [OLD DEPLOYMENT - couple
of weeks ago]
Does anyone know what is causing this error, or whether this is a bug
which has crept in to "openstack undercloud install"?
--
Dan Sneddon | Principal OpenStack Engineer
dsneddon(a)redhat.com | redhat.com/openstack
650.254.4025 | dsneddon:irc @dxs:twitter
9 years
[Rdo-list] Jumbo MTU to instances in Kilo?
by Erich Weiler
Hi Y'all,
I know someone must have figured this one out, but I can't seem to get
9000 byte MTUs working. I have it set in plugin.ini, etc, my nodes have
MTU=9000 on their interfaces, so does the network node. dnsmasq also is
configured to set MTU=9000 on instances, which works. But I still can't
ping with large packets to my instance:
[weiler@stacker ~]$ ping 10.50.100.2
PING 10.50.100.2 (10.50.100.2) 56(84) bytes of data.
64 bytes from 10.50.100.2: icmp_seq=1 ttl=63 time=2.95 ms
64 bytes from 10.50.100.2: icmp_seq=2 ttl=63 time=1.14 ms
64 bytes from 10.50.100.2: icmp_seq=3 ttl=63 time=0.661 ms
That works fine. This however doesn't work:
[root@stacker ~]# ping -M do -s 8000 10.50.100.2
PING 10.50.100.2 (10.50.100.2) 8000(8028) bytes of data.
From 10.50.100.2 icmp_seq=1 Frag needed and DF set (mtu = 1500)
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
ping: local error: Message too long, mtu=1500
It looks like somehow the br-int interface for OVS isn't set at 9000,
but I can't figure out how to do that...
Here's ifconfig on my compute node:
br-enp3s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
inet6 fe80::ec4:7aff:fe58:423e prefixlen 64 scopeid 0x20<link>
ether 0c:c4:7a:58:42:3e txqueuelen 0 (Ethernet)
RX packets 2401432 bytes 359276713 (342.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30 bytes 1572 (1.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-int: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::64dc:94ff:fe35:db4c prefixlen 64 scopeid 0x20<link>
ether 66:dc:94:35:db:4c txqueuelen 0 (Ethernet)
RX packets 69 bytes 6866 (6.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp3s0f0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 9000
inet6 fe80::ec4:7aff:fe58:423e prefixlen 64 scopeid 0x20<link>
ether 0c:c4:7a:58:42:3e txqueuelen 1000 (Ethernet)
RX packets 130174458 bytes 15334807929 (14.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22919305 bytes 5859090420 (5.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp3s0f0.50: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
inet 10.50.1.236 netmask 255.255.0.0 broadcast 10.50.255.255
inet6 fe80::ec4:7aff:fe58:423e prefixlen 64 scopeid 0x20<link>
ether 0c:c4:7a:58:42:3e txqueuelen 0 (Ethernet)
RX packets 38429352 bytes 5152853436 (4.7 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 419842 bytes 101161981 (96.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 22141566 bytes 1185622090 (1.1 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22141566 bytes 1185622090 (1.1 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
qbr247da3ed-a4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5c8f:c0ff:fe79:bc11 prefixlen 64 scopeid 0x20<link>
ether b6:1f:54:3f:3d:48 txqueuelen 0 (Ethernet)
RX packets 16 bytes 1472 (1.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
qbrf42ea01f-fe: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::f484:f1ff:fe53:fb2e prefixlen 64 scopeid 0x20<link>
ether c2:a6:d8:25:63:ea txqueuelen 0 (Ethernet)
RX packets 15 bytes 1456 (1.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
qvb247da3ed-a4: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet6 fe80::b41f:54ff:fe3f:3d48 prefixlen 64 scopeid 0x20<link>
ether b6:1f:54:3f:3d:48 txqueuelen 1000 (Ethernet)
RX packets 247 bytes 28323 (27.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 233 bytes 25355 (24.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
qvbf42ea01f-fe: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet6 fe80::c0a6:d8ff:fe25:63ea prefixlen 64 scopeid 0x20<link>
ether c2:a6:d8:25:63:ea txqueuelen 1000 (Ethernet)
RX packets 377 bytes 57664 (56.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 333 bytes 38765 (37.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
qvo247da3ed-a4: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet6 fe80::dcfa:f1ff:fe03:ee88 prefixlen 64 scopeid 0x20<link>
ether de:fa:f1:03:ee:88 txqueuelen 1000 (Ethernet)
RX packets 233 bytes 25355 (24.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 247 bytes 28323 (27.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
qvof42ea01f-fe: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet6 fe80::f03e:35ff:fefe:e52 prefixlen 64 scopeid 0x20<link>
ether f2:3e:35:fe:0e:52 txqueuelen 1000 (Ethernet)
RX packets 333 bytes 38765 (37.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 377 bytes 57664 (56.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tap247da3ed-a4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc16:3eff:fede:5eea prefixlen 64 scopeid 0x20<link>
ether fe:16:3e:de:5e:ea txqueuelen 500 (Ethernet)
RX packets 219 bytes 24239 (23.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 224 bytes 26661 (26.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast
192.168.122.255
ether 52:54:00:c4:75:9f txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
This is on RHEL 7.1. Any obvious way I can get all the intermediate
bridges to MTU=9000? I've RTFM'd and googled to no avail...
Here's the ovs-vsctl outout:
[root@node-136 ~]# ovs-vsctl show
6f5a5f00-59e2-4420-aeaf-7ad464ead232
Bridge br-int
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "qvo247da3ed-a4"
tag: 1
Interface "qvo247da3ed-a4"
Port "int-br-eth1"
Interface "int-br-eth1"
Port "int-br-enp3s0f0"
Interface "int-br-enp3s0f0"
type: patch
options: {peer="phy-br-enp3s0f0"}
Bridge "br-enp3s0f0"
Port "enp3s0f0"
Interface "enp3s0f0"
Port "br-enp3s0f0"
Interface "br-enp3s0f0"
type: internal
Port "phy-br-enp3s0f0"
Interface "phy-br-enp3s0f0"
type: patch
options: {peer="int-br-enp3s0f0"}
ovs_version: "2.3.1"
Many thanks if anyone has any information on this topic! Or can point
me to some documentation I missed...
Thanks,
erich
9 years
[Rdo-list] Heat stack create failed on overcloud deploy in tripleO
by Richards, Jeff
Trying to stand up a cloud using tripleO on CentOS 7 with libvirt+kvm virtual machines. Following along the tripleO documentation just to get something stood up for learning purposes, so using all the default options and installing from repos as per docs. Seems I am almost there. The overcloud deploy from the undercloud controller does not complete successfully:
[stack@instack ~]$ openstack overcloud deploy --templates
Deploying templates in the directory /usr/share/openstack-tripleo-heat-templates
Stack failed with status: Resource CREATE failed: resources.ComputePuppetDeployment: resources.ComputeNodesPostDeployment.Error: resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1
Heat Stack create failed.
Nova list shows the controller and novacompute running, heat stack-list shows the stack_status as "UPDATE_FAILED".
Logging on to the overlcoud controller and poking around I Traced it down to an error in /var/lib/heat-config/heat-config-puppet/0d44cd1d-799b-4dcd-b09c-538a89bf3b7a.pp:467:
package_manifest{$package_manifest_name: ensure => present}
Error is Invalid resource type package_manifest (from /var/log/messages on the overcloud controller):
template[/etc/puppet/modules/keepalived/templates/global_config.erb]:3\n
(at /etc/puppet/modules/keepalived/templates/global_config.erb:3:in `block in result')\u001b[0m\n
\u001b[1;31mWarning: notify is a metaparam; this value will inherit to all contained resources in the keepalived::instance definition\u001b[0m\n
\u001b[1;31mError: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type package_manifest at /var/lib/heat-config/heat-config-puppet/0d44cd1d-799b-4dcd-b09c-538a89bf3b7a.pp:467 on node overcloud-controller-0.localdomain\n
Wrapped exception:\n
Invalid resource type package_manifest\u001b[0m\n\u001b[1;31mError: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type package_manifest at /var/lib/heat-config/heat-config-puppet/0d44cd1d-799b-4dcd-b09c-538a89bf3b7a.pp:467 on node overcloud-controller-0.localdomain\u001b[0m\n
I do not know puppet and have spent nearly a full day searching for a workaround. Any tips would be appreciated!
Jeff Richards
This message and any enclosures are intended only for the addressee. Please
notify the sender by email if you are not the intended recipient. If you are
not the intended recipient, you may not use, copy, disclose, or distribute this
message or its contents or enclosures to any other person and any such actions
may be unlawful. Ball reserves the right to monitor and review all messages
and enclosures sent to or from this email address.
9 years
[Rdo-list] Nodes introspection
by Marius Cornea
Hi everyone,
A couple of questions regarding introspection (following the upstream docs):
1. Is Swift still used for storing nodes introspection details? I see no Swift object resulting after running introspection.
2. During introspection I can see error messages on the VMs console(running a virt environment) but it's hard to record them since the VM quickly turns off. What's the proper way to debug this?
3. The profile matching docs[1] reference ironic-discoverd which has now become ironic-inspector. How can we make this work? s/discoverd/inspector/ ?
Thanks,
Marius
[1] http://docs.openstack.org/developer/tripleo-docs/advanced_deployment/prof...
9 years
