forked from crowbar/crowbar-openstack
-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
So, I added with crowbarctl proposal edit nfs_client nova -m --data="{ 'deployment': { 'nfs_client': { 'elements': { 'nfs-client': ['hostname-C.domain']}}}}" a host to a proposal and committed it. After the commit, the node is in the proposal
# crowbarctl proposal show nfs_client nova --format json
{
"id": "nfs_client-nova",
"description": "Setup of NFS mounts",
"attributes": {
"nfs_client": {
"exports": {
"nova": {
"nfs_server": "192.168.128.251",
"export": "/export",
"mount_path": "/var/lib/nova/instances",
"mount_options": [
"vers=3",
"sec=sys",
"x-systemd.automount"
]
}
}
}
},
"deployment": {
"nfs_client": {
"crowbar-revision": 0,
"crowbar-applied": true,
"element_states": {
"nfs-client": [
"readying",
"ready",
"applying"
]
},
"elements": {
"nfs-client": [
"hostname-A.domain",
"hostname-B.domain",
"hostname-C.domain"
]
},
"element_order": [
[
"nfs-client"
]
],
"config": {
"environment": "nfs_client-base-config",
"mode": "full",
"transitions": false,
"transition_list": [
]
},
"crowbar-committing": false,
"crowbar-status": "success",
"crowbar-failed": "",
"crowbar-queued": false
}
}
}
but if I check with the actual host, the roles for nfs_client are not added
# crowbarctl node show hostname-C.domain --filter roles --format json
[
"crowbar-hostname-C_domain",
"deployer-client",
"deployer-config-default",
"bmc-nat-client",
"ipmi-config-default",
"network",
"network-config-default",
"dns-client",
"dns-config-default",
"logging-client",
"logging-config-default",
"ntp-client",
"ntp-config-default",
"provisioner-base",
"provisioner-config-default"
]
the same happens if I try to apply this way the nova barclamp. What do I miss?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels