New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix generation of firecracker config #1001
Comments
jodh-intel
added
bug
Incorrect behaviour
needs-review
Needs to be assessed by the team.
labels
Oct 20, 2020
jodh-intel
added a commit
to jodh-intel/kata-containers
that referenced
this issue
Oct 20, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#1001. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
c3d
pushed a commit
to c3d/runtime
that referenced
this issue
Oct 20, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#3005 From kata-containers/kata-containers#1002 Fixing kata-containers/kata-containers#1001 Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
c3d
pushed a commit
to c3d/runtime
that referenced
this issue
Oct 21, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#3005 From kata-containers/kata-containers#1002 Fixing kata-containers/kata-containers#1001 Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
c3d
pushed a commit
to c3d/runtime
that referenced
this issue
Oct 22, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#3005 From kata-containers/kata-containers#1002 Fixing kata-containers/kata-containers#1001 Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
c3d
pushed a commit
to c3d/runtime
that referenced
this issue
Oct 27, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#3005 From kata-containers/kata-containers#1002 Fixing kata-containers/kata-containers#1001 Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
c3d
pushed a commit
to c3d/runtime
that referenced
this issue
Nov 5, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#3005 From kata-containers/kata-containers#1002 Fixing kata-containers/kata-containers#1001 Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
c3d
pushed a commit
to c3d/runtime
that referenced
this issue
Nov 10, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#3005 From kata-containers/kata-containers#1002 Fixing kata-containers/kata-containers#1001 Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
fidencio
pushed a commit
to fidencio/kata-runtime
that referenced
this issue
Nov 11, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#3005 From kata-containers/kata-containers#1002 Fixing kata-containers/kata-containers#1001 Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
fidencio
pushed a commit
to fidencio/kata-runtime
that referenced
this issue
Nov 11, 2020
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#3005 From kata-containers/kata-containers#1002 Fixing kata-containers/kata-containers#1001 Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com> Signed-off-by: Christophe de Dinechin <dinechin@redhat.com>
c3d
pushed a commit
that referenced
this issue
Apr 12, 2021
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: #1001. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
c3d
pushed a commit
to c3d/kata-containers
that referenced
this issue
Apr 12, 2021
The build was setting a `FCVALIDPATHS` variable for firecracker, but that was never being used. Conversely, the firecracker configuration template was expecting a `FCVALIDHYPERVISORPATHS`, but that variable was never being set. Resolve by only setting the `FCVALIDHYPERVISORPATHS` variable to ensure the generated firecracker config is valid once again. Fixes: kata-containers#1001. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PR #902 reworked the code that generates the hypervisor configuration, but we didn't catch a problem: the
FCVALIDPATHS
variable is set, but never referenced byconfiguration-fc.toml
. The configuration file is actually expecting to be passed aFCVALIDHYPERVISORPATHS
variable but that is never set resulting in the following inconfiguration-fc.toml
:valid_hypervisor_paths =
The impact is that you cannot run a firecracker container until you change your
configuration-fc.toml
file to specify:The text was updated successfully, but these errors were encountered: