Does QA in DevOps roles means CI/CD or more? One of views on DevOps is to say that it combines fileds of Development, Operations and Quality Assurance.

Now many DevOps roles have focus either 


on development with the left shift in terms of operations awareness (up to a No-Ops full stack, you build it - you run it (c) Besos, Amazon's CTO), 
or a sysadmin who is expected to write CaSC (Configurarion as Code), IaC (infrastructure as code) and automation codes to reduce work required in operations.


In both cases you see lots of tools typical for these roles with and without DevOps context.

What does QA DevOps roles do today as a formal commitment? Test automation always has been there, for example. Is QA just meant here to support CI/CD infrastructure and teams working on it, or something else?
First, DevOps is a journey, not a destination.  Not every organization approaches similar problems with the same solution; while automation is a component of a DevOps platform, it's not the single defining characteristic.

The role and responsibilities of QA professionals haven't really changed; they're still responsible for validating that code is ready for release.  What HAS changed is the focus on both automation and smaller releases.  Much like operational roles, QA staff should now have the opportunity to focus on adding additional automatic quality checks into the development life cycle.

In a shop with a mature CI/CD pipeline, QA becomes more about designing great tests, and letting the software do the actual heavy lifting. As Tensibai commented above, "some QA tests can't be automated" (yet), so there will still need to be some engineering responsibilities, but the goal should be to utilize automation in every aspect of delivery in order to facilitate adding additional quality.