RHEL7 should be acceptable series for charms
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
There is no possible way to deploy RHEL 7 with a juju charm.
Setting the series to "rhel7" and deploying to a maas with a custom Red Hat 7 image resulted in:
16:06:21 INFO juju.cmd supercommand.go:56 running juju [2.4.3 gc go1.10]
16:06:21 DEBUG juju.cmd supercommand.go:57 args: []string{
16:06:21 INFO juju.juju api.go:67 connecting to API addresses: [10.244.
16:06:22 DEBUG juju.api apiclient.go:877 successfully dialed "wss://
16:06:22 INFO juju.api apiclient.go:599 connection established to "wss://
16:06:22 DEBUG juju.cmd.
16:06:22 DEBUG juju.api monitor.go:35 RPC connection died
ERROR unknown OS for series: "rhel7"
16:06:22 DEBUG cmd supercommand.go:459 error stack:
unknown OS for series: "rhel7"
github.
github.
github.
github.
github.
Currently rhel7 is not listed in the series versions map:
https:/
tags: | added: cdo-qa |
Thanks for the bug report. You're correct in that we don't currently list RHEL in the known series as we don't have images that we can test/rely on as being suitable for the expectations of Juju and the charms that are used. We don't list out things that we're not sure will function.
You have custom images in this case, and it makes sense to allow users to be able to do what they'd like. We'll see what we can do to enable custom setups so that we don't block users from pushing Juju into new/different spaces.