Catalog compilation failed sometimes
Bug #1403480 reported by
Vyacheslav Struk
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-vswitch |
Fix Released
|
High
|
Alex Schultz |
Bug Description
Catalog compilation fails with:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Sometimes puppet run ends-up successfully with just the same config, so it looks like a kind of race condition.
Both ovs_redhat_el6.rb and ovs_redhat.rb are present on a client and they are equal to server's files.
Puppet version is 3.6.2, module is from a master branch.
Changed in puppet-vswitch: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in puppet-vswitch: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I am also experiencing the the same behaviour listed here. I am running on RHEL7 with 2 physical NICs bonded with OVS, and a bridge on top. The module works fine on RHEL6 with the same configuration, though not in RHEL7. Puppet agent and master are 3.8.1
I am using the puppet-vswitch master branch.
# cat ifcfg-bond0 "enp2s0f0 enp2s0f1" "lacp=passive bond_mode= balance- tcp" type/vs_ port: Could not autoload puppet/ provider/ vs_port/ ovs_redhat_ el6: Could not find parent provider ovs_redhat of ovs_redhat_el6 on node <fqdn>
NAME=bond0
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
TYPE=OVSBond
DEVICETYPE=ovs
OVS_BRIDGE=br-bond0
BOND_IFACES=
OVS_OPTIONS=
NM_CONTROLLED=no
# puppet agent -td
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/
I have had the catalog compile successfully without changing any other code, the vast majority of the time though indicates the above failure.