Bug #12821
open
Unable to update a new VM's config after VM is successfully created
Description
After a new VM is created and successfully reporting back the status to Foreman, I tried to add/remove a Puppet Module on the server. However when I click "submit", the UI switches to the Network tab (Domain) and I cannot do anything with this and have to cancel out the change. Also, the correct Domain is already populated in the Domain field.
I have noticed that this occurs on VMs that show the "Float IP" on the Host-Details page, but with VMs that show the "Private IP and MAC" I am able to successfully add/remove a Puppet Module.
This is a Foreman (1.7.5) with an Openstack (Kilo) backend.
There are 3 Subnets defined:
VM (Openstack VMs) (196.168.xxx.xxx)
BareMetal (other Infrastructure servers) (10.32.xx5.xxx)
Openstack-Hosts (Openstack Infrastrure components) (10.32.xx6.xxx)
There are 2 Domains defined:
Main environment domain (stage.xxxx.com)
VM sub-domain of the Main environment domain (vm.xxxx.com)
I am not seeing anything that stands out in the logs.
Updated by Dominic Cleal over 8 years ago
- Status changed from New to Feedback
production.log may indicate precisely which attribute is failing validation to allow you to fix it.
Otherwise this bug report is against too old a version, please re-test on a newer release as the networking support in hosts and the host form has significantly changed as of Foreman 1.8.
Updated by Andrew Enstad over 8 years ago
From the production.log I see that is it pulling in my userid into the "MAC address field. And is reporting that is is not a valid MAC address. Any idea why it would pull in that into the MAC?
Updated by Anonymous about 7 years ago
- Category set to Compute resources - OpenStack
- Status changed from Feedback to New