Issue with engine-setup on master

Hi, I pulled the latest mater rpms from nightly builds [1] and there seems to be a issue running engine-setup. engine-setup fails with message [root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map' I had the same issue with dev env on master Any ideas Thanks Ravi [1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm

Should mention that I am on Fedora 28 On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Hi,
I pulled the latest mater rpms from nightly builds [1] and there seems to be a issue running engine-setup.
engine-setup fails with message
[root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map'
I had the same issue with dev env on master
Any ideas
Thanks
Ravi
[1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm

On Mon, Jul 30, 2018 at 9:50 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Should mention that I am on Fedora 28
On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Hi,
I pulled the latest mater rpms from nightly builds [1] and there seems to be a issue running engine-setup.
engine-setup fails with message
[root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map'
It's because we recently changed otopi to use python3 by default on fedora, and engine-setup is broken. Fixing above error is probably easy, but then you'll probably run into other errors. To workaround this, for now, you can run it with: OTOPI_PYTHON=/bin/python engine-setup Or, for a "permanent" solution, mkdir -p /etc/otopi.env.d echo 'OTOPI_PYTHON=/bin/python' > /etc/otopi.env.d/use-python2.env Adding Gal, who is working on python3/fedora support. Not sure about the exact status right now. If it's expected to take more than a few days until it's working at least for dev-env, perhaps we should default back to python2. Best regards,
I had the same issue with dev env on master
Any ideas
Thanks
Ravi
[1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/P5P65S5QVNGDRA...
-- Didi

Scott noticed while using my ansible dev env setup role that some packages changed names. Looks like there are py2 and py3 versions. I had assumed that was from this work -- is that correct? Since this work brings much instability for developers, it's important to communicate this stuff before it breaks ;) On Tue, Jul 31, 2018 at 4:01 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, Jul 30, 2018 at 9:50 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Should mention that I am on Fedora 28
On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Hi,
I pulled the latest mater rpms from nightly builds [1] and there seems
to
be a issue running engine-setup.
engine-setup fails with message
[root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map'
It's because we recently changed otopi to use python3 by default on fedora, and engine-setup is broken. Fixing above error is probably easy, but then you'll probably run into other errors.
To workaround this, for now, you can run it with:
OTOPI_PYTHON=/bin/python engine-setup
Or, for a "permanent" solution,
mkdir -p /etc/otopi.env.d echo 'OTOPI_PYTHON=/bin/python' > /etc/otopi.env.d/use-python2.env
Adding Gal, who is working on python3/fedora support. Not sure about the exact status right now. If it's expected to take more than a few days until it's working at least for dev-env, perhaps we should default back to python2.
Best regards,
I had the same issue with dev env on master
Any ideas
Thanks
Ravi
[1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/P5P65S5QVNGDRA...
-- Didi _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CENSLHLYCS4OLR...
-- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme@redhat.com IRC: gshereme <https://red.ht/sig>

On Tue, Jul 31, 2018 at 5:04 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Scott noticed while using my ansible dev env setup role that some packages changed names. Looks like there are py2 and py3 versions. I had assumed that was from this work -- is that correct? Since this work brings much instability for developers, it's important to communicate this stuff before it breaks ;)
Sorry, you are right. Now pushed this to revert for now: https://gerrit.ovirt.org/93414 Once it's merged, you can use the below workaround (amended) to default to python3, until we revert above patch, hopefully soon. Best regards,
On Tue, Jul 31, 2018 at 4:01 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, Jul 30, 2018 at 9:50 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Should mention that I am on Fedora 28
On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Hi,
I pulled the latest mater rpms from nightly builds [1] and there seems
to
be a issue running engine-setup.
engine-setup fails with message
[root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map'
It's because we recently changed otopi to use python3 by default on fedora, and engine-setup is broken. Fixing above error is probably easy, but then you'll probably run into other errors.
To workaround this, for now, you can run it with:
OTOPI_PYTHON=/bin/python engine-setup
Or, for a "permanent" solution,
mkdir -p /etc/otopi.env.d echo 'OTOPI_PYTHON=/bin/python' > /etc/otopi.env.d/use-python2.env
Adding Gal, who is working on python3/fedora support. Not sure about the exact status right now. If it's expected to take more than a few days until it's working at least for dev-env, perhaps we should default back to python2.
Best regards,
I had the same issue with dev env on master
Any ideas
Thanks
Ravi
[1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ P5P65S5QVNGDRAIJFMJTK5YHHICGFOSW/
-- Didi _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community- guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/ message/CENSLHLYCS4OLR672Y7QBM2OWMLXL25E/
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
-- Didi

On Wed, Aug 1, 2018 at 9:46 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Tue, Jul 31, 2018 at 5:04 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Scott noticed while using my ansible dev env setup role that some packages changed names. Looks like there are py2 and py3 versions. I had assumed that was from this work -- is that correct? Since this work brings much instability for developers, it's important to communicate this stuff before it breaks ;)
Sorry, you are right.
Now pushed this to revert for now:
https://gerrit.ovirt.org/93414
Once it's merged, you can use the below workaround (amended) to default to python3, until we revert above patch, hopefully soon.
Merged now, should land in master snapshot repo soon. Sorry for the noise.
Best regards,
On Tue, Jul 31, 2018 at 4:01 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, Jul 30, 2018 at 9:50 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Should mention that I am on Fedora 28
On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Hi,
I pulled the latest mater rpms from nightly builds [1] and there
seems to
be a issue running engine-setup.
engine-setup fails with message
[root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map'
It's because we recently changed otopi to use python3 by default on fedora, and engine-setup is broken. Fixing above error is probably easy, but then you'll probably run into other errors.
To workaround this, for now, you can run it with:
OTOPI_PYTHON=/bin/python engine-setup
Or, for a "permanent" solution,
mkdir -p /etc/otopi.env.d echo 'OTOPI_PYTHON=/bin/python' > /etc/otopi.env.d/use-python2.env
Adding Gal, who is working on python3/fedora support. Not sure about the exact status right now. If it's expected to take more than a few days until it's working at least for dev-env, perhaps we should default back to python2.
Best regards,
I had the same issue with dev env on master
Any ideas
Thanks
Ravi
[1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/messag e/P5P65S5QVNGDRAIJFMJTK5YHHICGFOSW/
-- Didi _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/communit y/about/community-guidelines/ List Archives: https://lists.ovirt.org/archiv es/list/devel@ovirt.org/message/CENSLHLYCS4OLR672Y7QBM2OWMLXL25E/
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
-- Didi
-- Didi

On Wed, Aug 1, 2018 at 11:37 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Aug 1, 2018 at 9:46 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Tue, Jul 31, 2018 at 5:04 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Scott noticed while using my ansible dev env setup role that some packages changed names. Looks like there are py2 and py3 versions. I had assumed that was from this work -- is that correct? Since this work brings much instability for developers, it's important to communicate this stuff before it breaks ;)
Sorry, you are right.
Now pushed this to revert for now:
https://gerrit.ovirt.org/93414
Once it's merged, you can use the below workaround (amended) to default to python3, until we revert above patch, hopefully soon.
Merged now, should land in master snapshot repo soon. Sorry for the noise.
BTW, we only default(ed) to python3 if python3-otopi was installed, which is not (yet!) required by the engine. So another fix is to not install it.
Best regards,
On Tue, Jul 31, 2018 at 4:01 AM Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, Jul 30, 2018 at 9:50 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Should mention that I am on Fedora 28
On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Hi,
I pulled the latest mater rpms from nightly builds [1] and there
seems to
be a issue running engine-setup.
engine-setup fails with message
[root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map'
It's because we recently changed otopi to use python3 by default on fedora, and engine-setup is broken. Fixing above error is probably easy, but then you'll probably run into other errors.
To workaround this, for now, you can run it with:
OTOPI_PYTHON=/bin/python engine-setup
Or, for a "permanent" solution,
mkdir -p /etc/otopi.env.d echo 'OTOPI_PYTHON=/bin/python' > /etc/otopi.env.d/use-python2.env
Adding Gal, who is working on python3/fedora support. Not sure about the exact status right now. If it's expected to take more than a few days until it's working at least for dev-env, perhaps we should default back to python2.
Best regards,
I had the same issue with dev env on master
Any ideas
Thanks
Ravi
[1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-maste
r.rpm
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/messag e/P5P65S5QVNGDRAIJFMJTK5YHHICGFOSW/
-- Didi _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/communit y/about/community-guidelines/ List Archives: https://lists.ovirt.org/archiv es/list/devel@ovirt.org/message/CENSLHLYCS4OLR672Y7QBM2OWMLXL25E/
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
-- Didi
-- Didi
-- Didi

On Wed, Aug 1, 2018 at 5:11 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Aug 1, 2018 at 11:37 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Aug 1, 2018 at 9:46 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Tue, Jul 31, 2018 at 5:04 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Scott noticed while using my ansible dev env setup role that some packages changed names. Looks like there are py2 and py3 versions. I had assumed that was from this work -- is that correct? Since this work brings much instability for developers, it's important to communicate this stuff before it breaks ;)
Greg I'm PRing your ansible role with the package names that I ended up using that worked on f28 and centos7.
Sorry, you are right.
Now pushed this to revert for now:
https://gerrit.ovirt.org/93414
Once it's merged, you can use the below workaround (amended) to default to python3, until we revert above patch, hopefully soon.
Merged now, should land in master snapshot repo soon. Sorry for the noise.
BTW, we only default(ed) to python3 if python3-otopi was installed, which is not (yet!) required by the engine. So another fix is to not install it.
Or to remove it if it got installed by accident (which was the last bit I needed to fix before engine setup worked on my f28).

Thanks that helped On Tue, Jul 31, 2018 at 3:43 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, Jul 30, 2018 at 9:50 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Should mention that I am on Fedora 28
On Mon, Jul 30, 2018 at 2:08 PM, Ravi Shankar Nori <rnori@redhat.com> wrote:
Hi,
I pulled the latest mater rpms from nightly builds [1] and there seems
to
be a issue running engine-setup.
engine-setup fails with message
[root@laptop ovirt-engine-master-new9]# engine-setup ***L:ERROR Internal error: No module named 'async_tasks_map'
It's because we recently changed otopi to use python3 by default on fedora, and engine-setup is broken. Fixing above error is probably easy, but then you'll probably run into other errors.
To workaround this, for now, you can run it with:
OTOPI_PYTHON=/bin/python engine-setup
Or, for a "permanent" solution,
mkdir -p /etc/otopi.env.d echo 'OTOPI_PYTHON=/bin/python' > /etc/otopi.env.d/use-python2.env
Adding Gal, who is working on python3/fedora support. Not sure about the exact status right now. If it's expected to take more than a few days until it's working at least for dev-env, perhaps we should default back to python2.
Best regards,
I had the same issue with dev env on master
Any ideas
Thanks
Ravi
[1] https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ P5P65S5QVNGDRAIJFMJTK5YHHICGFOSW/
-- Didi
participants (4)
-
Greg Sheremeta
-
Ravi Shankar Nori
-
Scott Dickerson
-
Yedidyah Bar David